if anyone ever reads about this comment, please start to think about how to fuzz your software in a fast way. You don't need to correct or patch every bug, you just need to find where the algorithm A, B, C doesn't perform well, or where you have an allocation of 2 MBs for a linked list that should have been half of it.
I'm not a daily user of jetbrains product, but please. If there's any engineering/developers, start to use afl/cargo fuzz or whatever your fuzzer is, and spot bottlenecks, issues. I started to write software because I was looking at the quality of the very first softwares that were being fuzzed and it opened me some doors.
I'm very sad to see some bugs catch by my fuzzer that was coded in three minutes of cargo-fuzz, disrupting UX. I filled some apple feedbacks that were fortunately fixed by some engineers, but I wonder what's happening under Q&A testing.