User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20170302120751 Steps to reproduce: This happens daily when I use Firefox, and I have experienced it at least since Firefox 51 (it may also have happened in 50 too, I am not sure). I think it happens more frequently if I have TweetDeck open, which displays a lot of images. I am using macOS Sierra on a 2013 13" MacBook Air with 4GiB of RAM. Actual results: After some time using it, random images will begin to disappear. Background images (e.g. Twitter UI elements like the “like” button heart or retweet button, or the Reddit upvote and downvote buttons) disappear. Other images show up as grey-filled rectangles (Firefox 51) or black-filled rectangles (Firefox 52). Refreshing a tab typically briefly fixes the issue for its images, unless the tab is for an image itself (rather than a page containing an image), in which case closing the tab and reopening it is needed to fix it. For both of these brief fix approaches, it is only temporary, and the disappearing images will quickly return. Expected results: Images should not randomly disappear, like they didn't in previous Firefox versions.
Sounds like what happens when we fail graphics allocations or have context loss.
Sound familiar to anyone?
If there are a lot of animated images, and this problem goes away in nightly, this is probably bug 686905. ajf - can you try this in nightly and let us know if the problem is gone?
(In reply to Milan Sreckovic [:milan] from comment #3) > If there are a lot of animated images, and this problem goes away in > nightly, this is probably bug 686905. > > ajf - can you try this in nightly and let us know if the problem is gone? I downloaded Nightly 55.0a1 (2017-05-03) (64-bit) and after using it a little while, no, the black images are unfortunately still a feature of my Firefox experience. On the plus side though, Nightly lacks the inexplicable runaway swap use I've seen for the last week, and it finally gets me e10s, so there's that.
I'm currently using Firefox 54 and I can't say I've experienced this in a while. Either 54 or maybe 53 must have fixed the issue. But also, recent versions consume vastly more memory, so that's probably related. I guess this bug is closed then.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.