Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox Quantum crashes each time I log off of Facebook

  • 7 replies
  • 2 have this problem
  • 3 views
  • Last reply by cor-el

more options

Firefox Quantum crashes every time I'm on Facebook and log off! I get the Firefox "send details" screen each and every time! Can anyone help???

Lida

Firefox Quantum crashes every time I'm on Facebook and log off! I get the Firefox "send details" screen each and every time! Can anyone help??? Lida

All Replies (7)

more options

hello, could you provide your latest few submitted crash reports? please enter about:crashes into the location bar, copy the latest few report ids from there starting with bp- & paste them here into a forum reply. this will give us a better understanding what may be triggering those crashes.

more options

Here you go, but when I typed in "about:crashes", what came up was "Unsubmitted Crash Reports", and I submitted all of them, so I don't understand... Also, there was no "bp" anywhere to be found!  :-\ Lida

Unsubmitted Crash Reports Report ID Date Crashed aecc492c-5759-4ece-ac5f-2174176159fc 12/23/2017 5:48 pm efdc6a8e-2fba-4961-b3bf-ae4fd9a50df5 12/21/2017 10:47 pm c9144c20-0ada-48da-8edc-dbab10d0f005 12/21/2017 3:57 am 3675934e-f38b-446d-8eaa-de6ed68b01ff 12/21/2017 3:57 am bfd1ab64-2172-4095-a528-fe39b6713ed8 12/20/2017 9:22 pm f1fc5241-c9f1-4265-9bf3-baa83625e55b 12/20/2017 5:37 pm 0e70eb07-0632-42db-b42e-391ddefeb97a 12/19/2017 3:22 am f5929975-9e4a-4b37-bee7-f79a5a4d1564 12/19/2017 3:22 am c070c23e-56cb-4119-b25c-dffbb7675e05 12/18/2017 4:33 am d9cedd96-4480-4698-842e-c1f6677ac237 12/18/2017 4:33 am 60cfc7c3-4cba-4ba2-88ea-d21d86d381b6 12/16/2017 4:38 pm 4f57d2f7-dc40-4d74-9dba-04bbe2991834 12/16/2017 4:38 pm 907bf9e7-2741-4149-bdcc-559c1a6b4220 12/15/2017 11:54 pm b0c41152-8e11-4998-8dfb-a1ceab18f8d2 12/15/2017 5:15 am 97b8e9c0-cead-4d55-949d-875b929fec6a 12/14/2017 10:23 pm 27781117-5ccb-4bff-b03d-dca3eba14c3a 12/14/2017 10:23 pm fef859ce-7cae-4169-bc5e-4de79d4916ae 12/11/2017 3:43 pm e9b61b25-8087-4e4b-bc8e-a0e60c0c5833 12/11/2017 3:43 pm 46348d9d-391a-47e4-bbb5-0991c665d08e 12/11/2017 3:43 pm 873cdf36-edef-4c7a-903b-68e630349186 12/11/2017 3:00 pm a6ae6b4e-3502-4739-997d-68a1be0239c0 12/10/2017 5:33 pm

Modified by Lidarose

more options

Ok, well none of the above help nor do the submitted crash reports as they go elsewhere.

Update Video Card Drivers

Please Refresh but do this 1st:

then

TEST....... If no issues then Extensions which need to be added back in 1 at a time and tested ..... Or it is your Profile : Make a new one and test ...:

If is your Profile :

Note: Any customization will revert back to default, you will also need to reinstall Extensions. Please let us know if this solved your issue or if need further assistance.

more options

Sorry...I don't understand a word of your response...  :-( Lida

more options

If a line on the about:crashes page doesn't start with "bp-" then click the line to submit the report and the link will be updated and gets a "bp-" prefix if the report is submitted successfully.

  • please do not add the "bp-" prefix yourself
more options

When I clicked on the latest "unsubmitted crash report" as you stated, it stated "Processing This Crash Report", and I got the following page which I've copied and pasted below, and the same thing occurred when I clicked on any of them. (No "bp-"prefix to be found?):

Product: Select Version: Report:

