Crash in [@ XUL@0x333dc03 | XUL@0x3ea067 | XUL@0x333df56 | XUL@0xf4725a | XUL@0xf4693b | XUL@0x157e6ba | XUL@0xf46a3d | XUL@0xf4648c | XUL@0x3f543c | XUL@0xf44f2c | XUL@0x3bce0cf | XUL@0xf46a89 | XUL@0x55e3b8 | XUL@0x55dcff | XUL@0x14aab1e | XUL@0x2fbf...
Categories
(Core :: General, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox80 | --- | wontfix |
People
(Reporter: emilghitta, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug is for crash report bp-b31aee9d-25af-402b-a402-8cd200200729.
Top 10 frames of crashing thread:
0 XUL XUL@0x333dc03
1 XUL XUL@0x3ea067
2 XUL XUL@0x333df56
3 XUL XUL@0xf4725a
4 XUL XUL@0xf4693b
5 XUL XUL@0x157e6ba
6 XUL XUL@0xf46a3d
7 XUL XUL@0xf4648c
8 XUL XUL@0x3f543c
9 XUL XUL@0xf44f2c
Unfortunately I don't have some reliable STR at the moment. I've left my pc in sleep mode overnight (Firefox 80.0b1 was still open before entering in sleep mode). After exiting from sleep mode I closed Firefox via the Hamburger menu which lead to a browser crash.
I will investigate this further and update this bug's description once I find some reliable STR.
Note
I'm not sure if this is the right component for this issue. Please feel free to change this if necessary.
Comment 1•4 years ago
|
||
I think those XUL@0x... symbols just means that Socorro failed to resolve the libxul addresses to a name.
So this crash could be about anything...
Comment 2•4 years ago
|
||
Emil: Has this happened to you again since the initial report?
If not, I think we should close as INVALID for now since the crash report is not actionable as-is.
Comment 3•4 years ago
|
||
Sorry, did not mean to close yet until confirmation from initial reporter.
Reporter | ||
Comment 4•4 years ago
|
||
I tried to reproduce this crash several times each day after exiting sleep mode but couldn't.
It may have been a one time crash. I'll keep an eye on this one and will reopen the issue if this happens again and if some reliable steps are found.
Updated•4 years ago
|
Description
•