Closed Bug 802390 Opened 7 years ago Closed 7 years ago
alt text is shown simultaneously with images
22.72 KB, image/png
2.76 KB, image/png
20.82 KB, image/png
5.17 KB, patch
|Details | Diff | Splinter Review|
Just came back to my browser and my inactive tabs ended up with alt-text all over some of the images. Attached is a screenshot on amazon. This state persists until ctrl-shift-r. I think a simple reload did not help.
I hit this as well, a few days ago, when switching to a facebook tab. The image in this screenshot is supposed to be just one tongue-sticking-out smiley-face, but it ended up (a) showing the alt text, and (b) changing the image bounds to be as large as the alt text. (making it show additional image-sprite content -- a whole other smiley-face)
(FWIW, my screenshot was taken on Sunday Oct 14, using an up-to-date Linux 64-bit nightly)
OS: Windows 7 → All
Version: unspecified → Trunk
Mine is from today's nightly
(In reply to Taras Glek (:taras) from comment #3) > Mine is from today's nightly Today's nightly is still suffering, but i have STR now. open up gmail, plus an image-heavy tab such as flickriver.com...scroll around in flickriver.com enough to evict gmail image cache entries, then switch to gmail tab and watch alt-text appear dom elements. Note the alt-text appears on all new image-elements inserted into the dom(even if they use the same images as are already displayed elsewhere), old ones are fine and reloading the page makes all images show alt-text. ctrl-shift-r resets the cache and alt-text disappears.
(In reply to Taras Glek (:taras) from comment #4) > (In reply to Taras Glek (:taras) from comment #3) > > Mine is from today's nightly > > Today's nightly is still suffering, but i have STR now. open up gmail, plus > an image-heavy tab such as flickriver.com...scroll around in flickriver.com > enough to evict gmail image cache entries, then switch to gmail tab and > watch alt-text appear dom elements. Note the alt-text appears on all new > image-elements inserted into the dom(even if they use the same images as are > already displayed elsewhere), old ones are fine and reloading the page makes > all images show alt-text. ctrl-shift-r resets the cache and alt-text > disappears. For a while I could reproduce this with yesterday's build, but then the issue ceased to be reproducable so my STR is wrong. I talked to dholbert and looks like the only sites that exhibit this issue are spdy sites: facebook, amazon, twitter, gmail.
Component: Layout → Networking
(In reply to Taras Glek (:taras) from comment #5) > > For a while I could reproduce this with yesterday's build, but then the > issue ceased to be reproducable so my STR is wrong. I talked to dholbert and > looks like the only sites that exhibit this issue are spdy sites: facebook, > amazon, twitter, gmail. fwiw I don't believe amazon.com uses any sdpy and facebook uses very little at this point in time in production (though they are testing it). might be a cache issue.
Why is this actually in the networking component? It seems more to be some layout or rendering issue...
(In reply to Honza Bambas (:mayhemer) from comment #7) > Why is this actually in the networking component? It seems more to be some > layout or rendering issue... Feels like a networking issue because resetting the cache fixes it but a simple reload doesn't.
Summary: alt text is shown simulataniously with images → alt text is shown simultaneously with images
Michal - Taras thinks this might have something to do with the cache state for images. He's guessing that maybe the cache is reporting that images are incomplete. Assigning to you to investigate, we can come up with a new plan if you determine that this isn't a cache bug.
Assignee: nobody → michal.novotny
Just hit something that looks like this bug on the https://hire.jobvite.com/ login page, after having a few jobvite tabs open for a few hours (long enough to make my Jobvite session time out and redirect me to the login page) In this case, it showed the broken-image icon instead of alt text, but I suspect it's the same issue. (it's just that we don't have alt-text to show for the images in this case. So the underlying issue that makes us show the alt-text on the other sites ends up making us show a broken-image icon at Jobvite.)
This bug seems very similar (possibly the same) as bug 804000, for which the regressing changeset is known.
I'm currently hitting this with the green/red availability indicator icons in the contact list on the left side of my Gmail tab. From inspecting those elements, they're effectively <img src="https://mail.google.com/mail/u/0/images/cleardot.gif" alt"some text" style="background: https://ssl.gstatic.com/ui/v1/icons/mail/icons2.png"> where that background image is a sheet of sprites. If I try to view either cleardot.gif or icons2.png directly, I get an error page: > The image [url] cannot be displayed because it displays errors.
Daniel set a watchpoint on a particular image going bad, and using that we figured out when this happens. It turns out to be the case that we don't handle shutting down a decoder that hasn't had a chance to do any work yet. The intention of this code is to let us display animated images that go bad after we've had at least one good frame. Unfortunately it didn't actually test whether things went bad, and just used "I have at least one frame" as a proxy for that. Making things explicit should make this bug go away.
Assignee: michal.novotny → joe
Attachment #682526 - Flags: review?(jmuizelaar)
now with less patch
jeff reviewed this over my shoulder
Unfortunately, this caused mochitest browser-chrome failures on all platforms. Backed out. https://hg.mozilla.org/integration/mozilla-inbound/rev/84384977f87b https://tbpl.mozilla.org/php/getParsedLog.php?id=17114895&tree=Mozilla-Inbound TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/webconsole/test/browser_webconsole_bug_595934_message_categories.js | Timed out while waiting for: test #15 successful finish Stack trace: JS frame :: chrome://mochitests/content/browser/browser/devtools/webconsole/test/head.js :: wait :: line 294 JS frame :: chrome://mochitests/content/browser/browser/devtools/webconsole/test/head.js :: <TOP_LEVEL> :: line 304 native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
Most of our time was spent trying to reverse-engineer what type of decode shutdown we were doing, but that broke things for various reasons. Instead of reverse-engineering it, let's just expose it directly. Try run: https://tbpl.mozilla.org/?tree=Try&rev=73e4455ba8f4
Attachment #685310 - Flags: review?(jmuizelaar) → review+
https://hg.mozilla.org/integration/mozilla-inbound/rev/305129d04cd1 I'll ask for aurora uplift once this has proven itself.
Target Milestone: --- → mozilla20
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Triage drive-by: not asking for uplift yet since comment 20 suggests Joe will do the right thing soon...
Comment on attachment 685310 [details] [diff] [review] expose the shutdown intent to Decoder::Finish() [Approval Request Comment] Bug caused by (feature/regressing bug #): bug 792199 User impact if declined: Images will occasionally fail to decode on quick tab switches. Testing completed (on m-c, etc.): On m-c for a week Risk to taking this patch (and alternatives if risky): Probably not too risky. Could expose other bugs, but probably won't. String or UUID changes made by this patch: none
Attachment #685310 - Flags: approval-mozilla-aurora?
Comment on attachment 685310 [details] [diff] [review] expose the shutdown intent to Decoder::Finish() Given where we are in the cycle, and the fact that we've got an extra week of Aurora here, approving for uplift. This is manageable risk.
Attachment #685310 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
https://hg.mozilla.org/releases/mozilla-aurora/rev/568804ee53fd The offending patch was actually disabled on 19; should we set the status-firefox19 flag to disabled?
Er, s/19/18. And ignore me, I can't read. Gah.
Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20100101 Firefox/20.0 Did not encountered any issues using Firefox 20.0 (buildID: 20130326150557).
You need to log in before you can comment on or make changes to this bug.