Open
Bug 1272019
Opened 8 years ago
Updated 2 years ago
Can get into a situation where slow-script notification bar cannot stop script
Categories
(Core :: DOM: Content Processes, defect, P3)
Core
DOM: Content Processes
Tracking
()
NEW
Tracking | Status | |
---|---|---|
e10s | - | --- |
People
(Reporter: mconley, Unassigned)
Details
(Whiteboard: btpp-backlog)
STR: 0) Ensure e10s is enabled by default. 1) Enable tracking protection for all sites. 2) Brace yourself, because this next step is going to kill your browser 3) Visit http://www.healthline.com/health/food-nutrition/is-silicon-dioxide-in-supplements-safe 4) Scroll down a bit 5) Wait for the slow-script notification bar to appear. 6) Click on "Stop It" ER: The page should become responsive again because I stopped the script. AR: The page continues to spin and consume more and more memory. The notification bar will continue to appear every few seconds, despite me clicking "Stop It" every time.
Reporter | ||
Updated•8 years ago
|
tracking-e10s:
--- → ?
What happens in non-e10s? It's pretty easy for a page to defeat the slow script killer since we only shut down one script. Example: setInterval(function { ... do something that takes 10 seconds ...}, 0);
(In reply to Bill McCloskey (:billm) from comment #1) > What happens in non-e10s? It's pretty easy for a page to defeat the slow > script killer since we only shut down one script. Example: > > setInterval(function { ... do something that takes 10 seconds ...}, 0); While it's still not difficult, I did fix that specific case in Bug 1252268.
Updated•8 years ago
|
Updated•8 years ago
|
Whiteboard: btpp-backlog
Updated•6 years ago
|
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•