Super Search Firefox 57.0.2 Crash Report [@ IPCError-browser | ShutDownKill ] Search Mozilla Support for this signature How to read this crash report ID: 4e8f6daf-2c99-4c86-93f4-3de5e0171225 Signature: IPCError-browser | ShutDownKill

   Details
   Metadata
   Bugzilla
   Modules
   Raw Dump
   Extensions
   Telemetry Environment
   Correlations

Signature IPCError-browser | ShutDownKill More Reports Search UUID 4e8f6daf-2c99-4c86-93f4-3de5e0171225 Date Processed 2017-12-25 06:47:31 Uptime 2,150 seconds (35 minutes and 50 seconds) Install Age 1,281,226 seconds since version was first installed (2 weeks, 19 hours and 53 minutes) Install Time 2017-12-09 02:55:04 Product Firefox Release Channel release Version 57.0.2 Build ID 20171206182557 OS Windows 7 OS Version 6.1.7601 Service Pack 1 Build Architecture x86 Build Architecture Info GenuineIntel family 6 model 15 stepping 6 | 2 Adapter Vendor ID

0x10de

Adapter Device ID

0x0400

Startup Crash

False

Process Type content (web) Crash Reason EXCEPTION_BREAKPOINT Crash Address 0x77296c74 User Comments EMCheckCompatibility

True

App Notes

FP(D00-L1000-W00001000-T000) AdapterVendorID: 0x10de, AdapterDeviceID: 0x0400, AdapterSubsysID: 043810de, AdapterDriverVersion: 9.18.13.4181 D2D1.1? DWrite? DWrite+ D2D1.1+ WR? WR- WebGL? EGL? EGL+ GL Context? GL Context+ WebGL+

