Can you give me your crash reports?

1. Enter about:crashes in the Firefox address bar and press Enter. A Submitted Crash Reports list will appear, similar to the one shown below.
2. Copy the 5 most recent Report IDs that start with bp- and paste them into your response here.

bp-c616c9b2-11e2-4499-8aa3-533472140519 5/19/2014 2:27 PM
bp-d62ea09b-9fa8-4aef-8b55-2fbf72140518 5/18/2014 2:18 PM
bp-bbb40dda-264c-4c90-9a0b-79c452140515 5/15/2014 4:16 PM
bp-bc8dba1c-0927-4e85-887b-736eb2140515 5/15/2014 12:48 PM
bp-79ef2d72-d456-40b5-a23c-9b2e72140515 5/15/2014 12:45 PM

4 out of 5 of your crash reports are with this signature

• js::jit::LinearScanAllocator::assign(js::jit::LAllocation

Which point to a problem with JIT

The one that had a different signature

• mozilla::gfx::DrawTarget*

Which points to a problem with graphics.
Try each suggestion and wait at least 2 hours before trying the second solution to be sure the first one worked. Continue browsing as normally

For the js:jit signature

Does it still crash in Safe Mode?
You can start Firefox in Safe Mode below:

• Windows/Mac: Go to Help > Restart with add-ons disabled
• Linux: Run firefox -safe-mode in the Terminal/Konsole

If it doesn't, then set javascript.options.baselinejit to false in about:config:

• Navigate to about:config in your Address Bar
• Press the "I'll be careful, I promise!" button to proceed
• Search for javascript.options.baselinejit and set it to false by right clicking the pref and selecting Toggle.
• Restart Firefox and see if it works properly.

for the gfx::DrawTarget signature This is an on going issue with graphics acceleration and it is being addressed in

• Bug 805406 - crash in gfxContext::PushClipsToDT with Direct2D 1.1 (d3d11.dll 6.2 or 6.3)

Please read the Bugzilla Etiquette if you decide to post in crash reports.

D2d is blocklisted for Firefox 21, and the current nightly version 31/32 is being monitored to less crashes. Now there are patches pending and performance monitoring being preformed on the patches.

For identification:

• Bug 902952 - Use Direct2D 1.1 on mozilla-central , please feel free to look at different bug descriptions at your leisure for *fixed* :-)

For current plan:

• Milestone for this issue is version 30. So it will be a while before non Firefox Beta is affected by the changes made.

It is not a work around, but the changes can be seen in version 30. If you continue to see crashes in the next version, I am happy to add them to the bug to see if there is more info. If you have any other questions, we are happy to help.

Firefox has hardware acceleration set to "on" by default, but it's still young, which means some video cards or drivers might have problems with it. You can try to disable hardware acceleration to see if that alleviates your problems.

You might need to restart Firefox in order for this to take effect, so save all work first (e.g., mail you are composing, online documents you're editing, etc.).

Then perform these steps for Firefox version 29.0 and above:

• Click the menu button and select Options for Windows or Preferences on Mac or Linux. For Firefox 28.0 and previous versions, click the orange Firefox button at the top left, then select the "Options" button, or, if there is no Firefox button at the top, go to Tools > Options.
• In the Firefox options window, click the Advanced tab, then select "General".
• In the settings list, you should find the Use hardware acceleration when available checkbox. Uncheck this checkbox.
• Now, restart Firefox and see if the problems persist.

Additionally, please check for updates for your graphics driver by following the steps mentioned in the following Knowledge base articles:

• Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems

• Upgrade your graphics drivers to use hardware acceleration and WebGL