Oliver Klee Reporter
	Description • 22 years ago

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021108
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021108

The latest nightly sometimes crashes on quit.

Reproducible: Sometimes

Steps to Reproduce:
1. Open Mozilla MailNews and Navigator.
2. Surf, read some mail.
3. Exit Mozilla.

Actual Results:  
Crash

Expected Results:  
No crash

Talkback IDs:
TB13760592Z
TB13757274Z
TB13747567Z
TB13746932W
TB13746916Z

This is a regression that has startet at some point between 2002-31-10 and
2002-11-08.

	Oliver Klee Reporter
	Comment 1 • 22 years ago

Maybe I should add that
1. I have QuickLaunch enabled
2. QuickLaunch is still useable after this crash

	Oliver Klee Reporter
	Comment 2 • 22 years ago

cc:ing Matti ... could you get the Talkback stack, please? Thanks!

	Matthias Versen [:Matti]
	Comment 3 • 22 years ago

Incident ID:  *   
Incident ID 13746932
Stack Signature 0x626c7275 16e50ccc
Product ID MozillaTrunk
Build ID 2002110808
Trigger Time 2002-11-10 06:09:24
Platform Win32
Operating System Windows NT 5.0 build 2195
Module
URL visited
User Comments quitting Mozilla (with QuickStrat enabled)
Trigger Reason Access violation
Source File Name
Trigger Line No.
Stack Trace

0x626c7275
nsCOMPtr_base::~nsCOMPtr_base 
[d:/builds/seamonkey/mozilla/xpcom/glue/nsCOMPtr.cpp, line 65]
nsHttpConnection::~nsHttpConnection 
[d:/builds/seamonkey/mozilla/netwerk/protocol/http/src/nsHttpConnection.cpp, 
line 92]
nsHttpConnection::`scalar deleting destructor'
nsHttpConnection::Release 
[d:/builds/seamonkey/mozilla/netwerk/protocol/http/src/nsHttpConnection.cpp, 
line 582]
nsHttpTransaction::~nsHttpTransaction 
[d:/builds/seamonkey/mozilla/netwerk/protocol/http/src/nsHttpTransaction.cpp, 
line 121]
nsHttpTransaction::`scalar deleting destructor'
nsHttpTransaction::DeleteSelfOnConsumerThread 
[d:/builds/seamonkey/mozilla/netwerk/protocol/http/src/nsHttpTransaction.cpp, 
line 696]


*Incident ID:  *   
Incident ID 13746916
Stack Signature ntdll.dll + 0x4b8f4 (0x778cb8f4) 3ecf3ceb
Product ID MozillaTrunk
Build ID 2002110808
Trigger Time 2002-11-10 06:08:22
Platform Win32
Operating System Windows NT 5.0 build 2195
Module ntdll.dll
URL visited
User Comments quitting Mozilla
Trigger Reason Access violation
Source File Name
Trigger Line No.
Stack Trace

