Closed
Bug 485840
Opened 16 years ago
Closed 16 years ago
crash [@ XPCJSRuntime::GCCallback(JSContext*,JSGCStatus)]
Categories
(Core :: XPConnect, defect)
Core
XPConnect
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| status1.9.2 | --- | beta1-fixed |
| status1.9.1 | --- | unaffected |
People
(Reporter: wgianopoulos, Assigned: mrbkap)
References
Details
(Keywords: topcrash)
Crash Data
Attachments
(1 file)
|
1.86 KB,
patch
|
roc
:
review+
roc
:
superreview+
|
Details | Diff | Splinter Review |
bp-6acde9b0-b7e6-4045-a841-2876d2090329
Crashes happen at random times. This one occured when clicking on the refresh toolbar button.
Flags: blocking1.9.2?
| Reporter | ||
Comment 1•16 years ago
|
||
From the Crash Reporter stats, this appears to have started with the 20090325030632 Linux build and Windows 20090326050203 builds.
There was no 3/25 Windows nightly. So, it would appear that this regressed between the 20090324 and 20090325 nightly builds
Regression range:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=6cfe70091cfc&tochange=c4c84ba77c47
Comment 2•16 years ago
|
||
Bill, this is only on m-c builds, not tm or 1.9.1?
/be
| Reporter | ||
Comment 3•16 years ago
|
||
(In reply to comment #2)
> Bill, this is only on m-c builds, not tm or 1.9.1?
>
> /be
I am seeing this on mozilla-central builds. Crash reporter stats only show it on m-c also.
I have not tried tracemonkey builds.
I have had several crashes today, but becuase of being busier than normal at work, I had not tested recent builds very much. Unfortunately, all the crashes except this one were either under Linux, where crash reports are useless becuase they don't work right on AMD64 processors, or on my onwn builds that obviously don't run crash reporter.
However, this is the number 2 topcrash for the week according to Crash Reporter, so there should be plenty of stack traces to work from.
| Reporter | ||
Comment 4•16 years ago
|
||
Oh this crash was also with default JIT settings. chrome false; content true.
| Assignee | ||
Comment 5•16 years ago
|
||
This is fallout from bug 474369 -- patch in a jiffy (sorry for not catching it during review).
Assignee: general → nobody
Blocks: 474369
Component: JavaScript Engine → XPConnect
QA Contact: general → xpconnect
| Assignee | ||
Comment 6•16 years ago
|
||
This code has to be reentrant-safe.
Assignee: nobody → mrbkap
Status: NEW → ASSIGNED
Attachment #369963 -
Flags: superreview?(jst)
Attachment #369963 -
Flags: review?(jst)
Attachment #369963 -
Flags: superreview?(jst)
Attachment #369963 -
Flags: superreview+
Attachment #369963 -
Flags: review?(jst)
Attachment #369963 -
Flags: review+
| Assignee | ||
Comment 7•16 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 8•16 years ago
|
||
And http://hg.mozilla.org/mozilla-central/rev/9b8be3ba5284 fixes a style nitpick I introduced.
Updated•16 years ago
|
Flags: blocking1.9.2? → blocking1.9.2+
Comment 9•16 years ago
|
||
Mass change: adding fixed1.9.2 keyword
(This bug was identified as a mozilla1.9.2 blocker which was fixed before the mozilla-1.9.2 repository was branched (August 13th, 2009) as per this query: http://is.gd/2ydcb - if this bug is not actually fixed on mozilla1.9.2, please remove the keyword. Apologies for the bugspam)
Keywords: fixed1.9.2
Updated•16 years ago
|
status1.9.2:
--- → beta1-fixed
Keywords: fixed1.9.2
Updated•16 years ago
|
status1.9.1:
--- → unaffected
Updated•14 years ago
|
Crash Signature: [@ XPCJSRuntime::GCCallback(JSContext*,JSGCStatus)]
You need to log in
before you can comment on or make changes to this bug.
Description
•