Closed Bug 43472 Opened 24 years ago Closed 24 years ago

crashes on exit in recent fullcircle builds [@ ViewportFrame::Destroy or nsContainerFrame::Destroy]

Categories

(Core :: Layout, defect, P1)

Product:
Core
Component:
Layout
Platform:
Other
Linux
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: namachi, Assigned: talkback)

References

Details

(4 keywords, Whiteboard: [nsbeta2-][nsbeta3+][pdtp1])

Crash Data

Attachments

(1 file)

Fix for crash on exit
(deleted), patch
Details | Diff | Splinter Review 
0x80410014

    0x80410014 dbdbda2e
         line 
        Build: 2000061908 CrashDate: 2000-06-19 UptimeMinutes: 37
Total: 37 
        OS: MacOS version 9.0
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12693224

    0x80410014 dbdbda2e
         line 
        Build: 2000062008 CrashDate: 2000-06-20 UptimeMinutes: 13
Total: 13 
        OS: MacOS version 9.0
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12760015

    0x80410014 dbdbda2e
         line 
        Build: 2000062008 CrashDate: 2000-06-20 UptimeMinutes: 2
Total: 2 
        OS: MacOS version 9.0.4
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12760018

    0x80410014 dbdbda2e
         line 
        Build: 2000062108 CrashDate: 2000-06-21 UptimeMinutes: 3
Total: 12 
        OS: MacOS version 9.0
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12827837

    0x80410014 dbdbda2e
         line 
        Build: 2000062108 CrashDate: 2000-06-21 UptimeMinutes: 12
Total: 12 
        OS: MacOS version 8.6
        URL: 
        Comment: 7
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12829174

    0x80410014 dbdbda2e
         line 
        Build: 2000062108 CrashDate: 2000-06-21 UptimeMinutes: 27
Total: 39 
        OS: MacOS version 8.6
        URL: 
        Comment: 7
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12830875

    0x80410014 dbdbda2e
         line 
        Build: 2000062108 CrashDate: 2000-06-21 UptimeMinutes: 7
Total: 112 
        OS: MacOS version 8.6
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12841929

    0x80410014 dbdbda2e
         line 
        Build: 2000062108 CrashDate: 2000-06-21 UptimeMinutes: 277
Total: 277 
        OS: MacOS version 9.0
        URL: 
        Comment: .
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12841943

    0x80410014 dbdbda2e
         line 
        Build: 2000062108 CrashDate: 2000-06-21 UptimeMinutes: 1
Total: 1 
        OS: MacOS version 8.6
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12847391

Stack Trace :-

ncident ID 12827837 
0x80410014 
ViewportFrame::Destroy() [nsViewportFrame.cpp] 
FrameManager::~FrameManager() [nsFrameManager.cpp] 
FrameManager::Release() [nsFrameManager.cpp] 
PresShell::~PresShell() [nsPresShell.cpp] 
PresShell::Release() [nsPresShell.cpp] 
nsCOMPtr_base::~nsCOMPtr_base() [nsCOMPtr.cpp] 
DocumentViewerImpl::~DocumentViewerImpl() [nsDocumentViewer.cpp] 
DocumentViewerImpl::Release() [nsDocumentViewer.cpp] 
nsCOMPtr_base::assign_with_AddRef() [nsCOMPtr.cpp] 
.__as__28nsCOMPtr<16nsIContentViewer>FP16nsIContentViewer [nsCOMPtr.h] 
nsDocShell::Destroy() [nsDocShell.cpp] 
nsWebShell::Destroy() [nsWebShell.cpp] 
nsXULWindow::Destroy() [nsXULWindow.cpp] 
nsWebShellWindow::Destroy() [nsWebShellWindow.cpp] 
nsWebShellWindow::Close() [nsWebShellWindow.cpp] 
nsAppShellService::~nsAppShellService() [nsAppShellService.cpp] 
nsAppShellService::Release() [nsAppShellService.cpp] 
nsXPCWrappedNative::~nsXPCWrappedNative() [xpcwrappednative.cpp] 
nsXPCWrappedNative::Release() [xpcwrappednative.cpp] 
nsXPCWrappedNative::JSObjectFinalized() [xpcwrappednative.cpp] 
WrappedNative_Finalize() [xpcwrappednativejsops.cpp] 
js_FinalizeObject() [jsobj.c] 
js_GC() [jsgc.c] 
js_ForceGC() [jsgc.c] 
js_DestroyContext() [jscntxt.c] 
JS_DestroyContext() [jsapi.c] 
mozJSComponentLoader::~mozJSComponentLoader() [mozJSComponentLoader.cpp] 
mozJSComponentLoader::Release() [mozJSComponentLoader.cpp] 
nsSupportsHashtable::ReleaseElement() [nsHashtable.cpp] 
_hashEnumerate() [nsHashtable.cpp] 
PL_HashTableEnumerateEntries() [plhash.c] 
nsHashtable::Enumerate() [nsHashtable.cpp] 
nsSupportsHashtable::~nsSupportsHashtable() [nsHashtable.cpp] 
nsComponentManagerImpl::Shutdown() [nsComponentManager.cpp] 
NS_ShutdownXPCOM() [nsXPComInit.cpp] 
main() [nsAppRunner.cpp] 
.__start
Adding keywords crash, topcrash
Keywords: crash, topcrash
With User Comments :-

