Shutdown crash with crash reporter when open new tab If you have opened a problematic page in the past

RESOLVED FIXED in Firefox 56

Status

()

Toolkit
WebExtensions: General
RESOLVED FIXED
6 months ago
6 months ago

People

(Reporter: Alice0775 White, Assigned: kmag)

Tracking

(Depends on: 1 bug, {crash, regression, reproducible})

56 Branch
mozilla56
x86_64
Windows 10
crash, regression, reproducible
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox-esr52 unaffected, firefox54 unaffected, firefox55 unaffected, firefox56 fixed)

Details

(Whiteboard: [DUPEME], crash signature, URL)

Comment hidden (obsolete)
Please provide your crash report ID: https://support.mozilla.org/kb/mozillacrashreporter
Component: Untriaged → Tabbed Browser
Comment hidden (obsolete)
(Reporter)

Comment 3

6 months ago
It seems to happen when the browser has hung up in the past.
And once you encounter this shutdown crash, it will be reproducible every time.

Exact STR is as follows.

Steps To Reproduce:
[prepare]
prepare-1. Make sure, only the about:home tab is opened at the first startup
prepare-2. Open https://bugzilla.mozilla.org/attachment.cgi?id=8889101
           --- browser will hang up due to Bug 1383478
prepare-3. Kill Nightly process

1. Start Nightly
2. Open any link(such as about:newtab) in new tab
3. Exit browser

Actual Results:
Nightly process remains for long period.
And finally, crash reporter dialog pops up.
bp-37f5111f-e1ac-492a-9d29-eb75a0170723

Expected Results:
Nightly process should disappear immediately.
Exit normally without crash.
Crash Signature: Crash in AsyncShutdownTimeout | profile-change-teardown | Extension Shutdown: screenshots@mozilla.org (Firefox Screenshots)
Keywords: crash, reproducible
(Reporter)

Updated

6 months ago
Depends on: 1380267
Crash Signature: Crash in AsyncShutdownTimeout | profile-change-teardown | Extension Shutdown: screenshots@mozilla.org (Firefox Screenshots) → [@ AsyncShutdownTimeout | profile-change-teardown | Extension Shutdown: screenshots@mozilla.org (Firefox Screenshots) ]
(Reporter)

Comment 4

6 months ago
[Tracking Requested - why for this release]:

Regression window:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=876f6d3d160852f68d6da1ad7353d8934bf27e84&tochange=23c63ef286cc35e1e31aa6a9afcaf00d227bf9d6

Regressed by: 23c63ef286cc	Kris Maglione — Bug 1357486: Follow-up: Wait for extension shutdown before starting storage shutdown. r=rhelmer
Blocks: 1357486
status-firefox54: --- → unaffected
status-firefox55: --- → unaffected
status-firefox56: --- → affected
status-firefox-esr52: --- → unaffected
tracking-firefox56: --- → ?
Component: Tabbed Browser → WebExtensions: General
Keywords: regression
Product: Firefox → Toolkit
(Reporter)

Updated

6 months ago
Keywords: multiprocess
Summary: Shutdown crash when open new tab → Shutdown crash with crash reporter when open new tab
(Reporter)

Comment 5

6 months ago
attachment 8878851 [details] in Bug 1374013 does also trigger this problem as well as https://bugzilla.mozilla.org/attachment.cgi?id=8889101 of comment#3.
(Reporter)

Updated

6 months ago
Summary: Shutdown crash with crash reporter when open new tab → Shutdown crash with crash reporter when open new tab If you have opened a problematic page in the past
(Reporter)

Comment 6

6 months ago
I notice that huge memory and CPU usage before the crash reporter pops up.
(Reporter)

Comment 7

6 months ago
Bug 1383478 was fixed. So, please use url https://bugzilla.mozilla.org/attachment.cgi?id=8878851 for step prepare-2.
(Reporter)

Updated

6 months ago
Depends on: 1384094

Comment 8

6 months ago
Track 56+ as new regression.

Hi :kmag,
Can you help look at this issue?
tracking-firefox56: ? → +
Flags: needinfo?(kmaglione+bmo)
(Reporter)

Comment 9

6 months ago
Bug 1380267 fixes the crash
Status: NEW → RESOLVED
Last Resolved: 6 months ago
status-firefox54: unaffected → ---
status-firefox55: unaffected → ---
status-firefox56: affected → ---
status-firefox-esr52: unaffected → ---
tracking-firefox56: + → ---
Flags: needinfo?(kmaglione+bmo)
Resolution: --- → FIXED
Assignee: nobody → kmaglione+bmo
status-firefox54: --- → unaffected
status-firefox55: --- → unaffected
status-firefox56: --- → fixed
status-firefox-esr52: --- → unaffected
Target Milestone: --- → mozilla56
You need to log in before you can comment on or make changes to this bug.