New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macOS kernel panic #86913
Comments
|
This just happened again, when i was trying to install new extension by John Papa. I went to https://marketplace.visualstudio.com/items?itemName=johnpapa.vscode-cloak Of course im running current VS Code version: |
|
Perhaps not a VSCode, but a VirtualBox bug, you both have virtualbox kext loaded. Same issue here. |
|
Both reports are from me, ;) |
|
There is not much VS Code can do here, would be better to file a bug with virtualbox and once they narrow down the cause, can proceed further if its a VS Code specific issue. Thanks! |
|
I dont know how you did you get that its virtualbox issue, but thats not the case. Kernel panic is clearly pointing to VScode.
And no, this is not a virtual machine. Im running it on native mac os. Im gonna mention couple contributors before you decide that this is virtualbox/macos issue and close it because memory leaks/segfaults is something that you prefer to not see. @bpasero @joaomoreno @jrieken @mjbvz @isidorn @alexdima @sandy081 @Tyriar @aeschli @roblourens |
I am sorry, misread the report. I see that the crashes happened from GPU helper process. Couple of things to try.
This is mostly likely a bug in chromium, but we can try to narrow down whats causing it based on the stack trace and report to them.
Please avoid that, actions like these are only going to annoy people and cause unnecessary delay in triaging the issue. |
|
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
|
Hello! |
|
@Olejqua I have the same thing happening to me. VSCode is open, I close my Macbook, and when I open it back up the kernel panic occurs. It's happened 4 times now. |
|
I have the same problem as well when trying to do composer install in folder inside mounted xampp drive, suddenly mac crashed in the middle of installing. Any idea if this vscode issue or anything else? |
|
@Olejqua @Nightsphere @halandi can you run with hw acceleration disabled https://code.visualstudio.com/updates/v1_40#_disable-gpu-acceleration and see if the issue happens ? |
|
Hi @deepak1556, I can confirm the problem still persist on my case. It is still crashing when i am executing composer install inside vscode, the problem does not exist when i use normal terminal (not inside vscode). Thank you. |
|
@deepak1556 yesterday I turned off the acceleration. Put the laptop to sleep and today again got a panic kernel. Also did not use the VSCode terminal. |
|
Thanks for confirming, its hard to debug with the current report, lets try to minimize the number of components that are involved,
I will try to put my machine to sleep with code running and see if I can repro the crash. |
|
I'm facing the same issue in my brand new 16-inch macbook. Have you tried to do some hardware(harddisk, memory, etc) health check? |
I had no luck with recreating the crash on my machine. Would be good to have some repro. |
|
Aside from using Electron, are there any commonalities between VSCode and MS Teams? Because I'm regularly hitting very similar kernel panics pointing to MS Teams: |
|
Also having this issue. Becoming rather frustrating. |
|
Also getting this. Happens every few hours or so. The helper isn't Code Helper, so it seems like a wider issue with Electron itself. |
|
I'm experiencing the same as of yesterday. Latest error report: Crash Reporter VSC info: Not sure what else is relevant here. The very first (and second, and third) time I got the error I was screensharing on a Zoom call, but I've had several now without Zoom. Apps that have been open every single crash are:
I've now disabled hardware acceleration as suggested above. Will report back if I get more info to share. |
|
Same thing here although mine is a bit more explicit about Electron Happens randomly while typing on a
|
|
It's been flagged on the Electron repo but they don't consider it an issue with Electron so they have closed it sadly. electron/electron#26023 |
|
Just crossposting this here as it seems this issue is not dead. Obsidian is another Electron-based app that is gaining popularity and has now started suffering from a similar KP: https://forum.obsidian.md/t/kernel-panic-on-macos-11-crash-reboot/12020 |
|
I kinda gave up trying to fix this. |
|
FWIW, I've been running into similar issues very frequently (sometimes more frequently than every hour) with VSCode 1.55.2 and MacOS 10.15.7 (Catalina). |
|
I keep having a similar issue. OSX 11.3.1 (20E241), VSC connected, via ssh, to remote host (ubuntu server 20.04, VMware): |
panic(cpu 0 caller 0xffffff800d9cccdf): "thread_invoke: preemption_level -1, possible cause: unlocking an unlocked mutex or spinlock"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4903.271.2/osfmk/kern/sched_prim.c:2420 BSD process name corresponding to current thread: Electron Mac OS version: |
|
I am seeing this on a MacBook Pro 2019 16"...lovely bug |
Possibly related to #63588
It looks like mac os crash was caused by VSCode. I dont remember if i was working in VScode at the time, but im sure it was open.
My VSCode info. I update VScode ASAP, so today i updated it as well, but i dont remember if the crash happened before or after this update.
VSCode info:
System information:
Extensions info:
Kernel panic info:
The text was updated successfully, but these errors were encountered: