Closed
Bug 483485
Opened 16 years ago
Closed 16 years ago
TM: Crash with JIT chrome enabled (multiple Signatures) - Tracking Bug
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 481302
People
(Reporter: fehe, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090314 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090314 Minefield/3.2a1pre
This is a tracking bug for a JIT chrome crash at the linked page, but which results (so far) in four different observed signatures.
Reproducible: Always
|
||
Comment 1•16 years ago
|
||
Probably related to bug 481302.
You just attached the same testcase for each bug. If they're all crashing on the same page then one bug would've been fine to start.
|
|
||
Comment 2•16 years ago
|
||
Just retested bug 481302 and checked yours. (both your attached testcase and the 2 slightly different URLs) All seem to be the same issue, none of which crash in the latest Tracemonkey branch build. (tested on WinXP & Linux)
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-tracemonkey/
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
|
|
||
Comment 7•16 years ago
|
||
Dear god that made a lot of bugspam. You really didn't need 5 bugs for one testcase.
In the future, please note:
1. One bug would have been plenty.
2. You can reference an attachment by URL or ID just like a bug, so attaching 4 identical testcases is redundant. An example for one of yours being: attachment 367455 [details]
3. Pasting the stack trace itself in the bug is helpful. You can then full-text search Bugzilla for parts and you can't guarantee immortality for the report on the server anyway.
4. Testing a known TM bug in the latest TM build is probably a good idea. I can easily reproduce your crash myself and then not reproduce it in latest TM. Checking this is easy to do.
5. A search for other URLs for piro.sakura.ne.jp would've found bug 481302.
Unfortunately, in the past, I have typically been forced to break up bugs--even when issues were related, which is why I decided to do it now than have to do it later.
Sorry about all that. :-)
Oops. I shouldn't file bugs when I'm tired and anxious to get to bed.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•