e4x/Regress/regress-474319.js must reset gczeal.

RESOLVED FIXED

Status

()

Core
JavaScript Engine
--
major
RESOLVED FIXED
9 years ago
9 years ago

People

(Reporter: bc, Assigned: bc)

Tracking

Trunk
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

The patch in bug 469718 (attachment 395644 [details] [diff] [review]) allows the javascript tests to be run in the browser. When the full set is run on a debug build, they slow to a crawl on tracemonkey mac at least. 

Steps to reproduce:

1. apply patch in attachment 395644 [details] [diff] [review]
2. build debug
3. make jstestbrowser in your debug objdir
This is a regression? Any blame window?

/be
yes, it is a regression. The blame window is probably a month. I have to step out for a few hours but will try to narrow it down later this evening.
I'm not sure it is a regression after all. Originally, with the first patch (attachment 383270 [details] [diff] [review]) and slightly different modification to reftest.js in bug 469718 I didn't see this behavior. With the new version of reftest.js, I see this behavior back in March. Prior to March crashes prevent the test from running long enough. The use of nsIDebug2 prevents testing prior to Jan 8.
The culprit is e4x/Regress/regress-474319.js. If that is disabled for debug builds, the test run will run to completion reasonably fast (for debug).
doh. http://hg.mozilla.org/tracemonkey/rev/0bb8d915221c
Assignee: general → bclary
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Summary: debug browser jsreftests slow to a crawl → e4x/Regress/regress-474319.js must reset gczeal.
You need to log in before you can comment on or make changes to this bug.