As a security precaution, we have turned on the setting "Require API key authentication for API requests" for everyone. If this has broken something, please contact
Last Comment Bug 714607 - jit-test/tests/basic/bug680217.js takes a long time
: jit-test/tests/basic/bug680217.js takes a long time
Product: Core
Classification: Components
Component: JavaScript Engine (show other bugs)
: unspecified
: All All
: -- normal (vote)
: mozilla12
Assigned To: Jan de Mooij [:jandem]
: Jason Orendorff [:jorendorff]
Depends on:
  Show dependency treegraph
Reported: 2012-01-02 04:06 PST by Jan de Mooij [:jandem]
Modified: 2012-01-03 03:43 PST (History)
2 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

Patch (868 bytes, patch)
2012-01-02 04:16 PST, Jan de Mooij [:jandem]
no flags Details | Diff | Splinter Review
Patch (875 bytes, patch)
2012-01-02 04:27 PST, Jan de Mooij [:jandem]
bhackett1024: review+
Details | Diff | Splinter Review

Description User image Jan de Mooij [:jandem] 2012-01-02 04:06:30 PST
I just got a timeout when running jit-tests. This test takes about 30 seconds to run in the interpreter (with a release build or with -m -n it's much faster)
Comment 1 User image Jan de Mooij [:jandem] 2012-01-02 04:16:24 PST
Created attachment 585274 [details] [diff] [review]

Since most changes for bug 680217 were in the parser/emitter, I think it's fine to just lower the iteration count. And even if this value is necessary, I'm sure the fuzzers will catch it again, probably by modifying this testcase.
Comment 2 User image Jan de Mooij [:jandem] 2012-01-02 04:27:46 PST
Created attachment 585275 [details] [diff] [review]

Also adds a gc() call (looks like these loops are there just to trigger a GC).
Comment 4 User image Marco Bonardo [::mak] 2012-01-03 03:43:54 PST

Note You need to log in before you can comment on or make changes to this bug.