Closed Bug 2056926 Opened 1 month ago Closed 1 month ago

Paper over partial update issues causing startup crashes when loading UA stylesheets.

Categories

(Core :: CSS Parsing and Computation, defect)

defect

Tracking

()

RESOLVED FIXED
155 Branch
Tracking Status
firefox-esr153 --- fixed
firefox153 --- fixed
firefox154 --- fixed
firefox155 --- fixed

People

(Reporter: emilio, Assigned: emilio)

References

Details

Attachments

(3 files)

No description provided.

See the comment for reasoning, and bug 1681745 for context.

Not a fan in many ways, since this is likely to cause wrong rendering at
best, and random crashes later down the line at worst. But at least I
add the crash reporter annotation message, if we then crash later down
the line...

Tested manually by removing select.css from my objdir and using the
non-nightly codepath.

Attachment #9614495 - Attachment description: Bug 2056926 - Paper over bug 1681745. r=#style! → Bug 2056926 - Paper over bug 1681745 / bug 1941972. r=#style!
Status: ASSIGNED → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 155 Branch

ni=emilio to request uplift, since I think we're trying to get this into a dot-release

(maybe you were wanting to add a bit more before doing so -- but maybe this is still independently worth uplifting on its own?)

Flags: needinfo?(emilio)

(In reply to Emilio Cobos Álvarez [:emilio] from comment #1)

Not a fan in many ways, since this is likely to cause wrong rendering at
best, and random crashes later down the line at worst.

To get an idea of how bad this might end up for users who would otherwise have crashed: I tested the same franken-build situation from earlier releases (v152.0 with v151 final-dot-release omni.ja, and v151.0 with v150 final-dot-release omni.ja), and indeed, both technically launch but are terribly unusable.

However, the v151.0-with-v150-omni.ja franken-build was at least able to self-update (and help|about successfully kicked that off, even if the rest of the UI was pretty broken). So the potential for that self-update lifeline is a vote in favor of taking this and avoiding the startup-crash, in the hopes that users who end up in this situation in the future will have a way that their Firefox installations might get back to working (via later self-updates)

Blocks: 2057731

See the comment for reasoning, and bug 1681745 + bug 1941972 for
context.

Not a fan in many ways, since this is likely to cause wrong rendering at
best, and random crashes later down the line at worst. But at least I
add the crash reporter annotation message, if we then crash later down
the line...

Tested manually by removing select.css from my objdir and using the
non-nightly codepath.

Original Revision: https://phabricator.services.mozilla.com/D313486

Attachment #9615943 - Flags: approval-mozilla-beta?

firefox-beta Uplift Approval Request

  • User impact if declined/Reason for urgency: Wallpaper for bug 1681745.
  • Code covered by automated testing?: no
  • Fix verified in Nightly?: no
  • Needs manual QE testing?: no
  • Steps to reproduce for manual QE testing:
  • Risk associated with taking this patch: low
  • Explanation of risk level: Avoids assuming that the omnijar contains the file we expect.
  • String changes made/needed?: none
  • Is Android affected?: yes

See the comment for reasoning, and bug 1681745 + bug 1941972 for
context.

Not a fan in many ways, since this is likely to cause wrong rendering at
best, and random crashes later down the line at worst. But at least I
add the crash reporter annotation message, if we then crash later down
the line...

Tested manually by removing select.css from my objdir and using the
non-nightly codepath.

Original Revision: https://phabricator.services.mozilla.com/D313486

Attachment #9615944 - Flags: approval-mozilla-release?

firefox-release Uplift Approval Request

  • User impact if declined/Reason for urgency: Wallpaper for bug 1681745.
  • Code covered by automated testing?: no
  • Fix verified in Nightly?: no
  • Needs manual QE testing?: no
  • Steps to reproduce for manual QE testing:
  • Risk associated with taking this patch: low
  • Explanation of risk level: Avoids assuming that the omnijar contains the file we expect.
  • String changes made/needed?: none
  • Is Android affected?: yes

Yeah I wanted to do bug 2057731 as well as per Gijs' request.

Flags: needinfo?(emilio)
Attachment #9615943 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Attachment #9615944 - Flags: approval-mozilla-release? → approval-mozilla-release+
QA Whiteboard: [qa-triage-done-c155/b154]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: