1774283 - Extensions unresponsive in Firefox 103a

Status: RESOLVED WORKSFORME

(WebExtensions :: Untriaged, defect)

Description

[shapiro125]

Attachment: Screen Shot 2022-06-14 at 4.45.20 PM.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:103.0) Gecko/20100101 Firefox/103.0

Steps to reproduce:

Browse regularly for an amount of time (unknown amount of time)

Actual results:

Extensions no longer working nor responsive. For example, uBlock Origin no longer blocking and 1Password no longer filling.

When clicking on the extensions, they're a plain white screen.

Restarting works, but then they stop working again after a few minutes.

Expected results:

Extensions should work as expected.

Comment 1

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

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

Comment 2

[Alex Cornestean]

Hello,

I could not reproduce the issue on the latest Nightly (103.0a1/20220615214908), Beta (102.0b8/20220614185842) and Release (101.0.1/20220608170832) under Windows 10 x64 and Ubuntu 16.04 LTS.

As per the steps to reproduce mentioned in Comment 0, I’ve installed both uBlock Origin and 1Password and created an account for the latter. Immediately after install/logging in both extensions functioned properly and as such I’ve started regularly using the browsers for about 30-40 minutes. After the mentioned period has passed, I rechecked the extensions, which were still functioning as expected, were responsive and clicking the toolbar icons properly showed the pop-ups.

I’ll continue to investigate this, in case the 30-40 minutes of browsing were not enough for the issue to surface and update the report accordingly.

Thank you !

Comment 3

[shapiro125]

Thank you – it may have been an issue on my end. I haven't been able to reproduce it again, especially with later Nightly updates.

Comment 4

[Alex Cornestean]

Hello shapiro125,

Since you cannot reproduce the issue anymore on your end, I’ll be closing the report as WORKSFORME.

Please reopen the issue in case it surfaces again. Thank you !

Comment 5

[shapiro125]

Hello! I got the issue again.

1. I received a notification that my tab had crashed.
2. When I reloaded the tab, the extensions were unresponsive.

If this happens again, how do I send the crash report after the tab crash?

Comment 6

[Luca Greco [:rpl] [:luca] [:lgreco]]

Hi shapiro125,
you can

• open about:crashes
• confirm that the most recent crash has been submitted:
  • if it is not the most recent crash would be under the first "Unsubmitted Crash Reports", click the "Submit" button if it wasn't yet submitted
• then once successfully submitted, the crash is expected to be listed in the "Submitted Crash Reports" section
• clicking on the "View" link should open you that crash report in a new tab.

If you can share the link to the crash report in a new comment to this bug, that may help us to gather some more details useful to investigate the actual underlying issue.

Based on the details from comment 0, it seems likely that the crash may be an extension child process crash.

Comment 7

[shapiro125]

Attachment: Screen Shot 2022-06-22 at 8.53.16 AM.png

Comment 8

[shapiro125]

Thanks.

Unfortunately, there are no crashes in about:crashes when the tab crashes. Added a screenshot above.

Comment 9

[Luca Greco [:rpl] [:luca] [:lgreco]]

(In reply to shapiro125 from comment #8)

Thanks.

Unfortunately, there are no crashes in about:crashes when the tab crashes. Added a screenshot above.

Would you mind to look if in the BrowserConsole there is any log that is emitted around the time the issues you are experiencing are being triggered? that may help us to get some more details useful to pin point this

(make sure to open the BrowserConsole before triggering the bug and to enable the "Show Content Messaging" toggle button that is available in the gear menu on the top-right of the BrowserConsole window).

Comment 10

[shapiro125]

Of course, now I can't recreate it! closing it back. sorry about that.