Skip to content

Memory corruption errors from Docker #2020

Open
@damienmckenna

Description

@damienmckenna

Describe the bug

In the past few weeks I've started getting these errors every few days:

panic(cpu 11 caller 0xffffff8016f92bb5): Possible memory corruption: pmap_pv_remove(0xffffff9539450080, 0x7ff84582d000, 0x80, 0x80000, 0xffffffd0f9053ba4, 0xfffffe9262f30168): pv not on hash, head: 0xffffff953af19a80, 0x19b025000, priors: 2 @pmap_internal.h:979
Panicked task 0xffffff8ba11d4bf8: 1 threads: pid 34366: docker

It typically happens when the computer is unattended running overnight. When this happens the mutagen instance associated with ddev-managed Docker containers ends up corrupt and I have to destroy all Docker data and start over.

To Reproduce

Unknown.

Expected behavior

Docker doesn't crash with memory-corruption errors.

Diagnostic report (REQUIRED)

OrbStack info:
Version: 1.11.3
Commit: fc21fa7866a51675a381a1612c39e06918559d09 (v1.11.3)

System info:
macOS: 13.7.6 (22H625)
CPU: amd64, 16 cores
CPU model: Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Model: MacBookPro16,1
Memory: 32 GiB

Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2025-06-28T12-10-40.490208Z.zip

Screenshots and additional context (optional)

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    t/bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions