Have you tried disabling Firefox from using hardware acceleration? Many users have reported Firefox 38 being sluggish with some display drivers, so this is a reasonably quick way to test whether that is a factor for you.

"3-bar" menu button (or Tools menu) > Options > Advanced

On the "General" mini-tab, uncheck the box for "Use hardware acceleration when available"

This takes effect the next time you exit Firefox and start it up again. Any difference?

Thank you for submitting crash reports. You can share the reports with forum volunteers to see whether they point to the solution. Please check the last section of the support article "Firefox Crashes" for steps to get those crash report IDs, and then post some of the recent ones here.

Doing that now and will monitor and report back.

Thank you.

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP in front of the numbers/letters, click it and select Submit.

Using your mouse, mark the most resent 7 - 10 crash reports, and copy them. Now go to the reply box below and paste them in.

That actually brings up several entries in a forum from 2008, nothing relating to my crash reports. Where would I find MY crash reports on my system?

about:crashes is an internal page - in the Firefox UI. You're typing it wrong if a search on the internet is being done.

Then where do I type it?

You type it into Firefox's address bar (where the URL of pages is normally displayed) and then press Enter or Return to load it.

If that isn't working for some reason, you can call up the Options page and edit the address from about:preferences to about:crashes and press Enter to load it that way:

"3-bar" menu button (or Tools menu) > Options

Thank you. [when I clicked 2 others, they were being "fetched" for severealseconds and then got BP in front of them, apparently having been submitted. This one actually appeared - (5/17/2015 7:30 AM):

Firefox 37.0.2 Crash Report [@ mozilla::gfx::UserData::Add(mozilla::gfx::UserDataKey*, void*, void (*)(void*)) ]

Search Mozilla Support for Help ID: e3ea088a-04b6-402a-8236-7dd742150518 Signature: mozilla::gfx::UserData::Add(mozilla::gfx::UserDataKey*, void*, void (*)(void*))

   Details
   Metadata
   Modules
   Raw Dump
   Extensions
   Correlations

Signature mozilla::gfx::UserData::Add(mozilla::gfx::UserDataKey*, void*, void (*)(void*)) More Reports Search UUID e3ea088a-04b6-402a-8236-7dd742150518 Date Processed 2015-05-18 16:14:41.105823 Uptime 145242 Last Crash 145285 seconds before submission Install Age 2157171 since version was first installed. Install Time 2015-04-23 17:01:37 Product Firefox Version 37.0.2 Build ID 20150415140819 Release Channel release OS Windows NT OS Version 6.1.7601 Service Pack 1 Build Architecture x86 Build Architecture Info GenuineIntel family 6 model 42 stepping 7 | 4 Crash Reason EXCEPTION_ACCESS_VIOLATION_READ Crash Address 0x8 User Comments App Notes

AdapterVendorID: 0x8086, AdapterDeviceID: 0x0102, AdapterSubsysID: 2ada103c, AdapterDriverVersion: 9.17.10.2932 D3D11-WARP? D3D11-WARP- D2D? D2D1.1? D2D1.1+ D2D+ DWrite? DWrite+ D3D11 Layers? D3D11 Layers+

Processor Notes sp-processor06_phx1_mozilla_com.29239:2015; MozillaProcessorAlgorithm2015; skunk_classifier: reject - not a plugin hang EMCheckCompatibility

True

Winsock LSP

MSAFD Tcpip [TCP/IP] : 2 : 1 :

MSAFD Tcpip [UDP/IP] : 2 : 2 : %SystemRoot%\system32\mswsock.dll 
MSAFD Tcpip [RAW/IP] : 2 : 3 :  
MSAFD Tcpip [TCP/IPv6] : 2 : 1 : %SystemRoot%\system32\mswsock.dll 
MSAFD Tcpip [UDP/IPv6] : 2 : 2 :  
MSAFD Tcpip [RAW/IPv6] : 2 : 3 : %SystemRoot%\system32\mswsock.dll 
RSVP TCPv6 Service Provider : 2 : 1 :  
RSVP TCP Service Provider : 2 : 1 : %SystemRoot%\system32\mswsock.dll 
RSVP UDPv6 Service Provider : 2 : 2 :  
RSVP UDP Service Provider : 2 : 2 : %SystemRoot%\system32\mswsock.dll

Adapter Vendor ID

0x8086

Adapter Device ID

0x0102

Total Virtual Memory

4294836224

Available Virtual Memory

426450944

System Memory Use Percentage

80

Available Page File

5077762048

Available Physical Memory

1231618048

Bugzilla - Report this bug in Firefox Core Plugins Toolkit Related Bugs

   1019063NEW --- crash in mozilla::gfx::UserData::Add(mozilla::gfx::UserDataKey*, void*, void (*)(void*))

Crashing Thread Frame Module Signature Source 0 xul.dll mozilla::gfx::UserData::Add(mozilla::gfx::UserDataKey*, void*, void (*)(void*)) gfx/2d/UserData.h 1 xul.dll nsDeviceContext::CreateRenderingContext() gfx/src/nsDeviceContext.cpp 2 xul.dll nsSimplePageSequenceFrame::PrintNextPage() layout/generic/nsSimplePageSequenceFrame.cpp 3 xul.dll nsPrintEngine::PrintPage(nsPrintObject*, bool&) layout/printing/nsPrintEngine.cpp 4 xul.dll nsPagePrintTimer::Run() layout/printing/nsPagePrintTimer.cpp 5 xul.dll nsThread::ProcessNextEvent(bool, bool*) xpcom/threads/nsThread.cpp 6 xul.dll mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) ipc/glue/MessagePump.cpp 7 xul.dll MessageLoop::RunHandler() ipc/chromium/src/base/message_loop.cc 8 xul.dll nsThreadManager::~nsThreadManager() xpcom/threads/nsThreadManager.h 9 xul.dll nsBaseAppShell::Run() widget/nsBaseAppShell.cpp 10 xul.dll nsAppShell::Run() widget/windows/nsAppShell.cpp 11 xul.dll nsAppStartup::Run() toolkit/components/startup/nsAppStartup.cpp 12 xul.dll XREMain::XRE_mainRun() toolkit/xre/nsAppRunner.cpp 13 xul.dll XREMain::XRE_main(int, char** const, nsXREAppData const*) toolkit/xre/nsAppRunner.cpp 14 xul.dll nsAString_internal::Replace(unsigned int, unsigned int, wchar_t const*, unsigned int, mozilla::fallible_t const&) xpcom/string/nsTSubstring.cpp 15 xul.dll nsLocalFile::AppendInternal(nsString const&, bool) xpcom/io/nsLocalFileWin.cpp 16 xul.dll nsLocalFile::Append(nsAString_internal const&) xpcom/io/nsLocalFileWin.cpp 17 kernel32.dll GetProcessPriorityBoost 18 kernel32.dll KernelBaseGetGlobalData 19 xul.dll std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Tidy(bool, unsigned int) c:/tools/vs2013/vc/include/xstring:2282 20 xul.dll `anonymous namespace'::HistogramGet(char const*, char const*, unsigned int, unsigned int, unsigned int, unsigned int, bool, base::Histogram**) toolkit/components/telemetry/Telemetry.cpp 21 xul.dll `anonymous namespace'::HistogramGet(char const*, char const*, unsigned int, unsigned int, unsigned int, unsigned int, bool, base::Histogram**) toolkit/components/telemetry/Telemetry.cpp 22 xul.dll mozilla::TimeStamp::ProcessCreation(bool&) xpcom/ds/TimeStamp.cpp 23 @0x14a237 </p>

