-
Notifications
You must be signed in to change notification settings - Fork 190
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
vpnkit crashing on intel macOS 12.6.1 with EXC_BAD_ACCESS (SIGSEGV) #610
Comments
Any idea what's going on? Also frequently crashing on my M2 MacBook Air after upgrade to Ventura and after Reset.
|
I have the same problem since Monday. Vpnkit keeps crashing in pretty much the same way. Your crash reports don't look exactly like mine and they're missing the stack for the crashed thread (number 3), so it might be a different issue. For me, they always happen in
|
The stack trace is the same one that I get in this repro case: docker/for-mac#6530 (comment) But we haven't been able to boil it down to a smaller repro case yet. i have a strong suspicion that this is a regression in lwt, and was introduced when we upgraded lwt from 5.5 to 5.6. |
That does sound quite familiar, as the referenced issue(s) seem to be related to running Chrome/Chromium in a container. In my case, I'm also running Chromium when the crash occurs. We're running a suite of Playwright tests with the |
No longer seeing the issue in the latest build mentioned here: docker/for-mac#6530 (comment) |
I have the same issue too. Just upgraded to Ventura 13.1 and Docker is still crashing. My docker is also the latest version (Docker Desktop 4.15.0 (93002) )
|
Even using the latest 4.16 version this is still happening every 1-2 days for me.. have to force kill all the docker processes and start docker again on my 2012 Mac mini running Ventura.
can include more if necessary |
I am also having the same issues, for me the last stable version was 4.12, every release after this has been unstable and will crash within a few hours. MacOS Ventura M1 chip. Process: com.docker.vpnkit [83335] Date/Time: 2023-01-29 14:21:00.3111 +0700 Sleep/Wake UUID: 81387B5F-3B7F-437A-9013-A45406AF3DB3 Time Awake Since Boot: 1200000 seconds System Integrity Protection: enabled Crashed Thread: 3 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 VM Region Info: 0x149000000 is not in any region. Bytes after previous region: 1 Bytes before following region: 115343360 |
latest update seems to have fixed this for me anyway.. |
Not true for me unfortunately, I tried 4.16.2 yesterday and received the same crash report. |
Wanted to add that I've been having this issue intermittently for some time, as have a few other people at work, and it's super disruptive. Same segfault and implicated code (this from a few minutes ago on latest versions):
going back to 4.12.0 to see if that helps. Even an update to determine that vpnkit is not running and restart it would be nice so it wouldn't just spin forever trying to start/stop. |
Confirmed as well. Docker crashes once every 4-6 hours with this exact issue
|
I upgraded to 4.17.0 a few days ago and I don't seem to have any further issues, usually it would crash by now. Can anyone else confirm this? |
Hopefully Apple sends you crash reports.
Docker for Mac 4.13.0 (89412) on my recently upgraded Monterrey macOS started getting frequent SIGSEGV crashes.
FortiClient and Sophos are also running.
Let me know if you need fuller details.
The text was updated successfully, but these errors were encountered: