Closed Bug 652118 Opened 14 years ago Closed 14 years ago

firefox.exe won't close after XP has hibernated

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: Peter6, Unassigned)

Details

(Keywords: regression)

Mozilla/5.0 (Windows NT 5.1; rv:6.0a1) Gecko/20110422 Firefox/6.0a1 ID:20110422030558 This has happened since roughly the creation of 6.0a1 repro: open FF browse a bit or not check for incremental update or not apply update or close firefox result: the firefox window closes, but firefox.exe stays active happens with daily profile even in -safe-mode with everything but bookmarks reset/disabled STR, I have not been able to figure it out in over a week. The only extension installed/in use is NTT.
ps, firefox.exe hangs about 50% of the times FF is closed. looks like some sort of race condition
Any external Influence like AV/Firewall App possible?
Can you get a stack when it's hung?
(In reply to comment #2) > Any external Influence like AV/Firewall App possible? No (In reply to comment #3) > Can you get a stack when it's hung? I wouldn't know how to get that. FF doesn't come with sessionrestore after i restart after i killed the process
Confirmed Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:6.0a1) Gecko/20110422 Firefox/6.0a1 It hangs randomly. Mostly on scrolling with scrollbar. It's probably related to plugin-container.exe, because when I kill it it stops hanging. I also see that plugin-container.exe is running even if there's no flash or java.
btw. Why is there no solution to all those firefox.exe stays active problem ? It is a big problem for a users. Is it possible to self-kill Firefox process if it is not terminated withing for example 10 seconds ?
(In reply to comment #5) > Confirmed > Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:6.0a1) Gecko/20110422 Firefox/6.0a1 > > It hangs randomly. Mostly on scrolling with scrollbar. > It's probably related to plugin-container.exe, because when I kill it it stops > hanging. I also see that plugin-container.exe is running even if there's no > flash or java. This bug is not about hanging while you browse. All plugins are disabled in -safe-mode so they don't play a role.
(In reply to comment #7) > All plugins are disabled in -safe-mode so they don't play a role. You would think they are, but that's still not the Case - see Bug 342333.
(In reply to comment #7) > This bug is not about hanging while you browse. > All plugins are disabled in -safe-mode so they don't play a role. I know, but it occurs when you're using Firefox before closing, when plugin-container.exe is also running in background. This probably triggers this bug, because when I kill manually this process and next close Firefox, it shutdown properly. This in someway can be also related to bug #651010. I will try find regression range AFAP.
I'm going to disable all plugins and see how it goes the next few days.
I manually disabled flash and restarted, then went for thw incremental update. Result: unfortunately firefox.exe still doesn't close about 50% of the time.
possible STR use FF... close FF let Windows XP go into hibernation wake up windows start FF check for updates... at the end FF closes but firefox.exe stays active kill firefox.exe start FF often FF doesn't fully load and freezes kill Firefox.exe start FF ... and it finally works
It still reproducible with latest builds ? Because for me it not happen anymore.
with STR of comment 12 it still happened last night. I closed FF after the download It wouldn't restart. killed firefox.exe started Firefox message the update couldn't be applied and needed the full download Firefox locked up with partial chrome loaded killed firefox.exe again Started Firefox again the partial update was applied and Firefox started and was functional
Summary: firefox.exe won't close → firefox.exe won't close after XP has hibernated
You could try Firefox with clean installation. For me it fixes also hanging problem when bug #648935 was fixed and it's still occurred in my case.
this appears to have been fixed a few days ago. Haven't been able to repro for a few days now. Leaving open for another few days before resolving. as far as i can tell this was een XPCOM bug fixing it, but the bugtitle wasn't as obvious. It was the discription at checkin that made me think it could be the one i was waiting for. Can't find it anymore thuogh.
nope, still happens.
This hasn't happened in over 2 weeks now. Resolving INCOMPLETE since it's too difficult to figure out what caused and fixed it
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.