0x80410014

    0x80410014 dbdbda2e
         line 
        Build: 2000062108 CrashDate: 2000-06-21 UptimeMinutes: 7
Total: 112 
        OS: MacOS version 8.6
        URL: 
        Comment: Crash quitting aim on mac
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12841929

    0x80410014 dbdbda2e
         line 
        Build: 2000062008 CrashDate: 2000-06-20 UptimeMinutes: 2
Total: 2 
        OS: MacOS version 9.0.4
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12760018

    0x80410014 dbdbda2e
         line 
        Build: 2000062008 CrashDate: 2000-06-20 UptimeMinutes: 13
Total: 13 
        OS: MacOS version 9.0
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12760015

    0x80410014 dbdbda2e
         line 
        Build: 2000062108 CrashDate: 2000-06-21 UptimeMinutes: 277
Total: 277 
        OS: MacOS version 9.0
        URL: 
        Comment: Not sure if I did anything much before Exit
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12841943

    0x80410014 dbdbda2e
         line 
        Build: 2000062108 CrashDate: 2000-06-21 UptimeMinutes: 3
Total: 12 
        OS: MacOS version 9.0
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12827837

    0x80410014 dbdbda2e
         line 
        Build: 2000062108 CrashDate: 2000-06-21 UptimeMinutes: 1
Total: 1 
        OS: MacOS version 8.6
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12847391

    0x80410014 dbdbda2e
         line 
        Build: 2000062108 CrashDate: 2000-06-21 UptimeMinutes: 27
Total: 39 
        OS: MacOS version 8.6
        URL: 
        Comment: crash quitting browser again
Mac 2000-06-21-08M1
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12830875

    0x80410014 dbdbda2e
         line 
        Build: 2000061908 CrashDate: 2000-06-19 UptimeMinutes: 37
Total: 37 
        OS: MacOS version 9.0
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12693224

    0x80410014 dbdbda2e
         line 
        Build: 2000062108 CrashDate: 2000-06-21 UptimeMinutes: 12
Total: 12 
        OS: MacOS version 8.6
        URL: 
        Comment: Crash quitting browser on Mac 2000-06-21-08M1
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=12829174
Summary: crashes on the recent builds. → crashes on exit in the recent builds.
Changing platform to all.  On Linux, I get a crash on exit absolutely every time
with today's or yesterday's commercial release build.  I've filed lots of
talkback reports.
OS: Mac System 9.0 → All
Hardware: Macintosh → All
Here are some talkback reports:

http://cyclone/reports/incidenttemplate.CFM?reportID=124&style=0&tc=4&cp=1&ck1=S
User+email+address&cd1=%25akkana%25&co1=like&bbid=13216795

