Closed
Bug 386850
Opened 17 years ago
Closed 12 years ago
js_Interpret calling InternNonIntElementId crashes [@ js_HashString]
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: timeless, Unassigned)
Details
(Keywords: crash, Whiteboard: closeme INCO 2012-09-01)
Crash Data
Attachments
(1 file)
|
23.78 KB,
text/plain
|
Details |
js3250!js_HashString+0x62 js3250!js_AtomizeString+0x12 js3250!js_ValueToStringAtom+0x20 js3250!InternNonIntElementId+0x4b js3250!js_Interpret+0x3f60 js3250!js_Invoke+0x41f xul!nsXPCWrappedJSClass::CallMethod+0x780 xul!nsXPCWrappedJS::CallMethod+0x27 xul!PrepareAndDispatch+0xe7 xul!SharedStub+0x16 xul!nsEventListenerManager::HandleEventSubType+0x110 xul!`string'+0x8 xul!PopupAllowedForEvent+0x80 WARNING: Frame IP not in any known module. Following frames may be wrong. 0x4b7cbd8 xul!nsEventTargetChainItem::HandleEvent+0x5e xul!nsEventTargetChainItem::HandleEventTargetChain+0x123 xul!nsEventDispatcher::Dispatch+0x1f3 xul!PresShell::HandleEventInternal+0x1b2 xul!PresShell::HandleEvent+0x449 xul!nsViewManager::HandleEvent+0x2f
|
||
Comment 1•17 years ago
|
||
C'mon, a string hash function cannot contain a GC hazard. It might be the caller that is to blame. But you have way too little evidence here to say what the bug is. How about starting from the symptom? /be
Summary: gc hazard? [@ js_HashString] → js_Interpret calling InternNonIntElementId crashes [@ js_HashString]
sorry, i wasn't blaming js_HashString. the two bits gc hazard and the skid mark weren't meant to be related.
|
||
Updated•13 years ago
|
Crash Signature: [@ js_HashString]
Is this still reproducible/actual?
Whiteboard: closeme INCO 2012-09-01
|
||
Updated•12 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•