Closed
Bug 202439
Opened 22 years ago
Closed 22 years ago
frequent crashes when closing/dismissing windows - Trunk [@ nsDocShell::Destroy]
Categories
(SeaMonkey :: UI Design, defect)
SeaMonkey
UI Design
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: bugzilla, Assigned: Brade)
References
Details
(Keywords: crash, regression, topcrash)
Crash Data
Attachments
(4 files)
i've noticed that with the 2003.04.17.09 build (on linux rh8.0, so far) i've
been crashing quite often when i've closed various windows. unfortunately, i
haven't found a consistent set of steps --other than closing windows-- and the
stack traces vary. :( but after encountering three crashes within ~30min, i
thought it couldn't hurt to file a bug. ;) pls reassign or dup as needed.
i'll attach the talkback reports soon.
here is what i've done when i've encountered the crash:
a. had multiple tabs open (3 or 4) and clicked the close widget to close one of
the tabs.
b. had a browser and help window open, and hit ctrl+w to close the help window.
c. had a browser and editor window open, and hit ctrl+w to close the editor window.
Reporter | ||
Comment 1•22 years ago
|
||
Reporter | ||
Comment 2•22 years ago
|
||
Reporter | ||
Comment 3•22 years ago
|
||
Reporter | ||
Comment 4•22 years ago
|
||
this wasn't a problem with the 2003.04.15.08 build.
Comment 5•22 years ago
|
||
A crash also occurs when the window closes as the result of some other action,
such as clicking on the send button in Mail/News.
Comment 6•22 years ago
|
||
I'm seeing this on Linux 8.0 with the 2003041709 build.
Reporter | ||
Comment 7•22 years ago
|
||
leston has a good point --i also crashed when i dismissed the table properties
dlg (clicked OK button).
Summary: frequent crashes when closing windows → frequent crashes when closing/dismissing windows
Comment 8•22 years ago
|
||
I've seen a few crashes in 20030417 when hitting "send" in mailnews; this is
closing the compose window, of course. No further details as yet.
Was OK in 20030416.
Comment 9•22 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030417
See Talkback ID's: TB19252388M and TB19252199Q
Reporter | ||
Updated•22 years ago
|
OS: Linux → All
![]() |
||
Comment 10•22 years ago
|
||
Can someone get a narrower regression range (12 hours would be good...)?
The stacks all end on line 1248 of nsWebShell; the only reason that should crash
is if we call Destroy() on an already-deleted webshell....
Comment 11•22 years ago
|
||
I have a build 2003041619 which works (that's 7pm BST == GMT + 1)
It would help if I could turn on talkback for my cvs builds; is this possible?
Reporter | ||
Comment 12•22 years ago
|
||
i've been playing with the 2003.04.17.05 mozilla build (linux rh8.0) for about
20min and have yet to crash. has anyone experienced crashes with that particular
build?
![]() |
||
Comment 13•22 years ago
|
||
> It would help if I could turn on talkback for my cvs builds; is this possible?
How about you just enable symbols and use a debugger? That'll let you tell me
pretty much anything that talkback can and possibly more.... ;)
Comment 14•22 years ago
|
||
Build ID 2003041709 crashes on Win98 when closing a tab, DocWatson & Talkback
are coming up:
TB19257114Z
TB19257156E
TB19257307Z
corresponding Stack Summaries from DocWatson
(can someone give me a hint how to copy&paste this data from file.wlg?)
0167:0009
DOCSHELL.DLL:.text+0x2436
GKLAYOUT.DLL:.text+0x1b71a4
GKLAYOUT.DLL:.text+0x81b8a
0167:028ac46e
DOCSHELL.DLL:.text+0x2474
GKLAYOUT.DLL:.text+0x1b71a4
GKLAYOUT.DLL:.text+0x81b8a
GKLAYOUT.DLL:.rdata+0xd2c0
DOCSHELL.DLL:.text+0x2474
GKLAYOUT.DLL:.text+0x1b71a4
GKLAYOUT.DLL:.text+0x81b8a
Comment 15•22 years ago
|
||
*** Bug 202479 has been marked as a duplicate of this bug. ***
Comment 16•22 years ago
|
||
WORKING 2003041704 Win98 (until now, will post again, when it crashes)
crashes 2003041709 Win98
Had just installed build ID 2003041704, and had no crashes in the time I had ten
with the newer build.
But it came up with an oversized window, or two, and with an empty toolbar.
Normally I´ve got lots of BookmarksFolders in my personal Toolbar.
I deleted a window, maximized the rest, entered manually a URL, but DUN wasn´t
starting, so I stopped Mozilla.
At second start of Mozilla Personal Toolbar was ok, I selected one of the
bookmarks from there, DUN started, all was going well.
Comment 17•22 years ago
|
||
*** Bug 202484 has been marked as a duplicate of this bug. ***
Comment 18•22 years ago
|
||
-> blocker (I crash evertime i close a tab or window)
Severity: critical → blocker
![]() |
||
Comment 19•22 years ago
|
||
Hermann, thanks for getting that regression window! Over to brade as the
honorary "only person to touch docshell in that time period"; reading over the
diffs now.
Assignee: jaggernaut → brade
![]() |
||
Comment 20•22 years ago
|
||
mozilla% cvs diff -u -r 1.538 -r 1.539 docshell/base/nsDocShell.cpp
- NS_IF_RELEASE(NS_STATIC_CAST(nsIClipboardDragDropHookList *,
mTransferableHookData));
+ nsIClipboardDragDropHookList *list =
NS_STATIC_CAST(nsIClipboardDragDropHookList *, mTransferableHookData);
+ NS_IF_RELEASE(list);
delete mTransferableHookData;
mTransferableHookData = nsnull;
So the old code would NS_IF_RELEASE mTransferableHookData, which called
Release() on it and nulled out the pointer ('cause that's what NS_IF_RELEASE
does). Then the |delete 0;| and |mTransferableHookData = nsnull;| were no-ops.
With this change, we release the mTransferableHookData (which will sometimes
call its destructor, if we're holding the last ref). Then we delete it (which
either deletes an object someone holds a ref to or double-deletes an object we
held the last ref to). Then we set it to null (if we ever get to that line
without crashing).
Removing the "delete" line made the crashes go away here.
Not posting a patch because I can't tell whether you mean to NS_RELEASE here or
just delete explicitly. I _suspect_ you want the former...
(My personal preference here would be to change the member variable into an
|nsCOMPtr<nsTransferableHookData> or even an
|nsCOMPtr<nsIClipboardDragDropHookList>| (since we never access this thing as an
nsTransferableHookData) and dispense with the manual memory-management, make
GetInterface just CallQI on the member or assign directly out of it, etc.)
Keywords: zt4newcrash
Hardware: PC → All
Comment 21•22 years ago
|
||
Assignee | ||
Comment 22•22 years ago
|
||
Comment on attachment 120926 [details] [diff] [review]
Patch to fix docshell hooks
other than some whitespace differences, this is what I had
Attachment #120926 -
Flags: review+
Comment 23•22 years ago
|
||
Checked in.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 24•22 years ago
|
||
*** Bug 202526 has been marked as a duplicate of this bug. ***
Comment 25•22 years ago
|
||
*** Bug 202524 has been marked as a duplicate of this bug. ***
![]() |
||
Comment 26•22 years ago
|
||
*** Bug 202666 has been marked as a duplicate of this bug. ***
Comment 27•22 years ago
|
||
Adding topcrash info for future reference. Also, no crashes since 4/17
checkin... marking verified based on Talkback data.
Status: RESOLVED → VERIFIED
Keywords: topcrash
Summary: frequent crashes when closing/dismissing windows → frequent crashes when closing/dismissing windows - Trunk [@ nsDocShell::Destroy]
Comment 28•22 years ago
|
||
*** Bug 202929 has been marked as a duplicate of this bug. ***
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
Updated•14 years ago
|
Crash Signature: [@ nsDocShell::Destroy]
You need to log in
before you can comment on or make changes to this bug.
Description
•