http://cyclone/reports/incidenttemplate.CFM?reportID=124&style=0&tc=4&cp=3&ck1=S
User+email+address&cd1=%25akkana%25&co1=like&bbid=13143445

http://cyclone/reports/incidenttemplate.CFM?reportID=124&style=0&tc=4&cp=4&ck1=S
User+email+address&cd1=%25akkana%25&co1=like&bbid=13133336

and here's a stack trace (they're all the same):

 Call Stack:    (Signature = nsContainerFrame::Destroy() 88f8030c)
   nsContainerFrame::Destroy() 
   ViewportFrame::Destroy()
   FrameManager::~FrameManager()
   FrameManager::Release()
   PresShell::~PresShell()
   PresShell::Release() 
   nsCOMPtr_base::~nsCOMPtr_base()
   DocumentViewerImpl::~DocumentViewerImpl()
   DocumentViewerImpl::Release()
   nsCOMPtr_base::assign_with_AddRef()
   nsDocShell::Destroy()
   nsWebShell::Destroy() 
   nsXULWindow::Destroy()
   nsWebShellWindow::Destroy()
   nsWebShellWindow::Close()
[...]

A debug mozilla build says:

XXX WARNING: Number of webshells being leaked: 1 

but does not crash on exit.
over to layout for further triage.
Assignee: asa → clayton
Component: Browser-General → Layout
QA Contact: doronr → petersen
What really scares me is the report with "UptimeMinutes: 1"

upping severity, nominating for beta2
Severity: normal → critical
Keywords: nsbeta2
This is a more general bug report of the crash that is reported in bug 41339 
which is marked nsbeta2+.

Marking this bug nsbeta2+ and marking 41339 as a dup of this bug...
Whiteboard: [nsbeta2+]
*** Bug 41339 has been marked as a duplicate of this bug. ***
Re-assigning to myself for a more detailed triage...  CCing karnaze and 
waterson, the layout guys for input.
Assignee: clayton → nisheeth
I cannot reproduce this in today's morning NT commercial debug build.  Is 
someone else seeing this?  Marking qawanted and updating status whiteboard.
Keywords: qawanted
Whiteboard: [nsbeta2+] → [nsbeta2+] Cannot reproduce.
I still see this every single time I exit with the 6/30 release build.  You're
welcome to try it on my machine (I've submitted several fullcircle reports
already).  Removing qawanted if my assumption is right that it means "need help
reproducing".
Keywords: qawanted
Updating OS to Linux.  Akkana, does your debug build crash on exit, too?
OS: All → Linux
Whiteboard: [nsbeta2+] Cannot reproduce. → [nsbeta2+]
Updating status whiteboard...
OS: Linux → All
No, my debug build doesn't; just the release, commercial, fullcircle build.
OS: All → Linux
Whiteboard: [nsbeta2+] → [nsbeta2+] Will look at on 7/5/00
Akkana has fired off an optimized build with debug symbols for me.  I'll use
that to investigate this more on Wednesday....
I have a debug commercial build available -- but it doesn't crash on exit.  Only
the release build (with fullcircle) seems to have a problem, and today's
fullcircle build still calls up a fullcircle build on exit.  Could this be a
fullcircle-introduced instability?  (I haven't tried making an optimized
commercial build, though; I could do that, if you think it's worthwhile.)

My debug build, if you want it for anything, is on guitar at /builds/commercial.
Summary: crashes on exit in the recent builds. → crashes on exit in recent fullcircle builds
Are you able to submit the crash report ? 

Yes.  I've submitted at least ten so far (one from today's build).
One thing I should have mentioned is that although I don't crash with my
commercial debug build, I do get a couple of asserts when exiting:

###!!! ASSERTION: NS_ENSURE_TRUE(aPropertyName) failed: 'aPropertyName', file
nsFrameManager.cpp, line 1776
###!!! Break: at file nsFrameManager.cpp, line 1776
###!!! ASSERTION: NS_ENSURE_TRUE(aPropertyName) failed: 'aPropertyName', file
nsFrameManager.cpp, line 1776
###!!! Break: at file nsFrameManager.cpp, line 1776

