Closed Bug 458227 Opened 16 years ago Closed 16 years ago

JIT crashes jsMSX demo.

Categories

(Core :: JavaScript Engine, defect, P2)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
Windows XP
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 455547

People

(Reporter: bugs, Assigned: dvander)

References

(
URL
)

Details

Clicking on Start, with JIT enabled, crashes. Disable JIT, works fine. Was testing to see if JIT improved performance of this demo (interestingly, Webkit was flatlining at 32 ips so I was curious if that was the natural speed of the demo for that ROM, or Webkit). Since it has been crashing for a week or two, figured I'd better make a note of it. http://crash-stats.mozilla.com/report/index/30c9825c-8c16-11dd-bd57-001a4bd43e5c http://crash-stats.mozilla.com/report/index/2735e1fd-8c16-11dd-b43a-001cc45a2c28 A couple of the crashes.
Can you plaese retest with a build form today (and please add the used build in the bug report) 0 js3250.dll nanojit::LIns::isop js/src/nanojit/LIR.h:365 1 js3250.dll nanojit::LIns::isTramp js/src/nanojit/LIR.h:383 2 js3250.dll nanojit::LIns::deref js/src/nanojit/LIR.cpp:244 3 js3250.dll nanojit::LIns::oprnd2 js/src/nanojit/LIR.cpp:627 4 js3250.dll TraceRecorder::set js/src/jstracer.cpp:1498 5 js3250.dll TraceRecorder::record_JSOP_GETELEM js/src/jstracer.cpp:4650 6 js3250.dll js3250.dll@0x66f15 7 js3250.dll js_Invoke js/src/jsinterp.cpp:1324 8 js3250.dll js_fun_apply js/src/jsfun.cpp:1731 9 js3250.dll js_Interpret js/src/jsinterp.cpp:4977 10 js3250.dll js_Execute js/src/jsinterp.cpp:1550 11 js3250.dll JS_EvaluateUCScriptForPrincipals js/src/jsapi.cpp:5078 12 xul.dll nsJSContext::EvaluateString dom/src/base/nsJSEnvironment.cpp:1574 13 xul.dll xul.dll@0x2f2be0
Flags: blocking1.9.1+
Priority: -- → P1
David is working on a crash that looks related.
Assignee: general → danderson
Right. Sorry. Should have been more explicit that I was testing with that day's trunk build. Re: Comment #3 - even if it doesn't warrant duping yet, mind referencing the bug? I of course would be interested to know when the patches are committed and such.
http://crash-stats.mozilla.com/report/index/5f9761d7-9557-11dd-9f7e-001cc45a2c28?p=1 The trace appears to have changed slightly, but the interesting thing I wanted to note was while retesting with latest nightly, the first time I tried firefox froze up with 100% of CPU and I killed it after a few minutes. This trace is from the 2nd attempt, which crashes as usual.
Just to confirm, with build: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b2pre) Gecko/20081020 Minefield/3.1b2pre it still crashes...
Priority: P1 → P2
Looks the same as the SCUMM bug, the fix works for me on both as well.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.