ntdll.dll + 0x4b8f4 (0x778cb8f4)
ntdll.dll + 0x4b795 (0x778cb795)
MSVCRT.DLL + 0x115c (0x7800115c)
??3@YAXPAX@Z
nsSocketTransport::`scalar deleting destructor'
nsSocketTransport::Release 
[d:/builds/seamonkey/mozilla/netwerk/base/src/nsSocketTransport.cpp, line 1325]
nsCOMPtr_base::~nsCOMPtr_base 
[d:/builds/seamonkey/mozilla/xpcom/glue/nsCOMPtr.cpp, line 65]
nsHttpConnection::~nsHttpConnection 
[d:/builds/seamonkey/mozilla/netwerk/protocol/http/src/nsHttpConnection.cpp, 
line 92]
nsHttpConnection::`scalar deleting destructor'
nsHttpConnection::Release 
[d:/builds/seamonkey/mozilla/netwerk/protocol/http/src/nsHttpConnection.cpp, 
line 582]
nsHttpTransaction::~nsHttpTransaction 
[d:/builds/seamonkey/mozilla/netwerk/protocol/http/src/nsHttpTransaction.cpp, 
line 121]
nsHttpTransaction::`scalar deleting destructor'
nsHttpTransaction::DeleteSelfOnConsumerThread 
[d:/builds/seamonkey/mozilla/netwerk/protocol/http/src/nsHttpTransaction.cpp, 
line 696]
nsHttpTransaction::Release 
[d:/builds/seamonkey/mozilla/netwerk/protocol/http/src/nsHttpTransaction.cpp, 
line 751]
nsCOMPtr_base::~nsCOMPtr_base 
[d:/builds/seamonkey/mozilla/xpcom/glue/nsCOMPtr.cpp, line 65]
nsOnStopRequestEvent::~nsOnStopRequestEvent 
[d:/builds/seamonkey/mozilla/netwerk/base/src/nsRequestObserverProxy.cpp, line 295]
nsOnStopRequestEvent::`scalar deleting destructor'
nsARequestObserverEvent::DestroyPLEvent 
[d:/builds/seamonkey/mozilla/netwerk/base/src/nsRequestObserverProxy.cpp, line 124]
PL_DequeueEvent [d:/builds/seamonkey/mozilla/xpcom/threads/plevent.c, line 713]
PL_DestroyEvent [d:/builds/seamonkey/mozilla/xpcom/threads/plevent.c, line 673]
PL_ProcessPendingEvents [d:/builds/seamonkey/mozilla/xpcom/threads/plevent.c, 
line 582]
nsEventQueueImpl::ProcessPendingEvents 
[d:/builds/seamonkey/mozilla/xpcom/threads/nsEventQueue.cpp, line 393]


-> Darin

	Henrik Gemal
	Comment 4 • 22 years ago

*** Bug 180077 has been marked as a duplicate of this bug. ***

	Wesha
	Comment 5 • 22 years ago

20021104 never crashed for me; 2002111404 does with the described sympthoms.
Hope this'll help you to narrow down the scope.

	Hermann Schwab
	Comment 6 • 22 years ago

Mozilla 1.3a

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a) Gecko/20021114

Downloaded nightly, unzipped in new folder, started, read some bugs, some news,
mail, and when news loaded very slow, and logging in to mailserver was slow,
I closed the browser, closed mail, closed download mgr, closed DUN,
and talkback came up.

TB 13935528K

Good ISDN-Connection, single channel 7.8kbyte/sec download speed,
but slow celeron333 with only 96 MB RAM

No quickstart, but pipelining enabled, browsing with tabs loading in background.
After some time I have to close the browser that it gets faster.
100 MB free on c:/ (tempfile), 500 MB free on E:/ for windows-swap and
mozilla-cache, download directories.

Windows is win98 first edition with servicepack 1 and some other fixes applied.

	Hermann Schwab
	Comment 7 • 22 years ago

Mozilla 1.3a

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a) Gecko/20021114

TB 13935528E
TB 13945920K

