Skip to content
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

Docker random crash since last update #6539

Closed
3 tasks done
ptmplop opened this issue Oct 27, 2022 · 5 comments
Closed
3 tasks done

Docker random crash since last update #6539

ptmplop opened this issue Oct 27, 2022 · 5 comments

Comments

@ptmplop
Copy link

ptmplop commented Oct 27, 2022

  • I have tried with the latest version of Docker Desktop
  • I have tried disabling enabled experimental features
  • I have uploaded Diagnostics

Expected behavior

Docker should run reliably without crash

Actual behavior

Docker will randomly crash and produce error in crash report logs (console) which I will attach for reference,
As an outline of the problem...

Process: com.docker.vpnkit [1675]
Path: /Applications/Docker.app/Contents/Resources/bin/com.docker.vpnkit
Identifier: com.docker.vpnkit
Version: ???
Code Type: ARM-64 (Native)
Parent Process: com.docker.backend [803]
Responsible: Docker [795]
User ID: 502
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000128000000
Exception Codes: 0x0000000000000001, 0x0000000128000000
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [1675]

Information

  • Is it reproducible?
    Yes as it will crash regularly however I can't give clear instructions on how to reproduce it on another environment.

  • Is the problem new?
    Seems to have appeared since the last Docker update, unsure of previous version.

  • Did the problem appear with an update?
    Yes, seems to have appeared in 4.13.0 (89412).

  • macOS Version: 13.0 (22A380) - However this was also a problem in the latest release of Monterey.

  • Intel chip or Apple chip: M1 Max

  • Docker Desktop Version: 4.13.0 (89412)

@ptmplop
Copy link
Author

ptmplop commented Oct 27, 2022

crash.txt

@ptmplop
Copy link
Author

ptmplop commented Oct 27, 2022

Thank you for a confirmation of the problem, I will roll back to 4.12.

@ptmplop ptmplop closed this as completed Oct 27, 2022
@ptmplop
Copy link
Author

ptmplop commented Jan 29, 2023

Opening this again as I am still experiencing the same issues on the latest releases,

It's worth noting that the last stable release for me was 4.12, all versions since have been crashing regularly.

Process: com.docker.vpnkit [83335]
Path: /Applications/Docker.app/Contents/Resources/bin/com.docker.vpnkit
Identifier: com.docker.vpnkit
Version: ???
Code Type: ARM-64 (Native)
Parent Process: com.docker.backend [83202]
Responsible: Docker [82993]
User ID: 502

Date/Time: 2023-01-29 14:21:00.3111 +0700
OS Version: macOS 13.1 (22C65)
Report Version: 12
Anonymous UUID: 3719BD85-559E-D5E2-8219-C52BA5B0EC42

Sleep/Wake UUID: 81387B5F-3B7F-437A-9013-A45406AF3DB3

Time Awake Since Boot: 1200000 seconds
Time Since Wake: 3590 seconds

System Integrity Protection: enabled

Crashed Thread: 3

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000149000000
Exception Codes: 0x0000000000000001, 0x0000000149000000

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [83335]

VM Region Info: 0x149000000 is not in any region. Bytes after previous region: 1 Bytes before following region: 115343360
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
MALLOC_SMALL 148800000-149000000 [ 8192K] rw-/rwx SM=PRV
---> GAP OF 0x6e00000 BYTES
MALLOC_TINY 14fe00000-14ff00000 [ 1024K] rw-/rwx SM=PRV

@ptmplop ptmplop reopened this Jan 29, 2023
@ptmplop
Copy link
Author

ptmplop commented Jan 30, 2023

Looks like a duplicate ticket with docker/for-mac/issues/6539

@docker-robott
Copy link
Collaborator

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 30 days.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants