Closed Bug 556861 Opened 15 years ago Closed 13 years ago

crash [@ nsScriptSecurityManager::GetPrincipalAndFrame(JSContext*, JSStackFrame**, unsigned int*)]

Categories

(Core :: Security: CAPS, defect)

x86
All
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: wsmwk, Unassigned)

References

Details

(Keywords: crash, intermittent-failure, Whiteboard: [regression?])

Crash Data

crash [@ nsScriptSecurityManager::GetPrincipalAndFrame(JSContext*, JSStackFrame**, unsigned int*)] #39 crash for Thunderbird v3.0.3 All OS Anecdotal note: crash rate seems to have substantially increased in v3.0.2. almost zero in v3.0 and v3.0.1. bp-2e555373-c120-4d27-87e1-42bd52100320 (has email address) 0 thunderbird.exe nsScriptSecurityManager::GetPrincipalAndFrame caps/src/nsScriptSecurityManager.cpp:2234 1 thunderbird.exe nsScriptSecurityManager::GetSubjectPrincipal caps/src/nsScriptSecurityManager.cpp:2308 2 thunderbird.exe nsScriptSecurityManager::CheckPropertyAccessImpl caps/src/nsScriptSecurityManager.cpp:684 3 thunderbird.exe nsScriptSecurityManager::CanAccess caps/src/nsScriptSecurityManager.cpp:3139 4 thunderbird.exe XPCWrappedNative::CallMethod js/src/xpconnect/src/xpcwrappednative.cpp:2047 5 thunderbird.exe XPC_WN_GetterSetter js/src/xpconnect/src/xpcwrappednativejsops.cpp:1622 6 js3250.dll js_Invoke js/src/jsinterp.cpp:1386 7 js3250.dll js_InternalInvoke js/src/jsinterp.cpp:1447 8 js3250.dll js_InternalGetOrSet js/src/jsinterp.cpp:1510 9 js3250.dll js_GetSprop js/src/jsscope.h:367 10 js3250.dll js_NativeGet js/src/jsobj.cpp:4167 11 js3250.dll js_Interpret js/src/jsinterp.cpp:4436 12 js3250.dll js_Invoke js/src/jsinterp.cpp:1394 13 thunderbird.exe nsXPCWrappedJSClass::CallMethod js/src/xpconnect/src/xpcwrappedjsclass.cpp:1745 I was deleting the files in one of the sent folders bp-ab029b9f-502b-4d50-9141-2059d2100227 I was writing a message to send to a newsgroup when Thunderbird crashed. This was immediately after I accepted the offer to upgrade to the latest version of Thunderbird and the install had completed. Frustration! 9a8900fa-63d0-43a2-b45d-4e1e22100226
I got the same crash today with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.3a4pre) Gecko/20100407 Minefield/3.7a4pre ID:20100407030830 The browser was minimized in the tray when the crash happened. Crash id: bp-c656f688-485f-4d73-ae8d-134c52100407 I have no idea which is the right component to put this bug into. Lets move it into NSPR for now.
Assignee: nobody → wtc
Component: Security → NSPR
Product: Thunderbird → NSPR
QA Contact: thunderbird → nspr
Version: Trunk → other
Henrik: I see no basis for marking this as an NSPR bug.
Hah, ok. I found the right component. Moving over to Core/Security:Caps
Assignee: wtc → nobody
Component: NSPR → Security: CAPS
Product: NSPR → Core
QA Contact: nspr → caps
Version: other → Trunk
rose to #31 crash for v3.0.4
Whiteboard: regression?
Blocks: 438871
Whiteboard: regression? → [orange][regression?]
See also: https://support.mozilla.com/en-US/questions/747009 Or was this fixed for 3.1.9?
Crash Signature: [@ nsScriptSecurityManager::GetPrincipalAndFrame(JSContext*, JSStackFrame**, unsigned int*)]
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that: * Haven't changed in > 6months * Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb} * Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive. I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases). Sorry for the spam! Filter on: #FFA500
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange][regression?] → [regression?]
You need to log in before you can comment on or make changes to this bug.