Closed
Bug 480335
Opened 16 years ago
Closed 16 years ago
Crash when typing anything in the address bar if javascript.options.jit.chrome is true
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 479053
People
(Reporter: darin-mozilla, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090226 Shiretoko/3.1b3pre
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090226 Shiretoko/3.1b3pre
If javascript.options.jit.chrome is true then typing anything into the address bar (even about:config) will result in a crash. This is utterly repeatable and inevitable. This has been going on for the last week and a half, and continues to be true in the latest nightlies for both 3.1b3pre and 3.2alpha1pre on both Mac and Windows. Turning this option off makes the problem go away.
Reproducible: Always
Steps to Reproduce:
1. Go to about:config
2. Search for JIT
3. Set javascript.options.jit.chrome to true
4. Begin typing anything into the address bar; within an eighth of a second or so, the browser will crash. If you're a really fast typist, you can maybe type anywhere from 1-5 characters before the crash occurs.
Actual Results:
Crash
Expected Results:
No crash
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•16 years ago
|
||
This bug has definitely -not- been fixed as has been claimed. I am getting this crash with even the most currently nightlies.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Comment 3•16 years ago
|
||
It's a dupe, please don't change this bugs status again. The chain takes us down to bug 472450 which you can see does not have the fixed1.9.1 keyword, so everyone is aware it is not yet fixed on the 1.9.1 branch. It is however fixed on the trunk and on the tracemonkey branch.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → DUPLICATE
Comment 4•16 years ago
|
||
Darin for your crashes on trunk can you provide a breakpad ID (about:crashes -- assuming you get breakpad appear when you crash and have submitted the data) so we can see the crash stack.. i hate to have made a mistake in triaging this bug..
You need to log in
before you can comment on or make changes to this bug.
Description
•