[10.15] Crash report is not generated in about:crashes (on stronghold.co)
Categories
(Toolkit :: Crash Reporting, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox71 | --- | affected |
People
(Reporter: sbadau, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
21.86 KB,
image/png
|
Details |
Screen Shot 2019-09-05 at 14.50.46.png
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:71.0) Gecko/20100101 Firefox/71.0
Build ID: 20190904163258
macOS Catalina - version 10.15 Beta 7 (19A546d)
Steps to reproduce:
- Launch Nightly 71.0a1
- Go to https://stronghold.co/careers/
Actual results:
The tab crashes, the crash dialog appears incomplete and the report is not submitted at all in about:crashes.
Expected results:
The website is properly loaded and If any crash should occur, then the crash dialog is properly displayed, the crash report is submitted accordingly and can be seen in about:crashes.
Please note that if the crash is generated via about:crashparent or via about:crashcontent - then the crash dialog is properly displayed and the report can be seen after submission in about:crashes.
This issue not reproducible on Firefox 69 or on Firefox 70 beta 3.
This issue is not reproducible on Mac OS X 10.14.
|
Reporter | |
Updated•5 years ago
|
|
||
Comment 1•5 years ago
|
||
Wondering if this belongs in Toolkit | Crash Reporting instead of Widget | Cocoa. Adding a ni on Gabriele.
|
||
Comment 2•5 years ago
|
||
Definitely crash reporting. I'll have a look tomorrow.
|
|
||
Comment 3•5 years ago
|
||
I couldn't reproduce on Mojave, I'm installing the Catalina Beta update to see if I can reproduce the crash with that combination.
|
|
||
Comment 4•5 years ago
|
||
I could reproduce on Catalina. So the crash is Catalina-specific and might not be caused by Firefox. The lack of a crash report however is most likely our fault. Catalina is removing support for 32-bit applications and our exception handler still relies on 32-bit functionality in the kernel. I'll try with the fix for bug 1035892 applied and see if the issue goes away.
|
|
||
Comment 5•5 years ago
|
||
I did some further tests and the problem seems to be gone. The crash was most likely happening outside of our code and it's possible that the latest beta update to macOS Catalina fixed it. I'm closing this as it's not reproducing anymore.
Description
•