Closed Bug 604690 Opened 14 years ago Closed 13 years ago

Firefox hangs when working with CPU hog scripts

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
VERIFIED DUPLICATE of bug 516752

People

(Reporter: Virtual, Unassigned)

References

(
URL
)

Details

(Keywords: nightly-community) 

User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:2.0b8pre) Gecko/20101015 Firefox/4.0b8pre
Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b8pre) Gecko/20101015 Firefox/4.0b8pre

Just go to http://www.mkyong.com/boring/google-chrome-vs-firefox-3-crash-stress-test/ and read full article

Reproducible: Always

Steps to Reproduce:
1.Create simple HTML file like this and open it in Firefox

<html>
<body>
<textarea id="test" cols=80 rows=50></textarea>
<br/>
<script>
var i;
for(i =0; i<10000; i++)
{
   document.getElementById("test").value += (i + " - http://www.mkyong.com\n");
}
</script>
</body>
</html>
Actual Results:  
Browser will hang for some time

Expected Results:  
Browser should remain stable like Chromium for example
Component: General → JavaScript Engine
Product: Firefox → Core
Version: unspecified → Trunk
pretty sure these are the same. please reopen if you feel otherwise.
Status: UNCONFIRMED → RESOLVED
blocking2.0: ? → ---
Closed: 14 years ago
Resolution: --- → DUPLICATE
Reopening, because patch for bug #575515, didn't fix this issue.
Browser is unresponsive during loading this prepared site.
Status: VERIFIED → UNCONFIRMED
blocking2.0: --- → ?
Resolution: DUPLICATE → ---
I loaded that test and I got the usual slow script dialog.
Content processes, when we get them, should help solve this.
(In reply to comment #3)
> I loaded that test and I got the usual slow script dialog.

Yep, but before you get this info, Fx will become unresponsive all this time
Assignee: nobody → general
QA Contact: general → general
Yes, but that's just an observation of the fact that the UI and the JS run on the same thread.  Which is not a js engine problem, and is a duplicate of the content processes bug as comment 4 says.
Assignee: general → nobody
Component: JavaScript Engine → General
QA Contact: general → general
Whiteboard: DUPEME
blocking2.0: ? → -
Marking this as dupe of e10s
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago → 13 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.