Crash in [@ CoreFoundation@0x1b2c0f]
Categories
(Core :: Audio/Video: Playback, defect, P3)
Tracking
()
People
(Reporter: mattwoodrow, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/defdca86-d176-4f5d-9809-48d830210216
Reason: EXC_BAD_INSTRUCTION / EXC_I386_INVOP
Top 10 frames of crashing thread:
0 CoreFoundation CoreFoundation@0x1b2c0f
1 CoreFoundation CoreFoundation@0x1a1d62
2 CoreFoundation CoreFoundation@0x1a27b2
3 CoreFoundation CoreFoundation@0x1a3539
4 CoreFoundation CoreFoundation@0x1a4940
5 libxpc.dylib libxpc.dylib@0xc9bf
6 libxpc.dylib libxpc.dylib@0xb77e
7 libdispatch.dylib libdispatch.dylib@0x3025
8 libdispatch.dylib libdispatch.dylib@0x1aaff
9 libdispatch.dylib libdispatch.dylib@0x8c46
RDD process is crashing on startup for jya.
The stacks appear to be confused, but I think it might be crashing trying to set the process name. Possibly an issue with the sandbox?
Updated•4 years ago
|
Reporter | ||
Comment 1•4 years ago
|
||
Haik, does this look like a sandbox problem?
Comment 2•4 years ago
|
||
(In reply to Matt Woodrow (:mattwoodrow) from comment #1)
Haik, does this look like a sandbox problem?
Possibly. I have not been able to reproduce this problem so any more information we could get would be helpful. If the RDD problem is reproducible, testing with MOZ_DISABLE_RDD_SANDBOX=1 would disable the RDD sandbox and let us rule out or confirm sandboxing involvement:
$ MOZ_DISABLE_RDD_SANDBOX=1 /Applications/Firefox.app/Contents/MacOS/firefox
At the time of the crash, the main thread (not the crashing thread) is calling SetProcessName() and we've just seen a new bug popup where the crashing thread is calling SetProcessName(). That is bug 1689626.
Comment 3•4 years ago
|
||
Closing because no crashes reported for 12 weeks.
Description
•