Last Comment Bug 768004 - IonMonkey: Don't monitor the stack value for non-ResumeAfter bailouts
: IonMonkey: Don't monitor the stack value for non-ResumeAfter bailouts
Product: Core
Classification: Components
Component: JavaScript Engine (show other bugs)
: unspecified
: All All
-- normal (vote)
: ---
Assigned To: Jan de Mooij [:jandem]
: Jason Orendorff [:jorendorff]
: 758167 (view as bug list)
Depends on:
Blocks: IonFuzz
  Show dependency treegraph
Reported: 2012-06-25 08:20 PDT by Jan de Mooij [:jandem]
Modified: 2012-07-30 05:10 PDT (History)
2 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

Patch (1.17 KB, patch)
2012-06-25 08:20 PDT, Jan de Mooij [:jandem]
dvander: review+
Details | Diff | Splinter Review

Description User image Jan de Mooij [:jandem] 2012-06-25 08:20:44 PDT
Created attachment 636317 [details] [diff] [review]

decoder reported a testcase on IRC where the overrecursion check triggered a GC + invalidaton. The first opcode in the script was JSOP_GETGNAME so InvalidationBailout tried to monitor the value on top of the stack and we'd crash.

The fix is to only monitor the value for resumeAfter bailouts - in all other cases the value on the stack is invalid and we will just redo the op in the interpreter.
Comment 1 User image Jan de Mooij [:jandem] 2012-06-26 02:41:43 PDT
Comment 2 User image Jan de Mooij [:jandem] 2012-07-30 05:10:23 PDT
*** Bug 758167 has been marked as a duplicate of this bug. ***

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