Closed Bug 487238 Opened 16 years ago Closed 16 years ago

Crash in [js_Invoke, js_Interpret and js_Execute] when selecting link

Categories

(Core :: JavaScript Engine, defect)

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

Tracking

()

Status:
VERIFIED DUPLICATE of bug 487271

People

(Reporter: marcia, Unassigned)

References

(
URL
)

Details

(Keywords: crash)

Seen while running Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2a1pre) Gecko/20090407 Minefield/3.6a1pre STR: 1. Load the URL site 2. Select the last link on the bottom right. Crash ID: http://crash-stats.mozilla.com/report/index/b42dc8da-8889-4e26-8cce-48bd52090407 100% reproducible on the 10.6 machine I am running on.
I was able to reproduce this easily using Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9.2a1pre) Gecko/20090407 Minefield/3.6a1pre as well.
I can reproduce on Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2a1pre) Gecko/20090407 Minefield/3.6a1pre http://crash-stats.mozilla.com/report/index/c8739b46-9527-4375-b78c-0dd6c2090407
OS: Mac OS X → All
Daniel, I get the same stack as you. But shouldn't get @JS_CallTracer it's own bug? It doesn't look related to Marcias stack.
Severity: major → critical
Hardware: x86 → All
(In reply to comment #3) > related to bug 487271? I believe that's a dupe.
(In reply to comment #4) > But shouldn't get @JS_CallTracer it's own > bug? Perhaps -- I didn't file another since it had the same STR as this bug, and memory-corruption bugs often turn up different stacks on different platforms & conditions. In any case, bug 487271 has a fix that will land on mozilla-central soon, and maybe that'll fix both sorts of crashes here. If it doesn't, feel free to open another bug for the @JS_CallTracer crash.
This appears to be the same root issue as the duped bug, and I no longer get the crash using the latest nightly, so duping this.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Yeah, this also fixed the crash I was seeing with @JS_CallTracer.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.