Could you paste the URL(s) of the report(s) on the crash stats server? As you may have noticed, those have links into the bug tracking system and to a database of similar reports, and the layout is much more readable there compared with the raw text paste.

Most were submitted. They are: bp-a03eb89b-7557-4670-ab7d-b38722150522 5/22/2015 2:46 AM bp-20064360-02d2-436e-9b42-5d5062150520 5/20/2015 1:50 PM bp-3b3b74b0-5760-4c3c-a773-2e0322150522 5/19/2015 9:47 PM bp-5dd85a5f-2986-4039-ad2c-39c4b2150519 5/19/2015 3:34 PM bp-e3ea088a-04b6-402a-8236-7dd742150518 5/18/2015 12:14 PM bp-7ae70cd1-e5c2-4836-bbab-ddd922150522 5/17/2015 7:30 AM bp-b252e5d2-bfb2-4c6d-acef-71cfb2150516 5/16/2015 7:53 PM bp-037be63f-2a06-4f9f-8800-630a62150516 5/15/2015 10:07 PM cdff1504-f5f1-497f-9311-01332ccf723c 5/13/2015 12:20 AM bp-9da8fdd4-1b39-40fc-b13c-2cc912150511 5/11/2015 11:40 AM bp-e1f81bcb-e4f0-4e38-9bd4-9e2cb2150509 5/9/2015 4:38 PM bp-8af569c9-ed68-46ea-847c-7b0a82150522 5/9/2015 9:03 AM 9bcdd435-7614-4b35-91ef-0c5c3241d30a 5/8/2015 9:03 AM de267b46-d883-4a69-a2c0-629c1b4cc88e 5/5/2015 8:36 PM bp-f778a1f8-1e4b-49c6-9d07-750872150505 5/5/2015 7:39 PM 54f32706-932f-4b85-a2c4-30730de933e9 5/4/2015 8:37 AM

Hi Miriam, I looked at the three latest ones. Two were Flash plugin "hang" reports and one was an "Out of memory" error with 13% of system memory available.

It's hard to address out of memory errors because some are caused by a particular function spinning out of control while others are caused by fragmentation of Windows memory causing Firefox's request for a new chunk of memory to be denied, and I can't always tell the difference.

