20419 - [dogfood] Clicking on links or typing a new URL doesn't load page

Status: VERIFIED WORKSFORME

(Core :: Networking, defect, P3)

Description

[chriss]

Build 1999113012
OS: Win98

Steps to reproduce:
1. Launch Seamonkey
2. Click on a link or bookmark - notice that page loads properly
3. Wait a minute or 2
4. Attempt to click on a link or type a URL and hit return
5. Notice that the status bar says the page has loaded (often quickly in less
than 1 sec) but no page appears.

I believe this bug is related to:
http://bugzilla.mozilla.org/show_bug.cgi?id=20416

Here's why: as soon as the ability to click on links breaks, I also cannot
make TCP connections in 4.7. Perhaps both these bugs have to do with a memory
leak?

Comment 1

[leger]

Link problem looks like a dup of:
http://bugzilla.mozilla.org/show_bug.cgi?id=19510

URL problem looks like:
http://bugzilla.mozilla.org/show_bug.cgi?id=15150
a dup of http://bugzilla.mozilla.org/show_bug.cgi?id=20172

chriss, these are 2 seperate bugs.  Both I believe known.  I will continue ith
investigation, but next time...two bugs please :-)

Comment 2

[chriss]

I don't think this bug is related at all to:
http://bugzilla.mozilla.org/show_bug.cgi?id=15150

Also I don't think this should be 2 separate bugs, since both links and typing
URLs work until some point in time and then both fail simultaneously.

What I am seeing is a symptom of some underlying bug, perhaps a memory leak.

Comment 3

[chriss]

Adding [e-mail] and [e-mail] to cc: list per conversation
with warren.

Comment 4

[leger]

Putting on PDT+ radar.

Comment 5

[daver]

Jan, can we reproduce this or mark works for me.

Comment 6

[chriss]

As of the 199120808 build, this problem has gone away for me. Warren - did you
check in a fix or do something special to my machine?

Comment 7

[Warren Harris]

No, we didn't check anything in for this (that I know of). [twlight zone theme]
We were suspecting the SSL i/o layering or perhaps the cartman process though.

Comment 8

[Doug Turner (:dougt)]

I have not change anything with regard to ssl io layering in a while.  I can
reproduce this intermittenly when running/debugging in xpcshell.  This does not
touch ssl/https.  I am not sure exactly what the steps to reproduce are.

Comment 9

[Warren Harris]

What is xpcshell? Are you saying other programs get the same winsock breakage?

Rick and I had determined that we were getting an error back from nspr from
connect (as I recall). Rick can confirm.

Comment 10

[Doug Turner (:dougt)]

xpcshell is some test application that allows you to load pieces of JS code
and call them as functions from a command line (really cool).  I have been
using it to test nsIFile.  On a few occurances, I caused tcp to lock up.  I
thought that this was some problem regarding a new dsl modem, but the symtoms
in this bug report are similar to what I experienced.  The javascript that I
had loaded should not go through connect() and in fact is mostly string
parsing.  I have tried since to reproduce it without any luck.

Comment 11

[Warren Harris]

Moving what's not done for M12 to M13.

Comment 12

[James Everingham]

Removing PDT+ to be reconsidered, this now works on Saito's machine as well.

Comment 13

[leger]

Putting on the PDT- radar.  Only on chriss machine.

Comment 14

[leger]

Bulk move of all Networking-Core (to be deleted component) bugs to new
Networking component.

Comment 15

[Warren Harris]

Chris: You said this problem went away for you, right? If so, can we mark this
WORKSFORME now? I'm not sure what else to do to try and track it down.

Comment 16

[Warren Harris]

We haven't seen this problem for weeks.

Comment 17

[Tom Everingham]

worksforme too - marking verified - 2000012520