3 ms·
Interestingly, one commenter posted that switching to OpenJDK fixes it. So it's some interaction between the hardware, the JRE, and JetBrains. I look forward to
by _bxg1 6y ago
Interestingly, one commenter posted that switching to OpenJDK fixes it. So it's some interaction between the hardware, the JRE, and JetBrains. I look forward to the post-mortem for this one.
- api 6y agoRead more. It doesn't, though it may be less frequent under OpenJDK (hard to tell as its random). Disabling newer GCs, SSE, and AVX has no effect either. My favorite is that nothing else triggers it. Just this app. So, so bizarre. I am wondering about some mega obscure Intel errata, some specific pattern of highly improbable opcodes combined with some pattern of multithreaded memory operations... My money is still on video though. I too await the postmortem.