Closed
Bug 243540
Opened 20 years ago
Closed 19 years ago
Testcase (exploit ?) leaks 2MB/sec and hang Mozilla
Categories
(SeaMonkey :: General, defect)
SeaMonkey
General
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: wolruf, Unassigned)
References
()
Details
(Keywords: hang, testcase)
Attachments
(1 file)
276 bytes,
text/html
|
Details |
Build ID: 20040513 on Win2k & 20040512 on Linux. Steps to reproduce: 1. Load testcase, 2. Mozilla memory usage grows 2MB/sec and CPU is at 99%
Reporter | ||
Comment 1•20 years ago
|
||
while(true) JavaScript running unbounded.
Assignee: general → general
Component: Browser-General → JavaScript Engine
QA Contact: general → pschwartau
Comment 3•20 years ago
|
||
I wonder why the branch callback is not catching this...
Comment 4•20 years ago
|
||
The callback will actually kill it if you wait long enough. It's spending an enormous amount of time in editor+txmgr+layout each time it goes out from js. There's less than 100 callbacks/second in an optimized build on a fast machine. We maybegc every 4k callbacks and then cut it off at 64k callbacks which is the first time the callback timer is checked.
It's the embedded Ctrl-U that's making mozilla eat memory. Remove it and mozilla just spins for a while before it asks it it should kill the script.
Comment 6•20 years ago
|
||
So back to browser-general? This was never JS engine. /be
Component: JavaScript Engine → Browser-General
QA Contact: pschwartau → general
Updated•20 years ago
|
Product: Browser → Seamonkey
Reporter | ||
Comment 7•19 years ago
|
||
Script is caught by the warning 'Unresponsive script' on both Camino 0.9a2 and Firefox Deep Park alpha 2. Marking WFM.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•