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 for Mac - DockerHelper crashes constantly #3470

NickLassondeAtLandmarkGlobal opened this issue Jan 16, 2019 · 7 comments


Copy link

commented Jan 16, 2019

After upgrading to Docker for Mac Edge, I repeatedly get a message that /Applications/ has crashed. Hitting "OK" dismisses the message, and it returns 10-60 seconds later. During this time, actual Docker images work fine.

  • I have tried with the latest version of my channel (Stable or Edge)
  • I have uploaded Diagnostics
  • Diagnostics ID: DD60E37F-FECD-45A7-B1F4-5742DE9C25BA/20190116182522

Expected behavior

DockerHelper will not constantly crash.

Actual behavior

DockerHelper does constantly crash.


  • macOS Version: 10.13.6

Diagnostic logs

The entire diagnostics window says:
Diagnose succeded
Yes, "succeded" is misspelled in the window. 

Steps to reproduce the behavior

  1. Upgrade to Docker Edge
  2. Reboot
  3. Wait 5-60 seconds
  4. See the "DockerHelper quit unexpectedly" dialog
  5. Dismiss the dialog
  6. Go to 3.

This comment has been minimized.

Copy link

commented Jan 20, 2019

same for me.
mpb 13" late 2011, 10.13.6, docker Edge.

DockerHepler constantly fails generating lots of crashrepots. It utilises almost all processor time to do that.
lldb trace for DockerHelper (exits with Illegal instruction: 4):

2019-01-20 13:32:59.281207+0300 DockerHelper[1347:67670] [] AppDelegate: launching...
Process 1347 stopped
* thread #1, queue = '', stop reason = EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
    frame #0: 0x0000000100010209 DockerHelper`DockerHelper.BundleConstants.init() -> DockerHelper.BundleConstants + 3177
DockerHelper`DockerHelper.BundleConstants.init() -> DockerHelper.BundleConstants:
->  0x100010209 <+3177>: ud2    
    0x10001020b <+3179>: xorps  %xmm0, %xmm0
    0x10001020e <+3182>: movaps %xmm0, -0x40(%rbp)
    0x100010212 <+3186>: movaps %xmm0, -0x50(%rbp)
Target 0: (DockerHelper) stopped.

Obviously fixed with stable channel.


This comment has been minimized.

Copy link

commented Jan 21, 2019

Same here. Diagnostics ID: A08352A3-67AF-415B-8504-58349D2BF71C/20190121093728


This comment has been minimized.

Copy link

commented Jan 22, 2019


thanks for your report. We are reproducing the issue and are currently investigating this.


This comment has been minimized.

Copy link

commented Jan 23, 2019

The issue has been identified and fixed. This will be released with next edge.


This comment has been minimized.

Copy link

commented Feb 28, 2019

LGTM. No more crashtascularity. Fixed & #3504


This comment has been minimized.

Copy link

commented Mar 6, 2019

For me, it still constantly crashes on the newest Docker Desktop (30090). It also utilizes 100% CPU all the time and makes Docker unusable.

Diagnostic ID: DEDC9D9C-D9C1-4EA3-AB00-A178B2480C31/20190306155150


This comment has been minimized.

Copy link

commented Jun 4, 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

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

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
7 participants
You can’t perform that action at this time.