380018 - "Assertion failure: pcdepth >= 0" with return in finally

Status: RESOLVED WORKSFORME

(Core :: JavaScript Engine, defect)

Description

[Jesse Ruderman]

js> (function() { try { try { } finally { return; } } finally { this.z.z; } })()   
Assertion failure: pcdepth >= 0, at jsopcode.c:4869

Thread 0 Crashed:
0   js 	0x000ca43a JS_Assert + 70 (jsutil.c:60)
1   js 	0x000972df js_DecompileValueGenerator + 2447 (jsopcode.c:4871)
2   js 	0x00026c95 js_ReportValueErrorFlags + 151 (jscntxt.c:1232)
3   js 	0x00085cdd js_ValueToNonNullObject + 117 (jsobj.c:4581)
4   js 	0x00068b75 js_Interpret + 55592 (jsinterp.c:3782)
5   js 	0x0005a3dd js_Execute + 715 (jsinterp.c:1591)
6   js 	0x0001b1c2 JS_ExecuteScript + 54 (jsapi.c:4702)
7   js 	0x00002812 Process + 912 (js.c:268)
8   js 	0x0000321b ProcessArgs + 2045 (js.c:519)
9   js 	0x000080e0 main + 612 (js.c:3237)
10  js 	0x00002326 _start + 216
11  js 	0x0000224d start + 41

Comment 1

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

This testcase seems to work as expected in TM tip, but still occurs in 1.9.0.x branch.

Comment 2

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

(In reply to comment #1)
> This testcase seems to work as expected in TM tip, but still occurs in 1.9.0.x
> branch.

Resolving as WFM would be a better resolution.