Closed Bug 452792 Opened 16 years ago Closed 16 years ago

Tracemonkey crashes loading Google Maps [@ JS_AliasElement]

Categories

(Core :: JavaScript Engine, defect)

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

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: megabyte, Unassigned)

References

(
URL
)

Details

(Keywords: crash, stackwanted)

Crash Data

Loading Google Maps crashes Firefox when Tracemonkey JIT is enabled.

User Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1a2pre) Gecko/20080828071729 Minefield/3.1a2pre

Stack trace:

00 02582400 04da0e8e 0000f000 js3250!JS_AliasElement+0x11a
01 00000384 00000384 0000ec7c 0x5abae80
02 02582400 0042ebec 0042ec98 js3250!JS_NewDoubleValue+0x191
03 02582400 0042ec98 02582400 js3250!JS_PushArguments+0x14f
04 02582400 00000003 044b35d0 js3250!JS_PCToLineNumber+0x25913
05 02582400 00000003 044b35c0 js3250!js_Invoke+0x41f
06 02582400 00000003 044b35a8 js3250!JS_ValueToString+0x895
07 04fd2701 00000000 00000000 js3250!resolving_MatchEntry+0xbe25
Keywords: crash
Summary: Tracemonkey crashes loading Google Maps JS_AliasElement → Tracemonkey crashes loading Google Maps [@ JS_AliasElement]
oops, sorry.... i assumed you had symbols configured

but on second thought, i'm going to guess you didn't. if you didn't, please follow the instructions at:
http://developer.mozilla.org/en/docs/How_to_get_a_stacktrace_with_WinDbg

so that we can get a correct stack trace.
Keywords: stackwanted
Yeah, sorry.

I can't get it to crash on Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1a2pre) Gecko/20080829054004 Minefield/3.1a2pre so I'm going to have to check my other computer when I get access.
Crash seems to be resolved in the aforementioned build and later.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
resolution fixed is reserved for the situation where a patch has fixed the bug. -> WFM.
Resolution: FIXED → WORKSFORME
Crash Signature: [@ JS_AliasElement]
You need to log in before you can comment on or make changes to this bug.