Created attachment 8489600 [details] favicon_browsers.png User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0 Build ID: 20140911151253 Steps to reproduce: Since new cache system was released in Nighly brand and now in Firefox release 32, the sites favicon are very intermittent on my system. Sometimes it loads, other not. Clearing the cache (ctrl+alt+del everything) or manually deleting the cache2 folder on profile, doesn't fix the issue. I tried to argue about this issue when new cache were added to Nighly weeks ago, in Moz IRC and MozillaZine, but none had the problem as me. I have no specific steps to reproduce the problem, I just run several random websites. In attached screenshot is a comparison of www.imgur.com on several browsers (IE, Firefox 33, Chrome, Opera, Mathon). I have no extra security software or other thing to manipulate my internet traffic. When testing release/beta/nighly I always do at a fresh profile. Not sure if someone else will be able to reproduce the problem, what I can confirm for sure, is that the bug is real. How can I help you guys to confirm the issue? Thank you!
Do you mean bug 1036939 ?
Maybe, from the sites suggested in that bug here is the result: www.anandtech.com - fine no issue after few times. www.techspot.com - confirmed the issue in all attempts. www.heise.de - confirmed the issue in all attempts. www.tomshardware.com - confirmed the issue in all attempts. Don't see nothing related to bookmarks, though. Based on my report, Bug 1066726 seems to be the correct one. If you or someone else have the same conclusion, please mark this bug as duplicated. Thanks.
^ Oppsie, correct report in test is: www.anandtech.com - confirmed the issue in all attempts. www.techspot.com - confirmed the issue in all attempts. www.heise.de - confirmed the issue in all attempts. www.tomshardware.com - fine no issue after few times.
I think you may experience bug 1066726.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1066726
You need to log in before you can comment on or make changes to this bug.