Processor Notes processor_prod-processor-i-08654899a508a5312_1386; MozillaProcessorAlgorithm2015; non-integer value of "SecondsSinceLastCrash"; Signature replaced with an IPC Channel Error, was: "sandbox::SharedMemIPCClient::DoCall" Crashing Thread (0) Frame Module Signature Source 0 ntdll.dll KiFastSystemCallRet 1 ntdll.dll NtWaitForSingleObject 2 kernelbase.dll WaitForSingleObjectEx 3 kernel32.dll WaitForSingleObjectExImplementation 4 kernel32.dll WaitForSingleObject 5 firefox.exe sandbox::SharedMemIPCClient::DoCall(sandbox::CrossCallParams*, sandbox::CrossCallReturn*) security/sandbox/chromium/sandbox/win/src/sharedmem_ipc_client.cc:82 6 firefox.exe sandbox::CrossCall<sandbox::SharedMemIPCClient, void*, unsigned long, unsigned long, unsigned long>(sandbox::SharedMemIPCClient&, unsigned int, void* const&, unsigned long const&, unsigned long const&, unsigned long const&, sandbox::CrossCallReturn*) security/sandbox/chromium/sandbox/win/src/crosscall_client.h:396 7 firefox.exe sandbox::DuplicateHandleProxy(void*, unsigned long, void**, unsigned long, unsigned long) security/sandbox/chromium/sandbox/win/src/handle_interception.cc:30 8 firefox.exe sandbox::TargetServicesBase::DuplicateHandle(void*, unsigned long, void**, unsigned long, unsigned long) security/sandbox/chromium/sandbox/win/src/target_services.cc:254 9 xul.dll mozilla::ipc::DuplicateHandle(void*, unsigned long, void**, unsigned long, unsigned long) ipc/glue/ProtocolUtils.cpp:198 10 xul.dll mozilla::CrossProcessSemaphore::ShareToProcess(unsigned long) ipc/glue/CrossProcessSemaphore_windows.cpp:78 11 xul.dll mozilla::layers::CrossProcessSemaphoreReadLock::Serialize(mozilla::layers::ReadLockDescriptor&, unsigned long) gfx/layers/client/TextureClient.cpp:1709 12 xul.dll mozilla::layers::TextureClient::SerializeReadLock(mozilla::layers::ReadLockDescriptor&) gfx/layers/client/TextureClient.cpp:601 13 xul.dll mozilla::layers::ShadowLayerForwarder::UseTextures(mozilla::layers::CompositableClient*, nsTArray<mozilla::layers::CompositableForwarder::TimedTextureClient> const&) gfx/layers/ipc/ShadowLayers.cpp:462 14 xul.dll mozilla::layers::ContentClientRemoteBuffer::Updated(mozilla::gfx::IntRegionTyped<mozilla::gfx::UnknownUnits> const&, mozilla::gfx::IntRegionTyped<mozilla::gfx::UnknownUnits> const&, bool) gfx/layers/client/ContentClient.cpp:453 15 xul.dll mozilla::layers::ClientPaintedLayer::UpdateContentClient(mozilla::layers::RotatedContentBuffer::PaintState&) gfx/layers/client/ClientPaintedLayer.cpp:92 16 xul.dll mozilla::layers::ClientPaintedLayer::PaintThebes(nsTArray<mozilla::layers::ReadbackProcessor::Update>*) gfx/layers/client/ClientPaintedLayer.cpp:182 17 xul.dll mozilla::layers::ClientPaintedLayer::RenderLayerWithReadback(mozilla::layers::ReadbackProcessor*) gfx/layers/client/ClientPaintedLayer.cpp:297 18 xul.dll mozilla::layers::ClientContainerLayer::RenderLayer() gfx/layers/client/ClientContainerLayer.h:57 19 xul.dll mozilla::layers::ClientLayer::RenderLayerWithReadback(mozilla::layers::ReadbackProcessor*) gfx/layers/client/ClientLayerManager.h:388 20 xul.dll mozilla::layers::ClientContainerLayer::RenderLayer() gfx/layers/client/ClientContainerLayer.h:57 21 xul.dll mozilla::layers::ClientLayerManager::EndTransactionInternal(void (*)(mozilla::layers::PaintedLayer*, gfxContext*, mozilla::gfx::IntRegionTyped<mozilla::gfx::UnknownUnits> const&, mozilla::gfx::IntRegionTyped<mozilla::gfx::UnknownUnits> const&, mozilla::layers::DrawRegionClip, mozilla::gfx::IntRegionTyped<mozilla::gfx::UnknownUnits> const&, void*), void*, mozilla::layers::LayerManager::EndTransactionFlags) gfx/layers/client/ClientLayerManager.cpp:380 22 xul.dll nsIFrame::ClearInvalidationStateBits() layout/generic/nsFrame.cpp:6536 23 xul.dll nsBlockFrame::GetChildLists(nsTArray<mozilla::layout::FrameChildList>*) layout/generic/nsBlockFrame.cpp:588 24 xul.dll mozilla::layers::ClientLayerManager::EndTransaction(void (*)(mozilla::layers::PaintedLayer*, gfxContext*, mozilla::gfx::IntRegionTyped<mozilla::gfx::UnknownUnits> const&, mozilla::gfx::IntRegionTyped<mozilla::gfx::UnknownUnits> const&, mozilla::layers::DrawRegionClip, mozilla::gfx::IntRegionTyped<mozilla::gfx::UnknownUnits> const&, void*), void*, mozilla::layers::LayerManager::EndTransactionFlags) gfx/layers/client/ClientLayerManager.cpp:438 25 xul.dll nsDisplayList::PaintRoot(nsDisplayListBuilder*, gfxContext*, unsigned int) layout/painting/nsDisplayList.cpp:2347 26 xul.dll mozilla::layers::Layer::MayResample() gfx/layers/Layers.cpp:463 27 xul.dll nsLayoutUtils::PaintFrame(gfxContext*, nsIFrame*, nsRegion const&, unsigned int, nsDisplayListBuilderMode, nsLayoutUtils::PaintFrameFlags) layout/base/nsLayoutUtils.cpp:3737 28 xul.dll nsRect::SaturatingUnion(nsRect const&) gfx/src/nsRect.h:66 29 xul.dll nsLayoutUtils::GetTransformToAncestor(nsIFrame*, nsIFrame const*, bool) layout/base/nsLayoutUtils.cpp:2686 30 @0x1826900f

Modified by Lidarose

more options

Posting the GUID of the crash report is sufficient.

  • bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

No need to post the content on the report.

  • bp-4e8f6daf-2c99-4c86-93f4-3de5e0171225
  • Firefox 57.0.2 Crash Report [@ IPCError-browser | ShutDownKill ]

You can try to disable hardware acceleration in Firefox.

Close and restart Firefox after modifying the setting to make the change effective.

You can check if there is an update for your graphics display driver and check for hardware acceleration related issues.