Closed Bug 325188 Opened 19 years ago Closed 17 years ago

task hang/unresponsive after system idle

Categories

(Firefox :: General, defect)

1.5.0.x Branch
PowerPC
macOS
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: darrenrobinson, Unassigned)

Details

(Keywords: hang, Whiteboard: CLOSEME 07/14)

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

firefox 1.5.0.1 hung when trying to use after machine had been idle, windows and tabs respond, can be selected and toggled, minimised, maximised, and most can be closed (see my other bug for details of the menu functions and the final window). web page links, however, do not respond in any way, nor does the back, forward and reload buttons. data cannot be entered into the address bar, nor can new windows/tabs be opened, but curiously most can be closed. scrol bars and menus continue to function, except for links (history, bookmarks, etc). unable to use and unable to exit cleanly (task only exited with a forced-quit)

Reproducible: Couldn't Reproduce

Steps to Reproduce:
Couldnt reproduce as had no way of knowing how this occured, firefox had been running fine, with no obvious signs of trouble before machine was idle. machine had been idle and asleep several times with no ill effects.




Bug #325187 may be related to this as occured at the same time, although Bug #325187 has occured previously in unconnected issues.
Version: unspecified → 1.5.0.x Branch
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Keywords: hang
Whiteboard: CLOSEME 07/14
Have not been able to reproduce in OS X 10.2.6 (never installed update to 10.2.8 after reinstall) and after upgraded to Firefox 2. Issue may have been resolved. However, as this bug was never assigned to anyone and no comments were added one might assume that nothing was done to actually fix the problem, so may resurface.

As i am unable to reproduce the error i will close the report as requested as WorksForMe.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.