std::bad_alloc crash on macOS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
New
|
Critical
|
Unassigned |
Bug Description
Process: mixxx [928]
Path: /Applications/
Identifier: org.mixxx.mixxx
Version: 2.3.1 (2.3.1)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: mixxx [928]
User ID: 501
Date/Time: 2021-10-27 18:32:29.872 +0200
OS Version: macOS 11.6 (20G165)
Report Version: 12
Bridge OS Version: 6.0 (19P50284g)
Anonymous UUID: DB838A04-
Please read the attachment file.
Time Awake Since Boot: 7600 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
abort() called
terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
summary: |
- crasch + std::bad_aloc crash on MacOs |
tags: | added: crash macos |
summary: |
- std::bad_aloc crash on MacOs + std::bad_alloc crash on MacOs |
Changed in mixxx: | |
importance: | Undecided → Critical |
summary: |
- std::bad_alloc crash on MacOs + std::bad_alloc crash on macOS |
Can you remember what you was trying to do when the crash happens? Was this only a single occourance or did this happen more often.
Do you have an idea what could be caused the issue?
This one might be related: https:/ /bugs.launchpad .net/mixxx/ +bug/1944512
std::alloc is a hint for an out of memory situation or a memory fault.
Does Mixxx continuously require more memory? Please compare the memory consumption using Activity Monitor. After restart Mixxx and after let's say one hour usage.
Is there a significant difference?