398695 - Minefield can't load pages after you switch your network interface

Status: RESOLVED INVALID

(Firefox :: General, defect, P4)

Description

[Eric Appleman]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a9pre) Gecko/2007100418 Minefield/3.0a9pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a9pre) Gecko/2007100418 Minefield/3.0a9pre

Minefield can't load pages after you switch your network interface until you kill the process and restart the browser.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Eric Appleman]

*forgot the steps to produce.

1. Open Minefield while connected to a wireless or wired network.
2. Browse a bit.
3. Switch your network interface from wireless to wired or wired to wireless.
4. Try to browse, you can't.

You have to kill the process in the task manager and restart Minefield before you can browse again.

Comment 2

[Mike Beltzner [:beltzner, not reading bugmail]]

Lucy has been able to reproduce this, so confirming and adding qawanted.

Comment 3

[Eric Appleman]

Mike, what's your browser string?

Comment 4

[Majken Connor [:Kensie]]

I was hitting this really randomly, and mostly at the MV office.  I think I still have a log somewhere from when I was trying to troubleshoot it.  Biesi's guess was that putting it into offline mode and then back to online mode would work.  I've been using alpha 7 for a while and not hitting it, will switch back to nightlies and see if it comes up again.

Eric, did this start for you at any point? Would you be able to see if it does or doesn't happen in alpha 7 for you?

Comment 5

[Christian :Biesinger (don't email me, ping me on IRC)]

OK, so the log from Majken shows that the last thing that happens on the socket transport thread is a PR_Poll without a timeout. I would therefore suspect that this is similar to bug 213637, except that the poll never returns instead of returning immediately.

However, the code in question is basically the same on branch...

Comment 6

[Eric Appleman]

majken, at least a week or two ago...

Comment 7

[Michaël Arnauts]

Easy to reproduce: 

* Connect to a wireless network
* Browse a bit
* Put computer/laptop in standby
* Wait a bit
* Wake up the computer/laptop
* Try to browse

It happens every time, simply closing firefox isn't enough, since the next time I start a process, it gives a message that a non-responding firefox is still running. I have to open taskmanager and kill it.

Comment 8

[Majken Connor [:Kensie]]

michael - would you be able to make a log of it? 

http://www.mozilla.org/projects/netlib/http/http-debugging.html

It probably won't attach here, but if you get one we can email it/put it up somewhere else and biesi can compare it to mine, see if it has any clues.

Comment 9

[Michaël Arnauts]

http://www.michaeleninneke.be/storage/log.txt

* I first visited tweakers.net
* then i want into standby
* after resuming, i tried searching with the integrated searchfield, and clicked a few bookmarks

I noticed however, that there is a connection made, but the screen doesn't change, and the statusbar just tells "Stopped".

Comment 10

[Mike Connor [:mconnor]]

more fun with network stacks for Jim!

Comment 11

[Mike Connor [:mconnor]]

Not blocking on this bug for final ship. Would take a safe enough patch if one comes through.

Comment 12

[Jim Mathies [:jimm]]

I was just testing this with Beta 4 and a laptop running Vista on a wireless network. I tried to scenarios, a full hibernation/resume, and a sleep/wake. In both cases I was not able to reproduce. Can anyone else confirm what I'm seeing currently?

Steps -
1) boot, connect to a wireless network
2) open firefox beta 4, search for 'firefox' using the search bar
3) start -> hibernate
4) wait for the computer to finish, then power back up and wait for a wireless network connection to be established
5) search for 'twitter' in the search bar

result: the search results come up for 'twitter'

or

1) boot, connect to a wireless network
2) open firefox beta 4, search for 'firefox' using the search bar
3) close the lib on the laptop and wait for the computer to fully sleep
4) open the lid and wait for a wireless network connection to be established
5) search for 'twitter' in the search bar

result: the search results come up for 'twitter'

Comment 13

[Jim Mathies [:jimm]]

marking as invalid, if anyone is still experiencing this, please re-open and I'll take another look.