Closed Bug 243046 Opened 21 years ago Closed 21 years ago

Display freeze when trying to render big image at slow network speed

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

()

VERIFIED FIXED

People

(Reporter: bugzilla, Assigned: bugzilla)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040403 Firefox/0.8 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040403 Firefox/0.8 Browse a while at slow speeds (dialup) and view fairly big images (few hundred kilos) on the web. At some point the display will freeze. I can still use the magical SysRq and kill X Windows and reboot, so I guess the keys still work, but the display is frozen. I've noticed it's about the size of the images (as in kilos) not the dimensions (as in pixels). It has to be images loaded at low speeds, it won't happen with a local webserver, local intranet or local harddisk which display them instantly. It also won't happen in a freshly started browser, it takes some time of constantly viewing such images to produce the freeze. It doesn't seem to be affected by themes, extensions and so on. It does NOT happen with the same Firefox version on Windows. It happens with various builds of Firefox on Linux, from various sources. Reproducible: Always Steps to Reproduce: 1. browse for big images (hundred of kilos) at slow network speeds. 2. at some point you get a display freeze. Actual Results: Complete display freeze. Expected Results: Not freeze.
This is not solely dependent on a slow network connection, nor on the size of one image. The same problem occurs when a page with several megabytes of images are loaded (i.e. listing/gallery of full size images of 100KB+ each). The entire browser freezes up. It happens on local web pages as well to an extent, though the effects aren't as severe due to the local connection. I've never noticed this problem in regular Mozilla--only FireFox.
Is this still here in 0.9.1?
Nope, all well now. I have used 0.9.1 for a while now and it didn't happen once.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.