Closed Bug 541997 Opened 15 years ago Closed 15 years ago

js1_5/extensions/regress-454704.js time out browser

Categories

(Core :: JavaScript Engine, defect)

1.9.1 Branch
x86
Linux
defect
Not set
normal

Tracking

()

VERIFIED FIXED
Tracking Status
blocking2.0 --- alpha1+
status1.9.2 --- unaffected
blocking1.9.1 --- .8+
status1.9.1 --- .8-fixed

People

(Reporter: bc, Assigned: mrbkap)

References

()

Details

(4 keywords, Whiteboard: [sg:nse])

1. http://test.bclary.com/tests/mozilla.org/js/js-test-driver-standards.html?test=js1_5%2Fextensions%2Fregress-454704.js;language=type;text/javascript 2. test takes over 8 minutes on linux when normally takes less than 15 seconds. bisection shows bug 504021 as the regressor.
Flags: in-testsuite+
Group: core-security
blocking2.0: --- → ?
Is this timing out on m-c too? Or 1.9.2? Or just 1.9.1?
I've only seen it on 1.9.1 so far. not m-c or tracemonkey if the themasta logs are to be believed. I'll have to check on 1.9.2.
Assignee: general → mrbkap
blocking2.0: ? → alpha1
Tentatively marking this as fixed (I never reproduced it locally) after the partial backout in bug 504021.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
A regression of this scale is probably a blocker, possibly noticeable on real-world sites. Maybe also related to a Ts slowdown (and thus already fixed by a recent partial backout of bug 504021 as noted in comment 3). But qawanted to verify that's the case. bc: please also verify that 1.9.2 is not affected and set the status1.9.2 field as appropriate (wanted or unaffected).
blocking1.9.1: --- → .8+
status1.9.2: --- → ?
Keywords: qawanted
v 1.9.1. 1.9.2 not affected.
Status: RESOLVED → VERIFIED
Keywords: qawantedverified1.9.1
Keywords: perf
Whiteboard: [sg:nse]
Group: core-security
You need to log in before you can comment on or make changes to this bug.