Open Bug 889802 Opened 8 years ago Updated 7 years ago
Firefox closes when loading Banana
Bench and Unreal demos
Mozilla/5.0 (X11; Linux i686; rv:25.0) Gecko/20130702 Firefox/25.0 Build ID: 20130702110300 Steps to reproduce: 1. Launch Firefox and load the following demos: http://www.unrealengine.com/html5 http://kripken.github.com/misc-js-benchmarks/banana/benchmark.html Expected results: The demos are properly loaded. Actual results: Firefox closes with this message in the terminal: "Aborted (core dumped)" Notes: I could reproduce the issue on Ubuntu 13.04 on a PC running with ATI Radeon HD 5450 video card and on Ubuntu 13.04 on a PC running with AMD Radeon HD 7700 Series. I could not reproduce the issue on Ubuntu 13.04 on a PC running with Intel HD 4000. I could not reproduce the issue on Mac OS X 10.8.3 on a PC running with AMD Radeon HD 6630 M 256 video card. On Windows 7 running on a PC with ATI Radeon HD 5450 video card - the unrealengine demo is not loaded, the BananaBench is loaded but playing jerky - Firefox does not close itself. Graphics for the PC running with ATI Radeon HD 5450: Adapter Description ATI Technologies Inc. -- ATI Radeon HD 5450 Device ID ATI Radeon HD 5450 Driver Version 4.2.12002 Compatibility Profile Context 9.012 GPU Accelerated Windows 0/1 Basic Vendor ID ATI Technologies Inc. WebGL Renderer ATI Technologies Inc. -- ATI Radeon HD 5450 windowLayerManagerRemote false AzureCanvasBackend cairo AzureContentBackend none AzureFallbackCanvasBackend none I'm currently working on a regression range and I'll post the results as soon as I get them.
Regression range: Last good nightly: 2013-03-16 First bad nightly: 2013-03-17 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=8f5b1f9f5804&tochange=0b052daa913c
The commit in the regression range that springs out is this: b3d85b68449d Luke Wagner — Bug 840282 - OdinMonkey (sr=dmandelin) But if that regression range is correct, the crash is FF22+ 0.o
Currently we tend to OOM pretty easily on 32-bit systems (this looks like a 32-bit system) and the browser tends to crash on OOM. Do you have the crash backtrace? We have fixes coming which will reduce the memory spikes.
Sometimes, when Firefox closes I get a crash report: https://crash-stats.mozilla.com/report/index/7cdfcf65-71c8-4e75-b209-841b72130708 (In reply to Luke Wagner [:luke] (on PTO until July 15th) from comment #3) > Currently we tend to OOM pretty easily on 32-bit systems (this looks like a > 32-bit system) and the browser tends to crash on OOM. Do you have the crash > backtrace? We have fixes coming which will reduce the memory spikes. I tried to get a crash backtrace using the steps from https://wiki.ubuntu.com/MozillaTeam/Bugs. When using the exact steps as provided in the above link, Firefox does not crash, it hangs instead and I can't get trough that hang. I can't get a complete backtrace in this case. I'm attaching the output that I get when running a debug Nightly build. If you need any other information or you can give me any suggestions that will help me get a complete crash backtrace, please let me know.
You need to log in before you can comment on or make changes to this bug.