Closed Bug 669041 Opened 13 years ago Closed 13 years ago

Not Responding After Session Restore

Categories

(Firefox :: Session Restore, defect)

5 Branch
All
Other
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 651011

People

(Reporter: donb, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20100101 Firefox/5.0
Build ID: 20110615151330

Steps to reproduce:

Firefox unexpectedly closed when my netbook battery became critically low and in turn shut down Windows unattended.  I then plugged in the ac adapter and powered on my netbook.


Actual results:

I started Firefox and was presented with the "Well, this is embarrassing." screen.  I chose Start New Session and Firefox immediately displayed "Not Responding" in the title bar and hung for a good 3-5 minutes.  After that, Firefox was running but very sluggishly.  

I exited Firefox and then ran SpeedyFox.  After starting Firefox, things were back to normal.


Expected results:

Firefox should not have hung for 3-5 minutes, IMHO.
No it shouldn't have. I haven't seen that myself, but I don't hit this case too often and I can't think of a good reason why this would happen. If you can reliably make this happen, I would be interested to hear more.
It has happened before but only upon an unexpected close of Firefox.  Since my netbook can go 8.5 hours in between charges, I run it on battery often.  I can try killing the task but I read somewhere on the internet that someone else with a similar issue was not able to reproduce the problem by killing Firefox via the task manager.
I intentionally let the battery get critically low and my netbook abruptly shut down while Firefox was running with four open tabs.  I did not get the session restore screen but the four tabs took like a minute to restore.  I shall continue to try to induce it again.

I strongly believe this problem has to do with a corrupted database file.  The reason I state this is because the browser hung similar to when I recently had a corrupted places.sqlite file.  Just saying.
Is there a places.sqlite.corrupt File inside your Profile Directory?

Else than this I believe this is due to Invalidation of the (then corrupt) Cache Directory after the non-normal Firefox Abortion what indeed takes "Ages" since Firefox 4 to rebuild/fix.
There is no places.sqlite.corrupt file.

Whatever Firefox is doing does seem to be taking ages.  

But why would it be [not responding] instead of being busy?
I allowed my netbook battery to get critically again and shut Windows down while Firefox was still running, but it did not repeat the problem.  I guess it will happen (again) with the luck of the draw I suppose.  

If it happens again, then what?  Do I need to look for something while it is hung?
I got it to reproduce.  

It seems to have to do with the cache.  I remember last time my cache was about 300MB so I allowed it to reach 251MB, and then I cleared the cache via Options > Advanced.  FF then became non-responsive for a good three minutes or so.  I then started Process Monitor and could see that FF was accessing a ton of cache files the entire time. Process Monitor revealed the following results while FF was processing cache directories:


1) NO MORE FILES
2) SHARING VIOLATION
3) NAME NOT FOUND
4) DELETE PENDING

BTW, I am using an ASUS 1201HAB Netbook running WinXP.  I remember that I used to keep the cache limited to 50MB but when FF5.0 released, I allowed it to use automatic cache management instead.
Sounds like this isn't related to session restore at all. This has to do with cache invalidation, which matches up with what you're seeing from process monitor.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.