85578 - Crash due to constant "meta refresh" reload of page (left overnight) - Trunk [@ nsSocketTransport::OnStatus]

Status: VERIFIED FIXED

(Core :: Networking: HTTP, defect, P1)

Description

[John Morrison]

Here is the stack trace for the thread crash that occurred for me when
I left my browser running overnight pointed at home.netscape.com.
That page reloads itself every 15 minutes or so, using a 'meta
refresh' tag in the page.

I've set up a mock copy of the current home.netscape.com which reloads
every sixty seconds. I'll leave it running this evening and see if
that is a reliable way to reproduce

The crash occurred in Linux trunk 2001060612. This is the talkback
stack trace:

0x41300275
nsSocketTransport::doResolveHost()
nsSocketTransport::Process()
nsSocketTransportService::ProcessWorkQ()
nsSocketTransportService::Run()
nsThread::Main()
libnspr4.so + 0x1f6ee (0x401b76ee)
libpthread.so.0 + 0x4eca (0x401caeca) 


(See also bug 85576, for a similar but separate thread crash, while
running the page loading test).

Comment 1

[John Morrison]

-> darin

Comment 2

[John Morrison]

-> mozilla0.9.2, crash : we should probably keep this on the radar, since the 
scenario (browser left running overnight pointed to "portal" or news page) is 
not an uncommon one. I will try to see how often this happens for me.

Comment 3

[Darin Fisher]

gordon: it's DNS related, but hard to tell from the stack trace whether it has
anything to do with the DNS service or not.  it could just be the socket
transport mishandling the DNS service.

Comment 4

[John Morrison]

(I forgot to add the one wacky thing about this crash: the Talkback dialog
comes up, but the browser stays up and the UI is responsive, although you 
can't load pages).

Comment 5

[John Morrison]

I didn't crash last night. Paw -- have you run this again? (he crashed this way 
earlier as well).

Comment 6

[Paul Wyskoczka]

I didn't crash 2 nights ago but crashed last night on the Branch build.  Will
leave it up tonight running the trunk build 2001061308.

Comment 7

[benc]

www.news.com is another self-refershing site, but I have not observed anything
like this.

Comment 8

[Darin Fisher]

i suspect that my patch for bug 82241 has fixed this bug.  the problem (i think)
was that we were clearing the socket transport's mProgressSink from the UI
thread, while the same socket transport was in the middle of making a call to
its mProgressSink on socket thread.  the socket transport's monitor is not
entered in SetNotificationCallbacks (perhaps it should be).  but, at any rate,
my patch fixes this problem by ensuring that the notification callbacks (and
hence mProgressSink) get cleared only on the socket thread when the socket
transport calls nsHttpConnection::OnStopRequest.

so, with that: marking FIXED.

Comment 9

[Darin Fisher]

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

Comment 10

[Jay Patel [:jay]]

Adding topcrash keyword and  Trunk [@ nsSocketTransport::OnStatus] to summary
since Bug 86662 has been marked a dup.  The crash reported there has come back
on the MozillaTrunk as a topcrasher, so reopening.  Here is the latest info:

nsSocketTransport::OnStatus   31
			 86662 	 RESO 	 DUPL 	 [e-mail] --- 
BBID range: 35722446 - 36147325
Min/Max Seconds since last crash: 604 - 368160
Min/Max Runtime: 1343 - 368160
Crash data range: 2001-09-21 to 2001-10-01
Build ID range: 2001092105 to 2001093011

Stack Trace: 

	 nsSocketTransport::OnStatus
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsSocketTransport.cpp  line 1846]
	 nsSocketReadRequest::OnRead
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsSocketTransport.cpp  line 2799]
	 nsSocketTransport::doReadWrite
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsSocketTransport.cpp  line 1037]
 
 	Source File :
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/netwerk/base/src/nsSocketTransport.cpp
line : 1846
     (36115790)	Comments: Reading mail.
     (36114586)	Comments: Nothing.  But presumably the mail reader was checking for mail. 
Also note that during that time my VPN went down  so it's possible it died due
to not being able to contact the server?
     (36110508)	Comments: Crashed over the weekend; mail window was open and periodically
checking mail  so maybe that?  otherwise  cause unknown.
     (36074194)	Comments: Nothing.  I left my computer and come back several hours later to
find it had crashed.  But presumably it was polling for new mail during that time.
     (36056266)	Comments: It hangs when it's turn on for too long  and you're doing nothing
with your pc  (4 hours or so)
     (35904246)	URL: mainetoday.com
     (35904246)	Comments: had multiple browser windows open  mainetoday.com was the most
recently used  but was not in the foreground on my machine (I was doing stuff in
telnet/ssh windows)
     (35878003)	Comments: It was just sitting there while I was away from my desk.
     (35867386)	Comments: left moz runnig for a while and did nothing. Maybe the
biff??Access Violation in Necko.dll @ 0xC0000005

Talkback data shows this is occurring on both Linux and Windows, so changing OS
to All.

Comment 11

[Darin Fisher]

-> 0.9.5 (investigating)

Comment 12

[Darin Fisher]

i only see crash reports under windows

Comment 13

[Darin Fisher]

seems like this started showing up as of the 9/21 windows build.

Comment 14

[Darin Fisher]

my fix for bug 99562 may be suspect

Comment 15

[Darin Fisher]

ok, i've filed bug 103016 to cover this new crash.  i say new, because i believe
that the cause of the original crash was fixed, and i'd like not to muddle this
bug with details of the new crash report and the eventual solution.

marking FIXED.

Comment 16

[John Unruh]

Verified per darin's comment.