Closed Bug 14503 Opened 21 years ago Closed 20 years ago

setInterval causes crash when fired

Categories

(Core :: DOM: Core & HTML, defect, P3, critical)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: peterl-retired, Assigned: vidur)

Details

Attachments

(1 file)

Load sample page (or any page with a setInterval call), crash.

NTDLL! 77f6ce0c()
NTDLL! 77f67546()
js_SuspendThread(JSThinLock * 0x011d75c4) line 506 + 12 bytes
js_Enqueue(JSThinLock * 0x011d75c4, long 15869456) line 548 + 9 bytes
js_Lock(JSThinLock * 0x011d75c4, long 15869456) line 581 + 13 bytes
js_LockScope1(JSContext * 0x0196a350, JSScope * 0x011d75a0, long 15869456) line
634 + 13 bytes
js_LockObj(JSContext * 0x0196a350, JSObject * 0x01adb030) line 702 + 17 bytes
js_GetSlotWhileLocked(JSContext * 0x0196a350, JSObject * 0x01adb030, unsigned
long 1) line 259 + 13 bytes
js_Invoke(JSContext * 0x0196a350, unsigned int 1, unsigned int 2) line 444 + 128
bytes
js_InternalCall(JSContext * 0x0196a350, JSObject * 0x011d7598, long 28160048,
unsigned int 1, long * 0x01ada450, long * 0x0012fca8) line 748 + 15 bytes
JS_CallFunction(JSContext * 0x0196a350, JSObject * 0x011d7598, JSFunction *
0x011d8b88, unsigned int 1, long * 0x01ada450, long * 0x0012fca8) line 2634 + 32
bytes
nsJSContext::CallFunction(nsJSContext * const 0x0196a4c0, void * 0x011d7598,
void * 0x011d8b88, unsigned int 1, void * 0x01ada450, int * 0x0012fcec) line 231
+ 39 bytes
GlobalWindowImpl::RunTimeout(nsTimeoutImpl * 0x01ada480) line 1713 + 68 bytes
nsGlobalWindow_RunTimeout(nsITimer * 0x01ada3c0, void * 0x01ada480) line 1617 +
15 bytes
TimerImpl::Fire(unsigned long 159202140) line 308 + 17 bytes
TimerImpl::ProcessTimeouts(unsigned long 159202140) line 187
FireTimeout(HWND__ * 0x00000000, unsigned int 275, unsigned int 7089, unsigned
long 159202140) line 101 + 9 bytes
USER32! 77e7185c()
main(int 1, char * * 0x00f213c0) line 136 + 11 bytes
mainCRTStartup() line 338 + 17 bytes
KERNEL32! 77f1ba06()
Attached file Test page
Assignee: mccabe → vidur
Component: Javascript Engine → DOM Level 0
QA Contact: cbegle → desale
i believe the correct component is dom 0.
Severity: normal → critical
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Can't actually find the original bug that was fixed a while ago, but either way
- this works now.
Status: RESOLVED → VERIFIED
Tested with 1999-11-11-09. Working fine, so marking it verified.
You need to log in before you can comment on or make changes to this bug.