Firefox Nightly keeps crashing when opened (latest version/2024-07-10)
Categories
(Firefox :: Shell Integration, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox128 | --- | unaffected |
firefox129 | --- | unaffected |
firefox130 | + | fixed |
People
(Reporter: ctanase, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
I've updated FF Nightly today and after restarting the PC it keept crashing when trying to open.
Regression range: good: 2024-07-09 / bad: 2024-07-10
Regression pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=da6255a8842052aee7d8b728b4af0b98a6cbc30e&tochange=0e3d86bfb0ea9b8cdccbe92755ba98b43b5e992d
Reporter | ||
Comment 1•5 months ago
|
||
Comment 2•5 months ago
|
||
Based on that pushlog, it seems like the most likely regressor is the backout of bug 1904436?
Comment 3•5 months ago
|
||
:nshukla, since you are the author of the regressor, bug 1904436, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Comment 4•5 months ago
|
||
[Tracking Requested - why for this release]: repeated startup crash regression sounds bad. Given the regression window, maybe the browser is in some weird state that won't happen for real browsers but it would be good to figure out what is going wrong here.
Comment 5•5 months ago
|
||
I can't personally make much sense out of what's happening with this crash report. The code that was backed out set the AppUserModelId incorrectly, which in itself caused crashes in certain cases, but I can't tell why backing it out would cause problems. Nothing there should be persistent across launches. You may have already done this, but does a system restart fix the problem?
Reporter | ||
Comment 6•5 months ago
|
||
It works now with 2024-07-11 update. Only with the 2024-07-10 version I had issues regardless what I was doing (system restart, new profile), 2024-07-09 was also fine.
Comment 7•5 months ago
|
||
Well, Bug 1904436 was merged on the 2024-07-10 and backed out the same day. I'm satisfied that this was caused by Bug 1904436 and fixed by its back out.
Updated•5 months ago
|
Description
•