I was trying to open 24 windows as firefox was starting. I have no idea why this function thought it was a good idea to get involved w/ spidermonkey, it normally interferes with networking activities. For my reference, i'm using 3.0.405208 Incident ID: 18520696 Stack Signature cahooknt.dll + 0x7f0 (0x100007f0) d1e344ae Product ID FirefoxTrunk Build ID 2006050405 Trigger Time 2006-05-10 05:59:42.0 Platform Win32 Operating System Windows NT 5.1 build 2600 Module cahooknt.dll + (000007f0) URL visited <a href='http://landfill.mozilla.org/ryl/random.html'>http://landfill.mozilla.org/ryl/random.html</a> User Comments Since Last Crash 14 sec Total Uptime 185880 sec Trigger Reason Access violation Source File, Line No. N/A Stack Trace cahooknt.dll + 0x7f0 (0x100007f0) JS_SetPrivate js_DefineFunction JS_DefineFunction JS_DefineFunctions JS_InitClass js_InitObjectClass js_InitFunctionAndObjectClasses JS_ResolveStandardClass TempGlobalResolve js_LookupPropertyWithFlags js_LookupProperty js_GetProperty XPCWrappedNativeScope::SetGlobal XPCWrappedNativeScope::XPCWrappedNativeScope XPCWrappedNativeScope::GetNewOrUsed nsXPConnect::InitClasses nsXPConnect::InitClassesWithNewWrappedGlobal jay: could you pull more details about this crash for me? I'd like to see if I can at least maybe figure out what was really happening. I'm filing this in spidermonkey because that's where the top of the stack is I need to figure out if there's any reason spidermonkey might allow this evil hook to invade its calling area. If it's possible and if there's a way to avoid that, that's something to consider. It's also possible that the real stack doesn't look like that, although the stack seems fairly coherent otherwise....
timeless, I can't query on the stack as I get Bad Response from Server errors. What email did you use?
Crash Signature: [@ cahooknt.dll + 0x7f0]
Is this still reproducible/actual?
Whiteboard: closeme INCO 2012-09-01
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.