Closed Bug 354076 Opened 18 years ago Closed 18 years ago

possible alarm crash [@ js_SetProtoOrParent]

Categories

(Calendar :: Alarms, defect)

Product:
Calendar
Component:
Alarms
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 353704

People

(Reporter: jminta, Unassigned)

Details

(Keywords: crash)

Crash Data

I'm seeing several talkback reports (TB23621344, TB23620975, TB23620475) with the same stack in current builds.  The comments suggest this is dealing with alarm-firing.  The stacks look fairly identical:
js_SetProtoOrParent  [mozilla\js\src\jsobj.c, line 341]
JS_SetPrototype  [mozilla\js\src\jsapi.c, line 2399]
xpc_CloneJSFunction  [mozilla\js\src\xpconnect\src\xpcwrappednativeinfo.cpp, line 77]
DefinePropertyIfFound  [mozilla\js\src\xpconnect\src\xpcwrappednativejsops.cpp, line 454]
XPC_WN_ModsAllowed_Proto_Resolve  [mozilla\js\src\xpconnect\src\xpcwrappednativejsops.cpp, line 1579]
js_LookupPropertyWithFlags  [mozilla\js\src\jsobj.c, line 3227]
js_LookupProperty  [mozilla\js\src\jsobj.c, line 3085]
nsWindowSH::NewResolve  [mozilla\dom\src\base\nsdomclassinfo.cpp, line 6004]
XPC_WN_Helper_NewResolve  [mozilla\js\src\xpconnect\src\xpcwrappednativejsops.cpp, line 1064]

Filing as UNCO until we can get real steps to reproduce
Flags: blocking0.3?
Keywords: qawanted
It's actually a crash caused by one of dbaron's leak fix bugs (bug 353090). It should be fixed now, though.

*** This bug has been marked as a duplicate of 353704 ***

*** This bug has been marked as a duplicate of 353704 ***
Severity: normal → critical
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Keywords: qawanted
Resolution: --- → DUPLICATE
Summary: possible alarm crash [@js_SetProtoOrParent] → possible alarm crash [@ js_SetProtoOrParent]
Status: RESOLVED → VERIFIED
Flags: blocking0.3?
Crash Signature: [@ js_SetProtoOrParent]
You need to log in before you can comment on or make changes to this bug.