Closed
Bug 496377
Opened 15 years ago
Closed 13 years ago
TM: Running Test on Sun loop-test results in unresponsive script with MozMill installed
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: aakashd, Unassigned)
References
(Blocks 1 open bug, )
Details
Build: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1pre) Gecko/20090601 Shiretoko/3.5pre (.NET CLR 3.5.30729) ID:20090601044045 and Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2a1pre) Gecko/20090601 Minefield/3.6a1pre (.NET CLR 3.5.30729) ID:20090601041706 When running the loop-test on any nightly (via any platform no matter jit is enabled or disabled), the script becomes unresponsive if MozMill is installed and enabled. Steps to Reproduce: 1. Install and Enable MozMill. 2. Run the loop test via the URL. Actual Results: Script becomes unresponsive Expected Results: A results page with finish times should show.
Flags: wanted1.9.1?
Comment 1•15 years ago
|
||
That's crazy! I'll try to get a shark profile.
Comment 2•15 years ago
|
||
Not directly related to bug 469347. We should check first if this is a Mozmill problem.
No longer depends on: 469347
Flags: wanted1.9.1?
Comment 3•15 years ago
|
||
Brendan, is this Shark profile helpful to identify why we are so slow on the sunspider test when Mozmill is installed?
Which shark profile? And which sunspider test? The loop test in the URL isn't part of Sunspider, afaict.
Comment 5•15 years ago
|
||
Oh double sorry. I meant the loop test and further forgot to point to the shark profile. Here it is: http://mozilla.hskupin.info/mozmill.mshark
Comment 6•13 years ago
|
||
WFM on current trunk and the MozMill 1.5.5 extension installed.
You need to log in
before you can comment on or make changes to this bug.
Description
•