This is a read-only archive of the Mumble forums.

This website archives and makes accessible historical state. It receives no updates or corrections. It is provided only to keep the information accessible as-is, under their old address.

For up-to-date information please refer to the Mumble website and its linked documentation and other resources. For support please refer to one of our other community/support channels.

Jump to content

Mumble 1.2.9 crashes on launch under Mac OS Mojave


MBoland
 Share

Recommended Posts

Latest mumble download.

Mumble crashes on launch.

Error reporter also crashes with "This really isn't funny, but apparently there's a bug in the crash reporting code, and we've failed to upload the report. You may inform a developer about error 3".


From crash reporter:

Process: Mumble [11301]

Path: /Applications/Mumble.app/Contents/MacOS/Mumble

Identifier: net.sourceforge.mumble.Mumble

Version: 1.2.19

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Mumble [11301]

User ID: 501


Date/Time: 2018-07-10 09:16:10.896 +1000

OS Version: Mac OS X 10.14 (18A326h)

Report Version: 12

Anonymous UUID: D11B06CF-C0DE-5370-97B2-CE246A81EC7F



Time Awake Since Boot: 270000 seconds


System Integrity Protection: disabled


Crashed Thread: 0 Dispatch queue: com.apple.main-thread


Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000038

Exception Note: EXC_CORPSE_NOTIFY


Termination Signal: Segmentation fault: 11

Termination Reason: Namespace SIGNAL, Code 0xb

Terminating Process: exc handler [11301]


VM Regions Near 0x38:

-->

__TEXT 0000000100000000-0000000101bd9000 [ 27.8M] r-x/rwx SM=COW /Applications/Mumble.app/Contents/MacOS/Mumble


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread


and a whole lot more

Edited by MBoland
Link to comment
Share on other sites

After the initial error report I now get "This really isn't funny, but apparently there's a bug in the crash reporting code, and we've failed to upload the report. You may inform a developer about error 299"


Does anyone know what the error 299 is all about?


Does anyone know if there is a fix in the works or even if dev's are aware of this?

Link to comment
Share on other sites

 Share

×
×
  • Create New...