Closed Bug 531837 Opened 15 years ago Closed 15 years ago

Assertion failure: tracecx->bailExit, at .../mozilla/js/src/jstracer.cpp:7740 with venkman & setting functionHook

Categories

(Core :: JavaScript Engine, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 519719

People

(Reporter: Gijs, Unassigned)

Details

(Keywords: assertion, crash)

Self-built debug build: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a1pre) Gecko/20091130 Minefield/3.7a1pre (.NET CLR 3.5.30729)

STR:
0. Install a stock copy of Venkman ( https://addons.mozilla.org/addon/216 ). Restart your browser.
1. Open Venkman (Tools > JavaScript Debugger)
2. In Venkman, use the menu to include chrome files (Debug > untick Exclude Chrome Files)
3. In the interactive session (bottom right), execute:

console.jsds.functionHook = console.callHook

This sets the js debugger service's functionHook.

5. Wait only a little bit, then use the UI. To me, pretty much any interaction with the menus, or the scripts view (doubleclicking scripts) crashes very quickly.

Expected results:
Be able to continue using Venkman.

Actual results:
Assert, crash.

Sample crash stack is at http://pastebin.mozilla.org/687083 (good for another month)

I tried to get a JS stack, but calling DumpJSStack() when stopped in devenv crashes Firefox (not devenv, fortunately, but it does lose all state info, it seems). :-(
Summary: Assertion failure: tracecx->bailExit, at .../mozilla/js/src/jstracer.cpp:7740 with modified venkman & setting functionHook → Assertion failure: tracecx->bailExit, at .../mozilla/js/src/jstracer.cpp:7740 with venkman & setting functionHook
Hmm, maybe to do with bug 519719 ?
Indeed, this is fixed after updating my m-c build. Thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
No longer blocks: 483685
You need to log in before you can comment on or make changes to this bug.