Closed Bug 1811640 Opened 2 years ago Closed 1 year ago

Crash in [@ pthread_kill | abort | _SCSessionUniverseByUIDAcquireAndLock.cold.2]

Categories

(Core :: Widget: Cocoa, defect, P3)

defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mccr8, Unassigned)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/83d013fd-1242-43bc-bb9e-5958d0230120

Reason: EXC_SOFTWARE / SIGABRT

Top 10 frames of crashing thread:

0  libsystem_kernel.dylib  mach_msg_trap  
1  libsystem_kernel.dylib  mach_msg  
2  XUL  google_breakpad::ReceivePort::WaitForMessage  toolkit/crashreporter/google-breakpad/src/common/mac/MachIPC.mm:249
3  XUL  google_breakpad::CrashGenerationClient::RequestDumpForException  toolkit/crashreporter/breakpad-client/mac/crash_generation/crash_generation_client.cc:68
4  XUL  google_breakpad::ExceptionHandler::WriteMinidumpWithException  toolkit/crashreporter/breakpad-client/mac/handler/exception_handler.cc:466
5  XUL  google_breakpad::ExceptionHandler::SignalHandler  toolkit/crashreporter/breakpad-client/mac/handler/exception_handler.cc:725
6  libsystem_platform.dylib  _sigtramp  
7  libsystem_kernel.dylib  __pthread_kill  
8  libsystem_pthread.dylib  pthread_kill  
9  libsystem_c.dylib  abort  

I'm not sure what to make of this crash, but there are a decent number of them. They seem to have "Mac Crash info" where the "message" starts with "Could not establish connection to coreservicesd. Err=(os/kern) successful", and the "module" is "/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore". There's some stuff in the correlations but I can't tell how much of it is the usual Mac stuff.

There are a few reports online of similar crashes in other applications, such as https://github.com/vlaci/openconnect-sso/issues/23. From the bug report:

"There is a known condition within OSX where calling fork in certain situations is prohibited. Normally this can be overridden by setting export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES as described on StackOverflow and other places."

The severity field is not set for this bug.
:spohl, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(spohl.mozilla.bugs)
Severity: -- → S3
Flags: needinfo?(spohl.mozilla.bugs)
Priority: -- → P3

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.