Author
Topic: Firefox 3 Bug (Read 3642 times)

I am having issues with firefox 3. I currently have the bug posted at Mozilla's Bug Tracker. The issue is this. I have just finished a complete reinstall, deleted profile with no extensions and a firefox reinstall, in an attempt to fix this issue. It appears that firefox is failing to load images on a refresh of a page. This occurs after many pages are refreshed using F5 or the reload button. As such, the pages appear broken and often contain just text with a very broken appearance. Has anyone experienced this? Click the link above for some images of what I am seeing.

I've had that image of a forum like DC and other forums happen on my computer after cleaning with ATF-Cleaner. And also at random times, but not often. Had the same issue with the previous version of FF also.

I have a similar problem when trying to view pages on my local server through my external IP address - but using the internal IP works just fine, and people from the outside can view through the external IP just fine as well. This also happens with IE6 though, so the problem probably isn't related, and might be due to my httpd setup.

Yes I know, I sent an email to the developers and have yet to receive a reply. We shall see. It seems that setting that option fixes the issue but why should it have to be enabled when it didnt have to be previously. Am I required to clear my cache on a daily basis (with each new list update) in order to fix the issue? I should hope not.

I haven't had a chance to see if it works here, I have uninstalled AM and have been really happy with the apparent increase in browser performance. It is such a difficult program to adjust, it seems to block lots of obscure pages that many sites call, and it was causing me more difficulty than the ads did, I've gone back to ABP, at least when you allow a site, it allows it all. It (AM) was also blocking something within the site of University I am going to, and that was pretty much the end of it for me. And the cache clearing, well I would clear the cache and sometimes it would work for a while sometimes not.

Yeah, that has been my experience. However, Jeff (AM List maintainer) has pawned this off as likely being a firefox bug since he is having no signs of this, as is the norm with most bugs I and others seem to report, although the bug completely disappears after changing an option in ad muncher or exiting it completely. This seems to be the norm from my experience.

I just fail to see how the bug could be firefox's fault when ad muncher's options (or exiting) fixes the issue. Can anyone explain this to me?

Mouser or any developer for that matter, from your experience, does this explanation make sense? In my limited development experience (limited to programs suiting my own particular needs) this doesnt make sense. If my program, when terminated, resolves an issue, or enabling an option in my developed program fixes a problem in another, how can this bug not be my programs fault?