Last Comment Bug 732365 - Assertion failure: hasAnalysis(), at jsinferinlines.h:1416
: Assertion failure: hasAnalysis(), at jsinferinlines.h:1416
Product: Core
Classification: Components
Component: JavaScript Engine (show other bugs)
: Trunk
: x86 Mac OS X
: -- normal (vote)
: ---
Assigned To: general
: Jason Orendorff [:jorendorff]
Depends on:
Blocks: minotaur
  Show dependency treegraph
Reported: 2012-03-02 03:18 PST by Panos Astithas [:past]
Modified: 2012-05-09 08:01 PDT (History)
9 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

Crash log that appeared in the OS X popup (70.28 KB, text/plain)
2012-03-02 03:19 PST, Panos Astithas [:past]
no flags Details

Description Panos Astithas [:past] 2012-03-02 03:18:19 PST

1) Enable the debugger by setting devtools.debugger.enabled to true and restart
2) Visit
3) cmd-opt-S to open the script debugger and then quickly reload the page:

Assertion failure: hasAnalysis(), at /Users/past/src/fx-team/js/src/jsinferinlines.h:1416
Comment 1 Panos Astithas [:past] 2012-03-02 03:19:31 PST
Created attachment 602303 [details]
Crash log that appeared in the OS X popup
Comment 2 Panos Astithas [:past] 2012-03-02 03:21:22 PST
Possibly useful data: there are a few seconds of beachballing between the assertion and the SIGSEGV message.
Comment 3 David Mandelin [:dmandelin] 2012-03-02 17:46:47 PST
Assigning medium priority for now since it doesn't look like it's blocking you. Let me know if that's not right.
Comment 4 Jason Orendorff [:jorendorff] 2012-03-20 09:01:37 PDT
I would be a little surprised if this didn't turn out to be a dup of bug 725733, even though it's a different assertion, different stack.

I'll try to get that one moving.
Comment 5 David Mandelin [:dmandelin] 2012-05-01 11:59:15 PDT
K9O triage question: are we going to have script debugger in scope for K9O?
Comment 6 Sheila Mooney 2012-05-01 12:34:16 PDT
Yes, it's in scope for k9o. Is this a dependency?
Comment 7 Panos Astithas [:past] 2012-05-09 08:01:51 PDT
It seems to be fixed now, so apparently it was a dup of bug 725733.

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