Strangely, I don't get them when running under the debugger.
Actually, Akkana, it would be helpful to have an optimized build with debug 
symbols.  Could you fire that off for me?  Thanks a lot.
Whiteboard: [nsbeta2+] Will look at on 7/5/00 → [nsbeta2+] Awaiting optimized build with debug symbols
Since this crash happens in Linus as well as Mac I am changing the OS to all.
Commonly reproducible in the following :-
        OS: MacOS version 8.6
        OS: MacOS version 9.0.4
        OS: Linux 2.2.14-5.0smp




Latest update from Talkback:

    0x80410014 dbdbda2e
         line 
        Build: 2000070511 CrashDate: 2000-07-05 UptimeMinutes: 1  Total:
7 
        OS: MacOS version 8.6
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=13663627

    0x80410014 dbdbda2e
         line 
        Build: 2000070608 CrashDate: 2000-07-06 UptimeMinutes: 77
Total: 117 
        OS: MacOS version 9.0
        URL: 
        Comment: crash on qui
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=13720935

    0x80410014 dbdbda2e
         line 
        Build: 2000070511 CrashDate: 2000-07-06 UptimeMinutes: 0  Total:
4 
        OS: MacOS version 9.0.4
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=13707931

    0x80410014 dbdbda2e
         line 
        Build: 2000070511 CrashDate: 2000-07-06 UptimeMinutes: 0  Total:
5 
        OS: MacOS version 9.0.4
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=13707980

    0x80410014 dbdbda2e
         line 
        Build: 2000070511 CrashDate: 2000-07-06 UptimeMinutes: 0  Total:
6 
        OS: MacOS version 9.0.4
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=13708578


--------------------------

Linux Crash reports. 


   nsContainerFrame::Destroy() 88f8030c
         line 
        Build: 2000070508 CrashDate: 2000-07-05 UptimeMinutes: 0  Total: 0 
        OS: Linux 2.2.14-5.0smp
        URL: about:blank
        Comment: 7/5 build: start up on about:blank
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=13657936

    nsContainerFrame::Destroy() 53efab9b
         line 
        Build: 2000070320 CrashDate: 2000-07-04 UptimeMinutes: 17  Total: 52 
        OS: Linux 2.2.14-5.0
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=13586820

    nsContainerFrame::Destroy() e496227d
         line 
        Build: 2000070508 CrashDate: 2000-07-05 UptimeMinutes: 25  Total: 76 
        OS: Linux 2.2.5-22
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=13660448

    nsContainerFrame::Destroy() e496227d
         line 
        Build: 2000070420 CrashDate: 2000-07-05 UptimeMinutes: 109  Total: 109 
        OS: Linux 2.2.5-15
        URL: 
        Comment: 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=13649066

    nsContainerFrame::Destroy() 35fefdca
         line 
        Build: 2000070608 CrashDate: 2000-07-06 UptimeMinutes: 1  Total: 282 
        OS: Linux 2.2.12-20
        URL: 
        Comment: linux 
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=13734678

    nsContainerFrame::Destroy() 5baf15ee
         line 
        Build: 2000070608 CrashDate: 2000-07-06 UptimeMinutes: 529  Total: 529 
        OS: Linux 2.2.5-22
        URL: 
        Comment: crash on qui
        Stacktrace: 
http://cyclone/reports/stackcommentemail.cfm?dynamicBBID=13735757
OS: Linux → All
*** Bug 39858 has been marked as a duplicate of this bug. ***
nisheeth, could you put an ETA in this bug so that we can mark the ETA in the 
dependent AIM bug as well. thanks, Vishy
I'm doing an optimized build with debug symbols to debug this today and will add 
an ETA as soon as I have a handle on the problem.
Status: NEW → ASSIGNED
Whiteboard: [nsbeta2+] Awaiting optimized build with debug symbols → [nsbeta2+]
Eric Pollmann and I couldn't reproduce this with today's commercial build on our 
linux boxes which are running linux 2.2.12-20.  Mike Pinkerton is running Mac OS 
9.0.4 and he couldn't reproduce the crash on exit with today's commercial 
build either.  I went up to Akkana's machine which is running linux 
2.2.14-5.0smp and the crash is reproducable there.

