js_Interpret calling InternNonIntElementId crashes [@ js_HashString]

RESOLVED INCOMPLETE

Status

()

--
critical
RESOLVED INCOMPLETE
11 years ago
6 years ago

People

(Reporter: timeless, Unassigned)

Tracking

({crash})

Trunk
x86
Windows XP
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: closeme INCO 2012-09-01, crash signature)

Attachments

(1 attachment)

(Reporter)

Description

11 years ago
Created attachment 270904 [details]
debugging bits

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
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]
(Reporter)

Comment 2

11 years ago
sorry, i wasn't blaming js_HashString. the two bits gc hazard and the skid mark weren't meant to be related.
Crash Signature: [@ js_HashString]

Comment 3

6 years ago
Is this still reproducible/actual?
Whiteboard: closeme INCO 2012-09-01

Updated

6 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.