Hi,

You can consider the Reset Firefox feature via Help (Alt + H) > Troubleshooting Information. If the problem persists, you can also try to deselect Use hardware acceleration when available in Preferences > Advanced > General. The Ubuntu forum would also be helpful.

Options

If you have submitted crash reports then please post the IDs of one or more crash reports (bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

• You can find the IDs of the submitted crash reports on the about:crashes page.
• You can open the about:crashes page via the location bar, like you open a website.

See:

• http://kb.mozillazine.org/Mozilla_Crash_Reporter
• https://support.mozilla.org/kb/Mozilla+Crash+Reporter

If you can't open Firefox then see:

• http://kb.mozillazine.org/Mozilla_Crash_Reporter#Location_of_crash_reports
• http://kb.mozillazine.org/Mozilla_Crash_Reporter#Viewing_crash_reports

• https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report

No crash reports since June, but it did crash yesterday without automatically offering to submit a report. When it hangs sometimes (since the upgrade from 3.x) I've killed the whole session and rebooted. I don't believe any crash reports were generated from those. If it crashes and issues a report before I get this reloading thing figured out, I'll post the number.

Thanks. I probably will try the reset feature even though a return to default settings will cause crashes and headaches until I find the right values again. We'll see.

It currently isn't using hardware acceleration.

Well, I tried the reset option. Things seem zippy now with the default options, however, it still draws images on my tumblr dashboard twice. Zippy, but nevertheless it takes nearly twice as long as it should, and besides it's kind of annoying. This seems to happen particularly with images that are read from the cache. Possibly it's only happening with progressive jpgs, which tumblr uses on its dashboard, but I'll need to test that.

Also, if you are using a proxy, you can try to temporarily choose No proxy in Preferences > Advanced > Network > Settings to see if it helps. Another thing you could try is to open the Web Console and then load/reload/hard reload the page. Clicking on the GET links related to problematic images and comparing it with the normal images would hopefully provide more info, if it is network/header related. You can also try starting Firefox via the terminal, the terminal may have helpful messages related to the jpeg library. If it is the Ubuntu Firefox, the Ubuntu forum may also have helpful information, especially new developments related to the new release.

Now I realize that it isn't just cached images. All images on my tumblr dashboard are doing this right now, and I've noticed it on other sites but haven't been testing them.

The web console shows that the downloads look okay. The redrawing happens after the images are downloaded. There are many css errors registered prior to the initial painting of images. Those don't seem to affect the initial display of the page and its images which were properly downloaded. It is only after this process is complete that the redrawing begins.

I'll try starting from the console. I'm also looking at MOZ_DISABLE_IMAGE_OPTIMIZE=1 which isn't well documented, in my opinion. If that makes a difference I'll note it here.