In my experiments enabling these aggressive memory allocation checks makes the Docker UI rather sluggish (not completely unusable, but not great) however interactions with the docker daemon via the CLI ( docker run, docker build etc) are not effected so things remain usable for doing actual work. Run /Applications/Docker.app/Contents/Resources/bin/docker-diagnose -u (again adjust if not installing to /Applications/Docker.app) and post the output here attaching $HOME/docker-malloc.log at the same time.Continue to use Docker as usual until you next observe the issue.Run MallocLogFile=docker-malloc.log MallocScribble=1 MallocCheckHeapStart=1 MallocCheckHeapEach=1 MallocCheckHeapAbort=1 /Applications/Docker.app/Contents/MacOS/Docker (if you have installed other than to /Applications/Docker.app then adjust as appropriate).Exiting Docker for Mac (Chose Quit from the Whale menu).It would be useful if you could each run Docker for Mac with additional checks in the Macos memory allocator enabled. Since the issue you are all seeing appears to be a use-after-free we only get a crash when the corruption eventually surfaces elsewhere in the code base, which makes it rather tricky to track down. Thanks for your various reports, I believe has consolidated them all here so I'll just post this here.
