Closed Bug 433305 Opened 17 years ago Closed 17 years ago

UI non responsive and often hangs (grey) with bloglines.com

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 421482

People

(Reporter: steve, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9pre) Gecko/2008051117 Minefield/3.0pre Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9pre) Gecko/2008051117 Minefield/3.0pre For several months I have been getting daily but random problems with nightlies and bloglines.com. I can't get an exactly reproducible scenario but it is consistently a problem. The UI often doesn't respond and usually greys out completely and only 'force quit' is available. Usually if you wait a very long time it becomes responsive again but keeps going unusable. See notes below Reproducible: Always Steps to Reproduce: 1. Can't tie it down, I just keep open my bloglines feeds open and restart with remembered tabs open. 2. See more info below 3. Actual Results: UI not responsive or greys out for long periods. Expected Results: no problems with UI responsiveness So I have tried a clean profile with no add-ons and only bloglines and seems to be a problem still. Perhaps worse with gmail also open which is my usual state (perhaps 2 Ajax tabs). * Inet and web access are always fine. * Disc always seems to be thrashing and continues for sometime after exiting FF (so it sees most likely that the problem is being IO bound) * Have problem on 2 machines (desktop and laptop) with Gutsy and Hardy Ubuntu. * Have accessibility (AT-SPI) on. * my feeds can be seen at http://www.bloglines.com/public/stevelee but that page never causes a problem, only the monitoring 'myblogs' page and seems to be when feeds have items to be viewed. Sorry to be so vague but this is a real painful issue that I have not yet managed to pin down.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.