Given that this crash is not reproducable on all machines, we should probably 
not consider this a beta 2 stopper.  I'm removing the beta2+ designation and 
adding a nsbeta3 keyword.

Chris (Petersen), it would be great if we could get some QA on this bug and see 
whether we get a crash on exit on commercial builds with fullcircle enabled on 
different Linux and Mac kernels.
Keywords: nsbeta3, qawanted
Whiteboard: [nsbeta2+]
Per recent data.  Putting on [nsbeta2-]
Whiteboard: [nsbeta2-]
I smoketested today's build (2000-07-13-08-M17 commercial) and i got a crash on 
file|quit on Linux and Mac and not on Win32.
Can we get this reevaluated?  I know it's hard to track down and all that, but
it's not just my machine, and we're going to look really bad if we release a
beta where the user can't exit without getting a fullcircle dialog every time.  

We have *lots* of fullcircle reports on this crash.  If fullcircle reports
aren't useful for helping to track down crashes, why are we inflicting them on
users?
Whiteboard: [nsbeta2-]
I agree with akkana.  I think this bug should be nsbeta2+ given that other 
people are seeing this crash too...
Summary: crashes on exit in recent fullcircle builds → crashes on exit in recent fullcircle builds [@ ViewportFrame::Destroy]
Putting on [nsbeta2+] radar for beta2 fix.
Whiteboard: [nsbeta2+]
Summary: crashes on exit in recent fullcircle builds [@ ViewportFrame::Destroy] → crashes on exit in recent fullcircle builds [@ ViewportFrame::Destroy or nsContainerFrame::Destroy]
sound like we just need to make a debug build,
drop the fullcircle binaries and master.ini
into the debug build tree and run the exit test
case to figure see if the full circle binaries
are creating the instability.

Steps tried to reproduce :-

Created a Mozilla Debug Build
Created Netscape Commerical Debug Build with fullcircle enabled
Copied master.ini
Launched Netscape6 and ran with few pages and exited.
No crash. 

Next Step:-
Build Mozilla Optimized Build with Symbols.
Build Netscape Commercial Optimized Build with Symbols and fullcircle enabled.
and Same steps as above case.

Hope I can reproduce. Anybody have other ideas ?


I'll be glad to try running anyone's build on my machine, if you want to make it
available -- just let me know where to NFS mount or ftp the build.
So, I built an optimized build with debug symbols on Linux.  I ran the build and
exited and did not see a crash.  I've added my build directory to /etc/exports,
Akkana, so you can nfs mount /builds on anubis and get to the build.  The full
path is /builds/nisheeth/ns/dist/bin.  Please update the bug report with what
you find when you run this build from your machine.  If you see the crash on
exit, we can debug this together tomorrow.  Thanks!
Updating status white board - the ETA is indeterminate until this problem is
reproducable in a debuggable build.
Whiteboard: [nsbeta2+] → [nsbeta2+] ETA - indeterminate until this is reproducable in a debuggable build
Still seen on commercial Linux with build 2000-07-19-08-M17, but i do not see a 
crash using commercial Mac anymore
Unfortunately, I don't seem to see it on the anubis build.  I'll try a few more
times, but it's not looking good.
Alek, I've made a tarball (ns.tar.gz) of a fullcircle enabled optimized build 
with debug symbols available in my home directory (/u/nisheeth).  Please install 
it on the box where you were able to reproduce the crash and run it.  If you can 
reproduce the crash with this build, we can try and debug this tomorrow evening.  
I will be away during the day for a class.
Turns out Alek wasn't on the cc list.  Adding him.  Alek, please see my comment 
on this bug right before this one.  Thanks!
*** Bug 45842 has been marked as a duplicate of this bug. ***
news steps to reproduce the crash on linux:
-start browser
-File|Open File
-let it open a file in a new browser
-then in either browser window File|Quit *NOTE*: its crashes on only File|Quit
-100% reproducible

