Closed
Bug 1711634
Opened 3 years ago
Closed 3 years ago
Crash in [@ AsyncShutdownTimeout | profile-before-change | PageThumbs: removing all thumbnails]
Categories
(Firefox :: New Tab Page, defect)
Tracking
()
RESOLVED
FIXED
90 Branch
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox88 | --- | unaffected |
firefox89 | --- | unaffected |
firefox90 | --- | fixed |
People
(Reporter: gsvelto, Assigned: emmamalysz)
References
(Regression)
Details
(Keywords: crash, regression)
Crash Data
Attachments
(1 file)
Crash report: https://crash-stats.mozilla.org/report/index/e198be42-0c27-4aef-bdff-764930210518
MOZ_CRASH Reason: MOZ_CRASH()
Top 6 frames of crashing thread:
0 mozglue.dll mozglue.dll@0x46645
1 ucrtbase.dll <unknown in ucrtbase.dll>
2 ucrtbase.dll <unknown in ucrtbase.dll>
3 xul.dll xul.dll@0x892ae7
4 ucrtbase.dll <unknown in ucrtbase.dll>
5 xul.dll xul.dll@0x514beef
This is a potential regression from bug 1649602. It seems that the shutdown procedure for PageThumb.jsm became a lot slower since that patch landed and it's now frequently causing shutdown hangs in the nightly channel. Emma could you have a look?
Severity: -- → S2
Comment 1•3 years ago
|
||
Set release status flags based on info from the regressing bug 1649602
status-firefox88:
--- → unaffected
status-firefox89:
--- → unaffected
status-firefox90:
--- → affected
status-firefox-esr78:
--- → unaffected
Updated•3 years ago
|
Flags: needinfo?(emalysz)
Assignee | ||
Comment 2•3 years ago
|
||
Updated•3 years ago
|
Assignee: nobody → emalysz
Status: NEW → ASSIGNED
Assignee | ||
Updated•3 years ago
|
Flags: needinfo?(emalysz)
Pushed by emalysz@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a400e87a7082 reduce number of AsyncShutdownTimeout crashes from PageThumbs r=barret
Comment 4•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 90 Branch
Updated•3 years ago
|
Has Regression Range: --- → yes
Updated•3 months ago
|
Flags: qe-verify-
You need to log in
before you can comment on or make changes to this bug.
Description
•