1759001 - Firefox 98 crashes with sidebar [@ mozilla::dom::XULTreeElement::GetCoordsForCellItem]

Status: RESOLVED WORKSFORME

(Core :: XUL, defect)

Description

[jcc]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:98.0) Gecko/20100101 Firefox/98.0

Steps to reproduce:

Clicked any of the bookmarks in the sidebar, or any of the history entries

I also refreshed firefox and tried again; still happened

Actual results:

Firefox crashed, every time I did this. Multiple 'crash reports' went to mozilla about this

Expected results:

the link should have opened

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Firefox::Bookmarks & History' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Mark Banner (:standard8)]

Please can you enter about:crashes in the address bar, and then copy and paste some of the crash ids here? That will help us identify the cause of the crash.

Comment 3

[jcc]

Here are the crash ids from this morning, following the updates that were pushed out to us yesterday (Wednesday is mass reboot day for us).

ba359b47-288b-42eb-a536-1cc3d7057c45 3/10/2022, 8:10 AM
a54876d8-0174-4d3b-b117-477596782bf6 3/10/2022, 7:30 AM
28784f4b-e173-4e53-b82f-394d1d3317d2 3/10/2022, 7:27 AM
d7566a47-0ae6-4902-ac09-1db40a38ea4b 3/10/2022, 7:26 AM
a06a9379-f061-405e-bb94-e11dc807b247 3/10/2022, 7:03 AM

Comment 4

[Mark Banner (:standard8)]

Unfortunately they don't seem to be found on the crash reporting system. Did it say they were submitted? Normally they should have a "bp-" prefix.

Comment 5

[jcc]

Sorry, I should have scrolled down further to a different section. These submitted today before I gave up:

bp-867639d2-7a33-428e-9518-978830220310 3/10/2022, 7:11 AM
View
bp-5c8286a8-8222-4025-bd05-7c9220220310 3/10/2022, 7:07 AM
View
bp-5ca49f9d-97f6-47d7-962e-6e3650220310 3/10/2022, 7:04 AM
View

Comment 6

[Mark Banner (:standard8)]

Thank you for those reports. Where it is crashing we haven't changed recently, but it could be something else up that's triggering it. I'm going to move this across to Core: DOM for the teams there to take a look at.

Comment 7

[Olli Pettay [:smaug][[e-mail]]]

Hmm, the crash reason is EXCEPTION_PRIV_INSTRUCTION.
Isn't that quite unusual?

Comment 8

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:enndeakin, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 9

[BugBot [:suhaib / :marco/ :calixte]]

The bug has a crash signature, thus the bug will be considered confirmed.

Comment 10

[Neil Deakin]

Seems to have been an isolated issue.

Comment 11

[BugBot [:suhaib / :marco/ :calixte]]

Closing because no crashes reported for 12 weeks.