Crash in [@ mozilla::dom::TimeoutManager::RescheduleTimeout]
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
People
(Reporter: sg, Unassigned)
References
Details
(Keywords: crash)
Crash Data
Maybe Fission related. (DOMFissionEnabled=1)
Crash report: https://crash-stats.mozilla.org/report/index/cd27b89d-a106-4ed1-a5b6-007960210109
MOZ_CRASH Reason: MOZ_DIAGNOSTIC_ASSERT(aLastCallbackTime <= aCurrentNow)
Top 10 frames of crashing thread:
0 XUL XUL@0xc617ba
1 XUL XUL@0xc60808
2 XUL XUL@0xc62672
3 XUL XUL@0x55df6e
4 XUL XUL@0x571ba4
5 XUL XUL@0x5556d0
6 XUL XUL@0x55971b
7 XUL XUL@0x564408
8 XUL XUL@0x77f9ed
9 XUL XUL@0x74e02f
The stack trace is garbled, but the diagnostic assertion is clearly coming from TimeoutManager::RescheduleTimeout.
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Comment 1•4 years ago
|
||
Since the signatures do not contain any readable function names, they are specific to a particular build.
Reporter | ||
Comment 2•4 years ago
|
||
Likely a duplicate of Bug 1671141.
Reporter | ||
Updated•4 years ago
|
Comment 3•4 years ago
|
||
(In reply to Simon Giesecke [:sg] [he/him] from comment #0)
Maybe Fission related. (DOMFissionEnabled=1)
Crash report: https://crash-stats.mozilla.org/report/index/cd27b89d-a106-4ed1-a5b6-007960210109
MOZ_CRASH Reason:
MOZ_DIAGNOSTIC_ASSERT(aLastCallbackTime <= aCurrentNow)
Top 10 frames of crashing thread:
0 XUL XUL@0xc617ba 1 XUL XUL@0xc60808 2 XUL XUL@0xc62672 3 XUL XUL@0x55df6e 4 XUL XUL@0x571ba4 5 XUL XUL@0x5556d0 6 XUL XUL@0x55971b 7 XUL XUL@0x564408 8 XUL XUL@0x77f9ed 9 XUL XUL@0x74e02f
The stack trace is garbled, but the diagnostic assertion is clearly coming from TimeoutManager::RescheduleTimeout.
FWIW, the build id 20201227234826 of that crash is older than this backout. This seems to be true for all signatures referenced above.
Reporter | ||
Comment 4•4 years ago
|
||
FWIW, the build id 20201227234826 of that crash is older than this backout. This seems to be true for all signatures referenced above.
Right. The reports are recent, but the build is rather old.
Gabriele, do you have an idea why the stack traces are not symbolized here?
Comment 5•4 years ago
|
||
I have to inspect the associated builds, let me have a look
Comment 6•4 years ago
|
||
Quite simply no symbol tasks were run for those builds which is really odd. I expected that the tasks would have ran and failed to generate symbols but that's not the case here; they didn't run at all. There might be an issue with the task definitions.
Comment 7•4 years ago
|
||
The diagnostic assertion is coming from TimeoutManager::RescheduleTimeout and per comment#3, close as a duplicated of bug 1671141.
Description
•