User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:220.127.116.11) Gecko/20091106 Shiretoko/3.5.5 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:18.104.22.168) Gecko/20091106 Shiretoko/3.5.5 Readmandarin.com uses both GIF images and GoogleAds, which seem to interfere with FF. Reproducible: Always Steps to Reproduce: 1.Go to www.readmandarin.com/learn.htm 2.Guess a charachter and its pronunciation 3.Click on "Continue" Actual Results: Firefox crashes. Expected Results: Display new character page, that is: - new GIF image - new GoogleAd - new text hyperlinks
Please provide a crash ID from about:crashes. https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report
Well, I firstly tried safemode deactivating my addons, which are the following: - AdBlock Plus (ads allowed on readmandarin.com) - Download Manager Tweak - Foxy Proxy (not active) It worked like a charm. After reactivating the addons, it continues (for now) to work as expected. Conclusion: strange as it may seem (yesterday always crashing and today never), the bug is gone. I close the report. Thanks.
I have some (bad) news. Today it was working, but only because the safe-mode disabled all plugins. Now I tested it thoroughly and the fault is of the Adobe Shockwave Flash plugin 10.0.32.18. That is: - without the plugin, everything is working fine; - with the plugin, firefox crashes. Should I try to get a backtrace or should I report it to Adobe or both?
Well, here it disabled all of it, but this is not the point. I run FF inside gdb and got the following message: Program received signal SIGSEGV, Segmentation fault. 0x00007ffff28104f0 in g_type_check_instance_cast () from /usr/lib/libgobject-2.0.so.0 Can this help you?
I'm closing a lot of bugs which are filed as Adobe Flash bugs which are either irrelevant, not actionable, or not serious enough to track in the Mozilla bug tracker. For the most part, Flash bugs should be filed in Adobe bugbase, and we'll only track a few highly-critical issues in the Mozilla tracker.
Version and milestone values are being reset to defaults as part of product refactoring.