We have a better idea how to resolve issues with the Flash Player plugin. I'm sure you've seen some of these suggestions before, but just in case:

(1) If you have any recorders/downloaders that interact with Flash media make sure they are as up-to-date as possible, or disable them temporarily.

(2) Disable hardware acceleration in Firefox and in Flash

(A) In Firefox, un-check the box here:

"3-bar" menu button (or Tools menu) > Options > Advanced > General > "Use hardware acceleration when available"

That takes effect the next time you exit and start Firefox up again.

(B) In Flash, right-click the media and choose Settings, then the first mini-tab and uncheck the box to use hardware acceleration. More information in this support article from Adobe: http://helpx.adobe.com/flash-player/kb/video-playback-issues.html#main_Solve_video_playback_issues

(3) Disable protected mode (Windows Vista and higher)

The protected mode feature of the Flash player plugin has security benefits, but seems to have compatibility issues on some systems. There is a hidden setting for this:

(A) In a new tab, type or paste about:config in the address bar and press Enter. Click the button promising to be careful.

(B) In the search box above the list, type or paste flash and pause while the list is filtered

(C) Double-click the dom.ipc.plugins.flash.disable-protected-mode preference to switch its value from false to true.

This might not take effect until all Flash has been unloaded for a few minutes, or you close Firefox.

Hi Miriam, I looked at the next three. One was a Flash plugin "hang" report and two were caused by printing.

There is a bug on file in the tracking system related to those print crashes where they are trying to work out what is causing them. One theory is that the code was designed for the Windows User Account Control (UAC) feature being enabled -- I think UAC is responsible for those annoying prompts about whether Windows has permission to do things you ask it to do -- and when it is disabled, Firefox is mistakenly exceeding the allowable privileges. But I don't think we have enough data to know exactly what the problem is, and I don't know of a workaround at the moment.

When I see the UAC prompt, I respond to it - it's usually during installation of a program / program update. I get the plug-in crashes often, and have to reload the pages in which they occur. [watching several baby birds growing into fledgelings]

I already deselected the hardware acceleration in FF and restarted it yesterday, and just followed the directions to deselect it in Flash and will restart FF and also will be restarting the PC this weekend. I hope that will help.

I appreciate everyone's feedback.

I have the lates version of Firefox and I have turned off hardware acceleration..

Here are my lates crash reports:

bp-cde5d013-0649-4e9a-93ec-003182150603 03/06/2015 10:27 bp-753f4acc-6db9-4d6d-91b9-ef1622150602 03/06/2015 00:02 bp-9b768be9-e72f-4e1a-8621-feadc2150602 02/06/2015 19:03 bp-aaee7512-9f6e-447f-8633-957342150602 02/06/2015 16:58 bp-14dbb86f-4d0d-42f9-843f-b1a722150602 02/06/2015 16:51 bp-647ebe31-0234-4c17-a7e9-ab8192150602 02/06/2015 16:45 bp-3d320d8f-10d0-4c7b-a0dd-4dea72150602 02/06/2015 15:35 bp-be081114-e5c6-428e-8a38-c39082150602 02/06/2015 03:00 bp-78f5fcb2-f6ba-441e-99a2-6e7382150601 02/06/2015 00:23 bp-a3c3821c-a546-42a2-b865-ce9b42150601 01/06/2015 21:50 bp-07c39b47-8617-4af5-a62a-04ac92150601 01/06/2015 20:57 bp-5c883425-f987-4f14-89cb-429f42150601 01/06/2015 12:05 bp-794cdb9d-48aa-4d8f-9630-203382150601 01/06/2015 03:32 bp-8592dcc3-c3f9-4d1e-b4d0-3d3e32150531 01/06/2015 00:56 Seems the cause is usually an EXCEPTION_BREAKPOINT.

How do I overcome this?

BTW Google Chrome behaves in a similar manner, but crashes with far fewer open tabs than Firefox.

Hi weitzd, the five most recent are different out-of-memory errors with diverse causes. Could you start a new question so we don't bombard Miriam with a discussion of issues on your Firefox?

You can start a new question at the following link. Scroll down past the suggestions to continue submitting your question: https://support.mozilla.org/questions/new/desktop/fix-problems

Also the reports show 15 enabled extensions (in addition to the default theme). Could you test in Firefox's Safe Mode? That's a standard diagnostic tool to deactivate extensions and some advanced features of Firefox. More info: Diagnose Firefox issues using Troubleshoot Mode.

If Firefox is not running: Hold down the Shift key when starting Firefox.

If Firefox is running: You can restart Firefox in Safe Mode using either:

• "3-bar" menu button > "?" button > Restart with Add-ons Disabled
• Help menu > Restart with Add-ons Disabled

and OK the restart.

Both scenarios: A small dialog should appear. Click "Start in Safe Mode" (not Refresh).

Any less crashy? However it turns out will be useful information.