3 ms·
Looking forward to seeing whether this contains a microcode or OS patch to fix what appears to be an Ice Lake CPU bug: https://youtrack.jetbrains.com/issue/JBR
by api 6y ago
Looking forward to seeing whether this contains a microcode or OS patch to fix what appears to be an Ice Lake CPU bug:
https://youtrack.jetbrains.com/issue/JBR-2310 https://youtrack.jetbrains.com/issue/JBR-2310
Read the whole thing. It really appears as if there is a virtualization-escaping CPU-crashing bug in Ice Lake (10th generation) Intel chips that was discovered because it exclusively crashes when used with Jetbrains IDEs.
Sounds unlikely, yes, but seriously read the whole thing.
- api 6y agoSelf-reply: no, it apparently does not. Microcode rev is the same and the issue is still there. TL;DR: Jetbrains IDEs all crash on the 2020 Air, which has a 10th gen Ice Lake CPU in it. Sometimes it brings down the OS. Doesn't happen at all on older Macs. At first I and everyone else thought it was a MacOS or maybe graphics driver bug. Then the plot thickened... I tried it in a Parallels Linux VM, and it crashed and brought down the entire host. Not the VM, the host. This should not be possible. Then someone reported that it also afflicts a Microsoft Surface model with the same generation CPU. So given that it escapes VM isolation and occurs on multiple OSes and hardware, it really appears as if this is an Intel CPU bug being triggered by some exotic pattern of instructions being generated by the JVM. I must also add that nothing else crashes on this machine. Nothing. I've run multiple OSes in concurrent VMs, done heavy work, run GPU stress tests, and it's rock solid... unless I fire up CLion or GoLand... then kaboom. No I'm not the only reporter. No it's not (insert mundane thing here). Read the whole thread I linked above.