Closed Bug 1553787 Opened 5 years ago Closed 5 years ago

Extensions are not working after some processes have been killed

Categories

(WebExtensions :: General, defect)

68 Branch
Desktop
Windows
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1355239

People

(Reporter: kolan_n, Unassigned)

Details

User Agent: Mozilla/5.0 (Android 6.0; Mobile; rv:59.0) Gecko/20100101 Firefox/59.0

Steps to reproduce:

1 Open Google with NoScript and uMatrix prohibiting it to execute JS
2 start killing child Firefox processes

Actual results:

  1. After some processes killed Google have managed to execute JS.
  2. This is permanent. All other sites also can execute JS.

Expected results:

All the extensions must keep working

OS: Unspecified → Windows
Hardware: Unspecified → Desktop
Version: 59 Branch → 68 Branch

This is permanent. All other sites also can execute JS.

Untill the briwser is restarted.

Hi, I tried to reproduce this issue but without any success, I added the 2 extensions but I am just not that familiar with them. Ill set the component for it and maybe one of our Devs might know what the problem is. I'm not sure if Javascript engine is the correct component for it but it seems like a good place to start, Please change it to a more suitable component if its not correct.

Component: Untriaged → JavaScript Engine
Product: Firefox → Core
Component: JavaScript Engine → General
Product: Core → WebExtensions
Version: 68 Branch → Firefox 68
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Version: Firefox 68 → 68 Branch
You need to log in before you can comment on or make changes to this bug.