Closed
Bug 429585
Opened 18 years ago
Closed 17 years ago
Crash [@ XPCNativeInterface::GetName] or [@ XPCNativeScriptableInfo::~XPCNativeScriptableInfo]
Categories
(Core :: XPConnect, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: gkw, Unassigned)
Details
(Keywords: crash, testcase, Whiteboard: [sg:critical?])
Crash Data
Attachments
(9 files)
I found this bug using Jesse's DOM fuzzer, and he is working on a reduced testcase because this crash is highly unreproducible and fairly inconsistent.
The first type of crash stacktraces occur on yesterday's compiled debug Firefox trunk on the Mac, while the second and third types started occurring on today's build.
Will be attaching 2 stacktraces of each type of crashes.
Updated•18 years ago
|
Attachment #316319 -
Attachment mime type: application/octet-stream → text/plain
| Reporter | ||
Comment 1•18 years ago
|
||
| Reporter | ||
Comment 2•18 years ago
|
||
| Reporter | ||
Comment 3•18 years ago
|
||
| Reporter | ||
Comment 4•18 years ago
|
||
| Reporter | ||
Comment 5•18 years ago
|
||
Updated•18 years ago
|
Comment 6•18 years ago
|
||
This testcase does not demonstrate a crash, but just a strange exception. (It also explains why the subsequent testcases use setTimeout.)
document.getElementById somehow manages to throw NS_ERROR_FILE_NOT_FOUND.
Comment 7•18 years ago
|
||
(Only when the testcase is local, I guess.)
Comment 8•18 years ago
|
||
With MallocScribble enabled, this testcase always triggers a crash
[@ XPCNativeInterface::GetName]. Without MallocScribble, it usually doesn't crash.
Comment 9•18 years ago
|
||
This crashes if you quit after loading it. It can crash even without MallocScribble.
Comment 10•18 years ago
|
||
Wouldn't hold back the release for this. Please re-nom if you disagree.
Flags: wanted1.9.0.x+
Flags: blocking1.9?
Flags: blocking1.9-
Comment 11•18 years ago
|
||
I can not get the "immediate crash" testcase to crash, even with MallocScribble turned on. Please reopen if you can.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Comment 12•18 years ago
|
||
Still crashes for me. Note that it must be local in order to request the privileges needed to force a garbage collection.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 13•17 years ago
|
||
Adding sayrer to help get this scheduled.
Updated•17 years ago
|
Whiteboard: [sg:critical] → [sg:critical?]
Comment 14•17 years ago
|
||
Comment on attachment 316337 [details]
testcase 1: immediate crash [@ XPCNativeInterface::GetName]
Can't reproduce on OSX with MallocScribble using a trunk build.
Comment 15•17 years ago
|
||
Comment on attachment 316338 [details]
testcase 2: shutdown crash [@ XPCNativeScriptableInfo::~XPCNativeScriptableInfo]
Can't reproduce this either.
Comment 16•17 years ago
|
||
WFM using TM branch (with mallocscribble and with JIT off to avoid bug 458857). I even tried the original testcase and the partially-reduced testcases I saved off while I was reducing it.
Status: REOPENED → RESOLVED
Closed: 18 years ago → 17 years ago
Resolution: --- → WORKSFORME
Updated•17 years ago
|
Flags: wanted1.9.0.x+ → wanted1.9.0.x?
| Reporter | ||
Updated•17 years ago
|
Flags: in-testsuite?
| Assignee | ||
Updated•15 years ago
|
Crash Signature: [@ XPCNativeInterface::GetName]
[@ XPCNativeScriptableInfo::~XPCNativeScriptableInfo]
Updated•10 years ago
|
Group: core-security → core-security-release
Updated•10 years ago
|
Group: core-security-release
You need to log in
before you can comment on or make changes to this bug.
Description
•