Closed Bug 389333 Opened 17 years ago Closed 17 years ago

"Assertion failure: *fp->pc == JSOP_CALL || *fp->pc == JSOP_NEW" at flip.com

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: jruderman, Assigned: brendan)

References

(
URL
)

Details

(Keywords: assertion) 

Steps to reproduce:
1. Load http://www.flip.com/.

Result:
Assertion failure: *fp->pc == JSOP_CALL || *fp->pc == JSOP_NEW, at mozilla/js/src/jsstr.c:1232

I'm testing with a Mac trunk debug build that has Brendan's patch from bug
385393 comment 97.
Odd to see bugs filed when the patch involved has not landed, but thanks. I can't get this to crash with the interdiff attached to bug 389331 applied on top of the last patch in bug 385393. Jesse, can you apply and retest?

/be
Clearly caused by the next-to-last patch in bug 385393.

/be
Assignee: general → brendan
Status: UNCONFIRMED → NEW
Ever confirmed: true
Blocks: jsfastnative
No longer asserts for me with the latest patch there :)
Status: NEW → RESOLVED
Closed: 17 years ago
Keywords: qawanted
Resolution: --- → FIXED
Flags: in-testsuite-
You need to log in before you can comment on or make changes to this bug.