:-(

	Darin Fisher Assignee
	Comment 8 • 22 years ago

does anyone seeing this crash have enigmail installed?  we've seen a lot of
mozilla networking crashes caused by enigmail.

	Oliver Klee Reporter
	Comment 9 • 22 years ago

I had installed Enigmail some time ago, but deinstalled it later. The crashes
started a few weeks after deinstalling Enigmail (with a new nightly build).

1.2b and 1.2branch don't crash on quit, BTW.

	Oliver Klee Reporter
	Comment 10 • 22 years ago

Maybe I should add that I do a fresh install from zip every time, erasing all
but the Plugins folder. I may be that Enigmail leaves something in my profile
directory, though.

	Oliver Klee Reporter
	Comment 11 • 22 years ago

New Talkback ID from build 2002112208: TB 14358732X.

If this is of any help: After the crash, I found a prefs.bak file in my Profile,
which is identical to prefs.js.

	Darin Fisher Assignee
	Comment 12 • 22 years ago

here's the stack for incident 14358732:

0x0374cd2b
nsHttpTransaction::Release
[c:/builds/seamonkey/mozilla/netwerk/protocol/http/src/nsHttpTransaction.cpp,
line 751]
nsCOMPtr_base::~nsCOMPtr_base
[c:/builds/seamonkey/mozilla/xpcom/glue/nsCOMPtr.cpp, line 65]
nsOnStopRequestEvent::~nsOnStopRequestEvent
[c:/builds/seamonkey/mozilla/netwerk/base/src/nsRequestObserverProxy.cpp, line 295]
nsOnStopRequestEvent::`scalar deleting destructor'
nsARequestObserverEvent::DestroyPLEvent
[c:/builds/seamonkey/mozilla/netwerk/base/src/nsRequestObserverProxy.cpp, line 124]
PL_DestroyEvent [c:/builds/seamonkey/mozilla/xpcom/threads/plevent.c, line 682]
PL_HandleEvent [c:/builds/seamonkey/mozilla/xpcom/threads/plevent.c, line 657]
PL_ProcessPendingEvents [c:/builds/seamonkey/mozilla/xpcom/threads/plevent.c,
line 578]
nsEventQueueImpl::ProcessPendingEvents
[c:/builds/seamonkey/mozilla/xpcom/threads/nsEventQueue.cpp, line 392] 

oliver: do you also have pipelining enabled?

	Oliver Klee Reporter
	Comment 13 • 22 years ago

Yes, I have pipelining enabled. In addition, I use a local proxy (WebWasher).
I'll try if switching off pipelining stops the crashes.

	Darin Fisher Assignee
	Comment 14 • 22 years ago

well, both you and hermann have pipelining enabled, so chances are pretty good
that this crash is related to pipelining.  otherwise (if pipelining is not a
factor), we'd expect to see more reports of this crash.  but, still please do
let us know if you observe this crash after disabling pipelining.  thx!

	Oliver Klee Reporter
	Comment 15 • 22 years ago

I get the crash even with pipelining disabled.

	Oliver Klee Reporter
	Comment 16 • 22 years ago

OK, disabling pipelining and the proxy does not help for me. Switching off
QuickLaunch doesn't help either.

	Oliver Klee Reporter
	Comment 17 • 22 years ago

I have the impression that I get the crash only when I have opened both MailNews
and Navigator in the same (Mozilla) session, not when I use only one of them.

Wesha, Hermann: Is it the same for you?

	Oliver Klee Reporter
	Comment 18 • 22 years ago

Correction: Navigator only crashes as well, but MailNews only does not.

	Darin Fisher Assignee
	Comment 19 • 22 years ago

*** Bug 182017 has been marked as a duplicate of this bug. ***

	David Bradley
	Comment 20 • 22 years ago

I think this is the same or similar crash. I was closing down. I hadn't run
mailnews, and I'm not sure if I have pipelining enabled or not (I never messed
with the setting, so what ever is the default). On my crash, mConnection was
already deleted, and caused my crash. Hope this helps.

	David Bradley
	Comment 21 • 22 years ago

Oh, almost forgot, this was a build pulled from CVS today

	Darin Fisher Assignee
	Comment 22 • 22 years ago

this appears to be caused by the patch for bug 174131.  i think that patch
probably just uncovered a deeper problem.

	Darin Fisher Assignee
	Comment 23 • 22 years ago

the patch in bug 181230 might help.

	Matthias Versen [:Matti]
	Comment 24 • 22 years ago

*** Bug 181744 has been marked as a duplicate of this bug. ***

	Oliver Klee Reporter
	Comment 25 • 22 years ago

Should this be topcrash+? It looks like these stacks show up on
ftp://ftp.mozilla.org/pub/data/crash-data/seamonkey-crash-analysis-detailed.txt .

	Jay Davis
	Comment 26 • 22 years ago

In my case, I have solved my "crash upon exiting" problem with Mozilla by
replacing the one piece of Mozilla that I never touch-- the Plugins folder.  I
was wiping the profile and everything else.  I basically just copied the Plugins
folder from my Netscape 7 installation which was older, and that folder has all
the main plugins, so I'm not sure yet what was causing the problem or if a file
was corrupted.
  This also seems to have fixed a very strange problem I was having loading a
certain web page.  See bug 167757 if interested, but only one other person
seemed to be affected by that.

	Oliver Klee Reporter
	Comment 27 • 22 years ago

That looks like another bug.

I still get this crash after having removed every file from my Plugins folder
(except npnul32.dll).

	Hermann Schwab
	Comment 28 • 22 years ago

update to comment #6 and comment #7
I had some crashes on my machine at home, not at work.
can´t report talkback numbers, because I install zips in fresh folders,
so talkback data is lost.
My plugin folder is empty besides npnul32.dll,
pipelining is disabled now, and crashes are less frequent.
My machine at home is a celeron333 with 96 mb only, and a crappy partition
scheme, 8 MB grafics card SiS6326.

After some time reading a newsticker and its comments,
the machine is getting slower and slower, and I´m getting impatient.
So when I close mozilla while it´s still loading, I´m not surprised if it crashes.
If I´m closing mail, download window, mozilla and then DUN, mostly it´s ok.

Software:
Win98 german with SP1 and some patches from MS,
ZoneAlarm 2.6.88
RamIdle Standard V4.8 (beta3) disabled since comment #6, but in tray
shows usage: GDI 66% System 60% User 60% Pagefile: Total 1013, available 936 MB
1st HDD c: win98, tempfile, 144 Mb free on 4 GB
2nd HDD d: (NT4 unused), mail folders, 234 MB free on 4 GB,
e: mozilla cache, windows swap file, 930 MB free on 4 GB,
other partitions: ReiserFS, SuSe

Wastebasket disabled, so files are deleted directly.
I´m using nightlies as my default browser and default mail.

 

	Hermann Schwab
	Comment 29 • 22 years ago

TB14719056Q

Mozilla 1.3a

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a) Gecko/20021204

Celeron 333 MHz, 96 MB RAM, Win98 with 900 MB pagefile on second disk

When available RAM got down to 0 MB, loading got very slow,
so I decided to provoke a crash by ending mozilla while loading two tabs.
Ended Mozilla, then Bookmark Manager in Task Tray, then DUN.

Then crash, DocWatson came up, Talkback came up.
Wrote some data in the above talkback, DocWatson data available on request.

current data while writing this:
GDI 65% System 56% User 56%
Memory load 76%
Total physical memory 96 MB
Available physical Memory 1 MB
Total page File 976 MB
Available Page File 901 MB

	Darin Fisher Assignee
	Comment 30 • 22 years ago

*** Bug 183610 has been marked as a duplicate of this bug. ***

	Jay Davis
	Comment 31 • 22 years ago

Oliver,

You're right.  This bug is alive and well right through today's build.

	Jay Patel [:jay]
	Comment 32 • 22 years ago

Adding nsHttpTransaction::~nsHttpTransaction to summary from duped bug 183610
since Talkback is reported crashes on the Trunk under that stack signature.

	Jay Patel [:jay]
	Comment 33 • 22 years ago

Adding M121 to summary since this is a topcrash for Mozilla 1.2.1 as well.

	Michael kmd
	Comment 34 • 22 years ago

similar report on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a)
Gecko/20021209

crash when quiting mozilla.

TB14894077Y
TB14894179H
TB14896780Q
...

	Hermann Schwab
	Comment 35 • 22 years ago

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a) Gecko/20021212
TB15084877Y
TB15089345G
TB15091895G

HTTP1.1 enabled incl. Keep-Alive, Pipelining
tabs loading in background
no proxy specified, but running zonealarm

Data from DocWatson available on request ( Necko.dll, Nullptr )

	Markus Gerstel
	Comment 36 • 22 years ago

*** Bug 187232 has been marked as a duplicate of this bug. ***

	AMBROISE JEAN-MARIE
	Comment 37 • 22 years ago

Mozilla Build 2002123108 for MAC OS X still crash on quit

	Darin Fisher Assignee
	Comment 38 • 22 years ago

should be fixed by my patch for bug 176919.

	Jay Davis
	Comment 39 • 22 years ago

That's funny, this bug has been causing crashes everyday for a couple months,
and now you've fixed it with a patch from October?  I don't see that this patch
is checked in today, nevertheless.

	Matthias Versen [:Matti]
	Comment 40 • 22 years ago

the patch is a prototype as you can read and it's of course not checked in.
(needs final patch + review)

	David Baron :dbaron:
	Comment 41 • 22 years ago

Has anyone seen this crash in a build from January 18 or later?

	Darin Fisher Assignee
	Comment 42 • 22 years ago

FIXED with patch from bug 176919.

	benc
	Comment 43 • 22 years ago

VERIFIED