Closed Bug 1690748 Opened 4 years ago Closed 2 years ago

macOS 11 ARM Crash in [@ shutdownhang | __psynch_cvwait | _pthread_cond_wait]

Categories

(Core :: General, defect, P3)

Unspecified
macOS
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox98 --- affected

People

(Reporter: aryx, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/e2c037dc-2826-4807-844a-b2a400210203

MOZ_CRASH Reason: MOZ_CRASH(Shutdown hanging after all known phases and workers finished.)

Top 3 frames of crashing thread:

0 libsystem_kernel.dylib __psynch_cvwait 
1 libsystem_pthread.dylib _pthread_cond_wait 
2 libmozglue.dylib mozilla::detail::ConditionVariableImpl::wait mozglue/misc/ConditionVariable_posix.cpp:108

These stacks are really bad. I don't know if there's a known issue with stack walking. Maybe with better stacks this would turn into some existing shutdown hang.

Flags: needinfo?(gsvelto)

I have looked into the generated symbol files and how the stack walker is handling them but there isn't anything that's standing out: the CFI directives appear to be complete and the stack walker isn't encountering anything odd until the frame in mozglue. A normal stack frame of a crash like that on macOS should look like this though:

https://crash-stats.mozilla.org/report/index/f8d9239f-4e96-4d45-b320-cb0480210205

This is x86-64 while the issue here only seems to apply to AArch64 so there might be either a bug in CFI generated for that platform, a bug in the stackwalker or a bug in the debuginfo. I'll open a separate bug to investigate.

Flags: needinfo?(gsvelto)
See Also: → 1691020
Severity: -- → S3
Priority: -- → P3

For some reason, my problems only seemed to start with the update to 98.0

I have trouble loading the internet, then when I close firefox, it stalls & crashes :(

Here are my bug reports:

Closing because no crashes reported for 12 weeks.

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