Last Comment Bug 649477 - TI: Assertion failure: inContext(), at jscntxt.cpp:114
: TI: Assertion failure: inContext(), at jscntxt.cpp:114
Status: RESOLVED FIXED
:
Product: Core
Classification: Components
Component: JavaScript Engine (show other bugs)
: unspecified
: All All
: -- normal (vote)
: ---
Assigned To: general
:
: Jason Orendorff [:jorendorff]
Mentors:
Depends on:
Blocks: infer-regress
  Show dependency treegraph
 
Reported: 2011-04-12 13:31 PDT by Jan de Mooij [:jandem]
Modified: 2011-04-13 07:14 PDT (History)
5 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments
Stack trace (28.08 KB, text/plain)
2011-04-12 13:31 PDT, Jan de Mooij [:jandem]
no flags Details

Description Jan de Mooij [:jandem] 2011-04-12 13:31:57 PDT
Created attachment 525489 [details]
Stack trace

I get this assert when using Gmail.
Comment 1 Brian Hackett (:bhackett) 2011-04-13 07:14:15 PDT
It looks from the stack and pointer values like we are triggering recompilation immediately after having pushed a new, empty stack segment for an ExternalInvoke, which StackSpace::containingSegment doesn't like.  This makes containingSegment work in such cases.  I don't think calling containingSegment is possible in the TM branch between when the segment gets pushed and the associated invoke frame gets pushed, but this still might want to go on TM.

http://hg.mozilla.org/projects/jaegermonkey/rev/9eafb9ecc76a

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