Attaching a patch that fixes this crash.  Can somebody on the cc list please
code review this?  Thanks.
Attached patch Fix for crash on exit (deleted) — — Splinter Review 

    
    

    
  
Updating status whiteboard...
Whiteboard: [nsbeta2+] ETA - indeterminate until this is reproducable in a debuggable build → [nsbeta2+] Fix in hand.  Awaiting code review.

    
    

    
  
The fix is checked in.  r=rpotts.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED

    
    

    
  
no longer seen on any platforms with commercial builds 2000-07-24-08-M17 
Status: RESOLVED → VERIFIED

    
    

    
  
Really?  I'm still seeing the crash with the 7/24 sweetlou commercial build.

I'll try downloading one later today.  Maybe I got mislabelled bits or something
(wouldn't be the first time that had happened).

    
    

    
  
i've ran through the whole browser test File|Quiting after every test case and 
can't reproduce a crash using build 2000-07-24-08-M17 
Akkana: maybe the crash is specific to your computer.

    
    

    
  
Is this problem due to smp ?

    
    

    
  
Not SMP: I only have a single processor.

Using today's build as dogfood, I'm seeing a LOT of crashes doing practically
everything.  In addition to the crash on exit, which still happens, I've been
getting random crashes in practically every area of the product, perhaps every
20-30 minutes.

I've switched to the mozilla build (no fullcircle); so far I've seen one crash,
which isn't enough to tell for sure whether it's more stable or not.

    
    

    
  
Akkana, your machine is Single processor machine. My suspicion is the kernel
is smp.(I may be wrong). The following information I got from Talkback incident.
This could be the reason.

 System Information: 
 Linux
 2.2.14-5.0smp
 #1 SMP Tue Mar 7 21:01:40 EST 2000



    
    

    
  
This is the standard kernel that Redhat 6.2 installs.  I did a vanilla Redhat
6.2 install and haven't changed the kernel.

    
    

    
  
Note, I'm still seeing this in the 7/28 build, though it's a little more
difficult to reproduce.

Here's how I make it happen:

1. Make sure I have a chrome directory under my profile directory.  It doesn't
happen if I move my chrome directory aside.  (Users will have a chrome directory
if they've mucked with themes, or if they've installed a user.css.  It's not my
user.css causing the problem -- moving it aside doesn't make the crash go away,
only moving the whole chrome directory, and there's nothing else of note in the
chrome directory.)
2. Run mozilla http://www.mozilla.org
3. Click on the mail icon in the taskbar to bring up a mail window.
4. When Inbox has loaded (mine is IMAP, probably doesn't matter), click on a
message to read it.
5. Click on another message to read that one.  (I have to read a second message
or I don't see the crash.)
6. Alt-Q to exit.
A fullcircle dialog will come up.

I'm going to reopen since the crash is still completely reproducible for me.

Note: may possibly be related to bug 46849, which I just filed.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---

    
    

    
  
Are the new steps still worthy of nsbeta2+?  Or can we relnote it?
Whiteboard: [nsbeta2+] Fix in hand.  Awaiting code review.

    
    

    
  
Probably okay to relnote it, hoping people won't play with skins much, or
anything else that might make a chrome directory.

    
    

    
  
Does it crash on exit is you use Close Box instead of File/Quit?
Whiteboard: [NEED INFO]

    
    

    
  
No, doesn't happen if you close the windows one at a time instead of exiting the
app.

    
    

    
  
Putting on [nsbeta2-] radar.  Not critical to beta2.  Adding "relnote" keyword 
for PR2 release. 
Keywords: relnote, 
          
            relnote2
Whiteboard: [NEED INFO] → [nsbeta2-]

    
    

    
  
seen on linux m18 build 2000-08-09-08-M18

    
    

    
  
Putting on dogfood+...can we get this fixed ASAP?
Whiteboard: [nsbeta2-] → [dogfood+][nsbeta2-]

    
    

    
  
this is on Linux only.  Updating OS info.
OS: All → Linux
Hardware: All → Other

    
    

    
  
Marking nsbeta3+
Status: REOPENED → ASSIGNED
Whiteboard: [dogfood+][nsbeta2-] → [dogfood+][nsbeta2-][nsbeta3+]

    
    

    
  
Please add an ETA for the dogfood+ bugs.  Thanks, PDT

    
  
Keywords: pp

    
    

    
  
Adding ETA...  I don't think that this should be a dogfood bug because a crash 
on exit does not hamper the usability of the product.  Removing the dogfood+ 
marker and keeping it on the beta 3 radar.
Whiteboard: [dogfood+][nsbeta2-][nsbeta3+] → [nsbeta2-][nsbeta3+] ETA - 8/15/00

    
    

    
  
It only hampers usability of the product if there are prefs/rdf/other info which
only get saved on exit.  I'm not sure whether that's currently the case.  A lot
of our prefs seem to get written out as soon as they are changed, and if so,
this bug becomes much more minor (in fact, if we turned off fullcircle, users
wouldn't even know there was a problem).

    
    

    
  
Does it core dump when fullcircle is removed ?

    
    

    
  
Yes, but since current versions of Linux don't save core files for multithreaded
apps, the user doesn't know it has core dumped; it just looks like a normal
exit.  The only clue/annoyance the user has that anything is wrong is the
fullcircle dialog coming up.

    
    

    
  
Marking P1...
Priority: P3 → P1

    
    

    
  
PDT agrees P1 with some dissension :-)

    
    

    
  
Putting [pdtp1] in whiteboard
Whiteboard: [nsbeta2-][nsbeta3+] ETA - 8/15/00 → [nsbeta2-][nsbeta3+][pdtp1] ETA - 8/15/00

    
  
Whiteboard: [nsbeta2-][nsbeta3+][pdtp1] ETA - 8/15/00 → [nsbeta2-][nsbeta3+][pdtp1]

    
    

    
  
I changed themes from the preferences menu and then went through the 6 steps
listed in Akkana's post timestamped 7/28/2000 14:02 on an optimized, full circle
enabled Linux build with debug symbols.  I could not reproduce the crash on
exit.

Akkana, my build is located on "g" in /export/nisheeth/ns/dist/bin.  Could you
run it from your user account and see if you can reproduce the crash?

Also, Akkana mentioned in her post cited above that the crash could be related
to bug 46489.  That bug has been fixed since then, so, maybe this crash on exit
has been fixed as a result.

    
    

    
  
I don't see a fullcircle dialog when I go through the steps with this build.

I do see an assertion at shutdown:

###!!! ASSERTION: Component Manager being held past XPCOM shutdown.: 'cnt == 0',
file nsXPComInit.cpp, line 667
###!!! Break: at file nsXPComInit.cpp, line 667

but there doesn't seem to be a crash associated with it.

    
    

    
  
Akkana just tested a commercial build on her box and that does not crash any
more either.  Marking bug worksforme.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → WORKSFORME

    
    

    
  
verifying. using linux 2000-09-26-09-MN6 mozilla build, Mozilla doesn't crash on
exit.

Status: RESOLVED → VERIFIED

    
    

    
  
Moving all the Works For Me bugs to talkback user account for future reference.

Assignee: nisheeth → talkback
Status: VERIFIED → NEW

    
    

    
  
We are gathering all the Resolved and WFM bugs which are happened to be topcrash 
bugs and assigning it to talkback. I am marking all of them as RESOLVED WFM.
Status: NEW → RESOLVED
Closed: 24 years ago → 24 years ago
Crash Signature: [@ ViewportFrame::Destroy or nsContainerFrame::Destroy]
Keywords: qawanted

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: