Crash in [@ round]
Categories
(Toolkit :: Crash Reporting, defect, P3)
Tracking
()
People
(Reporter: jseward, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug is for crash report bp-5d69e0ac-1d14-4a43-a2ad-fa6ce0190412.
In the Windows nightlies for 2019 April 11 there are around 10 crashes
in 3 different installations, that (1) have |round| at or near the
innermost stack frame, and (2) look like they might involve memory
corruption (EXCEPTION_ACCESS_VIOLATION_WRITE, EXCEPTION_ACCESS_VIOLATION_EXEC).
Apart from that I failed to see any pattern in the stacks from which
I could guess the component/subsystem involved. Most of the stacks
are useless -- only two frames. The two reports with actual stacks
are
https://crash-stats.mozilla.com/report/index/5d69e0ac-1d14-4a43-a2ad-fa6ce0190412
https://crash-stats.mozilla.com/report/index/5496689f-c6a1-4fb6-b46b-b714a0190414
and even those don't make any sense to me. Note that there's stack
scanning involved, so the stacks might be unreliable.
Top 10 frames of crashing thread:
0 xul.dll round
1 xul.dll void mozilla::BRFrame::~BRFrame layout/generic/BRFrame.cpp:87
2 xul.dll nsFrame::DestroyFrom layout/generic/nsFrame.cpp:857
3 xul.dll nsLineBox::DeleteLineList layout/generic/nsLineBox.cpp:372
4 xul.dll nsBlockFrame::DestroyFrom layout/generic/nsBlockFrame.cpp:328
5 xul.dll nsLineBox::DeleteLineList layout/generic/nsLineBox.cpp:372
6 xul.dll nsBlockFrame::DestroyFrom layout/generic/nsBlockFrame.cpp:328
7 xul.dll nsBlockFrame::DestroyFrom layout/generic/nsBlockFrame.cpp:325
8 xul.dll nsLineBox::DeleteLineList layout/generic/nsLineBox.cpp:372
9 xul.dll nsBlockFrame::DestroyFrom layout/generic/nsBlockFrame.cpp:328
| Reporter | ||
Comment 1•6 years ago
|
||
Andrew, any idea how to classify this better?
Comment 2•6 years ago
|
||
I have no idea. It seems like the stack walking is just producing a junky result sometimes, given how unrelated the two crashes with stacks are.
Updated•6 years ago
|
Comment 3•6 years ago
|
||
Stacks don't appear too useful for analysis. Unhiding for broader view
Updated•6 years ago
|
Comment 4•6 years ago
|
||
I looked at a handful of crashes and the stacks are all over the place. It's likely these are memory corruptions crashes. With a bit of luck - if something comes out of this year's helpful crash reporter GSoC - we'll be able to identify them as such soon.
Comment 5•3 years ago
|
||
Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.
For more information, please visit auto_nag documentation.
Comment 6•1 year ago
|
||
Closing because no crashes reported for 12 weeks.
Description
•