Last Comment Bug 707337 - [IncrementalGC] "Assertion failure: started,"
: [IncrementalGC] "Assertion failure: started,"
: assertion, testcase
Product: Core
Classification: Components
Component: JavaScript Engine (show other bugs)
: Other Branch
: x86 Mac OS X
-- critical (vote)
: ---
Assigned To: Bill McCloskey (:billm)
: Jason Orendorff [:jorendorff]
Depends on:
Blocks: jsfunfuzz 630996 IncrementalGC
  Show dependency treegraph
Reported: 2011-12-02 15:09 PST by Gary Kwong [:gkw] [:nth10sd]
Modified: 2011-12-06 16:03 PST (History)
4 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

testcase (2.70 KB, text/plain)
2011-12-02 15:09 PST, Gary Kwong [:gkw] [:nth10sd]
no flags Details

Description User image Gary Kwong [:gkw] [:nth10sd] 2011-12-02 15:09:28 PST
Created attachment 578738 [details]

The attached testcase asserts js 64-bit debug shell on larch changeset 52c1d5dc6aad without any CLI arguments at Assertion failure: started, when passed in as a CLI argument.

This was found using a combination of jsfunfuzz and jandem's method fuzzer.
Comment 1 User image Bill McCloskey (:billm) 2011-12-06 16:03:38 PST
Another great test case. This is fixed in:

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