Closed
Bug 631553
Opened 13 years ago
Closed 13 years ago
crash [@ PL_DHashTableOperate | nsFrameScriptExecutor::LoadFrameScriptInternal]
Categories
(Core :: IPC, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jdm, Assigned: jdm)
Details
(Keywords: crash)
Crash Data
Attachments
(1 file, 2 obsolete files)
977 bytes,
patch
|
smaug
:
review+
johnath
:
approval2.0+
|
Details | Diff | Splinter Review |
This bug was filed from the Socorro interface and is report bp-049a1da3-0f33-42dc-9150-097b32110203 . ============================================================= According to the stack, we're trying to load a frame script in-process due to a DOM event being fired, and meanwhile XPCOM is shutting down. 0 libxul.so PL_DHashTableOperate pldhash.c:615 1 libxul.so nsFrameScriptExecutor::LoadFrameScriptInternal nsTHashtable.h:171 2 libxul.so nsInProcessTabChildGlobal::LoadFrameScript content/base/src/nsInProcessTabChildGlobal.cpp:334 ... 37 libxul.so mozilla::ShutdownXPCOM xpcom/build/nsXPComInit.cpp:637 38 libxul.so NS_ShutdownXPCOM_P xpcom/build/nsXPComInit.cpp:595 39 libxul.so ScopedXPCOMStartup::~ScopedXPCOMStartup toolkit/xre/nsAppRunner.cpp:1119 Since this is just the script caching breaking (sCachedScripts is null), I'm hoping we can change a couple lines and avoid this: >620 nsFrameScriptExecutorJSObjectHolder* holder = sCachedScripts->Get(aURL); >703 sCachedScripts->Put(aURL, holder);
Assignee | ||
Updated•13 years ago
|
Component: General → IPC
Product: Fennec → Core
QA Contact: general → ipc
Comment 1•13 years ago
|
||
Add a null check?
Assignee | ||
Comment 2•13 years ago
|
||
Attachment #511039 -
Flags: review?(Olli.Pettay)
Comment 3•13 years ago
|
||
Comment on attachment 511039 [details] [diff] [review] Avoid caching frame scripts during xpcom shutdown. Could you just return early if !sCachedScripts?
Assignee | ||
Comment 4•13 years ago
|
||
Do you really want to just not execute the script if we can't cache it? Granted, this is during shutdown, but it makes me nervous.
Comment 5•13 years ago
|
||
We shouldn't run any new scripts during shutdown, IMO.
Assignee | ||
Comment 6•13 years ago
|
||
When you say new, do you mean never-seen-before, or just scripts in general? Because there's no way to determine if a script is new or not, as we've destroyed the script cache.
Comment 7•13 years ago
|
||
I mean we shouldn't allow executing nsFrameScriptExecutor::LoadFrameScriptInternal. The whole DOM and layout has been already shutdown if sScriptCacheCleaner is null.
Assignee | ||
Comment 8•13 years ago
|
||
Assignee | ||
Comment 9•13 years ago
|
||
Attachment #512823 -
Flags: review?(Olli.Pettay)
Assignee | ||
Updated•13 years ago
|
Attachment #511039 -
Attachment is obsolete: true
Attachment #511039 -
Flags: review?(Olli.Pettay)
Assignee | ||
Updated•13 years ago
|
Attachment #512822 -
Attachment is obsolete: true
Updated•13 years ago
|
Attachment #512823 -
Flags: review?(Olli.Pettay) → review+
Assignee | ||
Comment 10•13 years ago
|
||
Comment on attachment 512823 [details] [diff] [review] Avoid caching frame scripts during xpcom shutdown. This is a safe crash-on-shutdown fix that was popping up fairly regularly in b4 crash stats.
Attachment #512823 -
Flags: approval2.0?
Updated•13 years ago
|
Attachment #512823 -
Flags: approval2.0? → approval2.0+
Updated•13 years ago
|
Assignee: nobody → josh
Assignee | ||
Updated•13 years ago
|
Keywords: checkin-needed
Assignee | ||
Comment 11•13 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/5534fbe5e318
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•13 years ago
|
Keywords: checkin-needed
Updated•13 years ago
|
Crash Signature: [@ PL_DHashTableOperate | nsFrameScriptExecutor::LoadFrameScriptInternal]
You need to log in
before you can comment on or make changes to this bug.
Description
•