Firefox - Your tab just crashed
Firefox 57.0.4 (64-bit) under Linux Mint 18.3 Prior to Jan 21, no problem encountered then on 21st Jan, get message "Your tab just crashed" while trying to reach "https://www.bonprix-wa.be/". The page is displayed and images are loaded. Keep loading then suddenly, it crashes. The same occured with "https://www.renaissancecss.com/?ref=webdesignernews.com". (First 'faulty' site has been accessed succesfully in the week prior to Jan 21) When those are the only two opened tabs, Firefox completely crashes (window disappears) Same occurs in Safe Mode and after Refresh. No crash report generated
Before somebody asks, I didn't change any settings of Firefox prior to troubles ...
All Replies (20)
Gah-Your-tab-just-crashed https://support.mozilla.org/en-US/kb/firefox-crashes-troubleshoot-prevent-and-get-help
In the address bar, type about:crashes<enter>.
Note: If any reports do not have BP- in front of
the numbers/letters, click it to submit them.
The crash report is several pages of data. We need the report numbers to see the whole report.
Using your mouse, mark the most recent 7 - 10 crash reports, and copy them. Now go to the reply box and paste them in.
For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support
about:crashes gives the error "That address doesn't look right.", so no crash report. Likewise, there is nothing in folder "Crash Reports" registered on Jan 21 or today. There are also only two subfolders: "events" (empty) and "pending" (dated Dec 18, 2017).
I also logged HTTP activity. The last 20 lines of log.txt-main are:
2018-01-22 09:03:25.078949 UTC - [Socket Thread]: D/nsSocketTransport index=7 mActiveCount=14 2018-01-22 09:03:25.078957 UTC - [Socket Thread]: D/nsSocketTransport active=13 idle=0 2018-01-22 09:03:25.078966 UTC - [Socket Thread]: D/nsSocketTransport active [6] { handler=0x7f96f4ee3400 condition=80004004 pollflags=7 } 2018-01-22 09:03:25.078974 UTC - [Socket Thread]: D/nsSocketTransport nsSocketTransportService::DetachSocket [handler=0x7f96f4ee3400] 2018-01-22 09:03:25.078983 UTC - [Socket Thread]: D/nsSocketTransport nsSocketTransport::OnSocketDetached [this=0x7f96f4ee3400 cond=80004004] 2018-01-22 09:03:25.078991 UTC - [Socket Thread]: D/nsSocketTransport nsSocketTransport::RecoverFromError [this=0x7f96f4ee3400 state=4 cond=80004004] 2018-01-22 09:03:25.078999 UTC - [Socket Thread]: D/nsSocketTransport nsSocketTransport::RecoverFromError do not retry because mDoNotRetryToConnect is set [this=0x7f96f4ee3400] 2018-01-22 09:03:25.079008 UTC - [Socket Thread]: D/nsSocketTransport nsSocketInputStream::OnSocketReady [this=0x7f96f4ee3660 cond=80004004] 2018-01-22 09:03:25.079016 UTC - [Socket Thread]: D/nsSocketTransport nsSocketOutputStream::OnSocketReady [this=0x7f96f4ee3698 cond=80004004] 2018-01-22 09:03:25.079028 UTC - [Socket Thread]: D/nsSocketTransport nsSocketTransport: calling PR_Close [this=0x7f96f4ee3400] 2018-01-22 09:03:25.079325 UTC - [Socket Thread]: D/nsSocketTransport destroying nsSocketTransport @0x7f96f4ee3400 2018-01-22 09:03:25.079359 UTC - [Socket Thread]: D/nsSocketTransport nsSocketTransportService::RemoveFromPollList [handler=(nil)] 2018-01-22 09:03:25.079369 UTC - [Socket Thread]: D/nsSocketTransport index=6 mActiveCount=13 2018-01-22 09:03:25.079382 UTC - [Socket Thread]: D/nsSocketTransport active=12 idle=0 2018-01-22 09:03:25.079394 UTC - [Socket Thread]: D/nsSocketTransport active [5] { handler=0x7f970c461400 condition=0 pollflags=5 } 2018-01-22 09:03:25.079409 UTC - [Socket Thread]: D/nsSocketTransport active [4] { handler=0x7f97020e7400 condition=0 pollflags=5 } 2018-01-22 09:03:25.079423 UTC - [Socket Thread]: D/nsSocketTransport active [3] { handler=0x7f96f4ed9800 condition=0 pollflags=5 } 2018-01-22 09:03:25.079438 UTC - [Socket Thread]: D/nsSocketTransport active [2] { handler=0x7f97017a1400 condition=0 pollflags=5 } 2018-01-22 09:03:25.079460 UTC - [Socket Thread]: D/nsSocketTransport active [1] { handler=0x7f9570a8cc00 condition=0 pollflags=5 } 2018-01-22 09:03:25.079469 UTC - [Socket Thread]: D/nsSocketTransport active [0] { handler=0x7f9570a8d800 condition=0 pollflags=5 } 2018-01-22 09:03:25.079477 UTC - [Socket Thread]: D/nsSocketTransport calling PR_Poll [active=12 idle=0]
And for log.txt-child:
2018-01-22 09:03:20.666908 UTC - [Socket Thread]: D/nsSocketTransport PollableEvent::Clear 2018-01-22 09:03:20.666922 UTC - [Socket Thread]: D/nsSocketTransport PollableEvent::Signal PR_Read 1 2018-01-22 09:03:20.666936 UTC - [Socket Thread]: D/nsSocketTransport STS dispatch [0x7f24f9f8a2c0] 2018-01-22 09:03:20.666947 UTC - [Socket Thread]: D/nsSocketTransport OnDispatchedEvent Same Thread Skip Signal 2018-01-22 09:03:20.666970 UTC - [Socket Thread]: V/nsHttp HttpBackgroundChannelChild::RecvOnTransportAndData [this=0x7f24fb273600] 2018-01-22 09:03:20.666982 UTC - [Socket Thread]: V/nsHttp > pending until OnStartRequest [offset=0 count=49] 2018-01-22 09:03:20.667000 UTC - [Socket Thread]: D/nsSocketTransport STS poll iter 2018-01-22 09:03:20.667010 UTC - [Socket Thread]: D/nsSocketTransport calling PR_Poll [active=0 idle=0] 2018-01-22 09:03:20.667020 UTC - [Socket Thread]: D/nsSocketTransport timeout = -1 milliseconds 2018-01-22 09:03:20.668376 UTC - [Chrome_ChildThread]: D/nsSocketTransport PollableEvent::Signal 2018-01-22 09:03:20.668419 UTC - [Chrome_ChildThread]: D/nsSocketTransport PollableEvent::Signal PR_Write 1 2018-01-22 09:03:20.668438 UTC - [Socket Thread]: D/nsSocketTransport ...returned after 2 milliseconds 2018-01-22 09:03:20.668458 UTC - [Socket Thread]: D/nsSocketTransport PollableEvent::Clear 2018-01-22 09:03:20.668472 UTC - [Socket Thread]: D/nsSocketTransport PollableEvent::Signal PR_Read 1 2018-01-22 09:03:20.668484 UTC - [Socket Thread]: D/nsSocketTransport STS dispatch [0x7f24f9f8a440] 2018-01-22 09:03:20.668495 UTC - [Socket Thread]: D/nsSocketTransport OnDispatchedEvent Same Thread Skip Signal 2018-01-22 09:03:20.668515 UTC - [Socket Thread]: V/nsHttp HttpBackgroundChannelChild::RecvOnStopRequest [this=0x7f24fb273600] 2018-01-22 09:03:20.668526 UTC - [Socket Thread]: V/nsHttp > pending until OnStartRequest [status=0] 2018-01-22 09:03:20.668544 UTC - [Socket Thread]: D/nsSocketTransport STS poll iter 2018-01-22 09:03:20.668555 UTC - [Socket Thread]: D/nsSocketTransport calling PR_Poll [active=0 idle=0] 2018-01-22 09:03:20.668565 UTC - [Socket Thread]: D/nsSocketTransport timeout = -1 milliseconds
kelumden said
about:crashes gives the error "That address doesn't look right."
As this is an internal page, something is wrong with the browser install.
Let’s do a full clean re-install;
Download Firefox For All languages And Systems {web link}
Save the file. Then Close Firefox.
Using your file browser, open the Programs Folder on your computer.
Windows: C:\Program Files C:\Program Files (x86)
Mac: Open the "Applications" folder. https://support.mozilla.org/en-US/kb/how-download-and-install-firefox-mac
Linux: Check your user manual. If you installed Firefox with the distro-based package manager, you should use the same way to uninstall it. See Install Firefox on Linux; https://support.mozilla.org/en-US/kb/install-firefox-linux
If you downloaded and installed the binary package from the Firefox download page, simply remove the folder Firefox in your home directory. http://www.mozilla.org/firefox#desktop ++++++++++++++++++++++++++++ Look for, and remove any Mozilla or Firefox program folders. Do not remove the Mozilla Thunderbird folder if there is one.
Do Not remove the profiles folder.
After rebooting the computer, run a registry scanner if you have one. Then run the installer. +++++++++++++++++++++++++++ If there is a problem, start your Computer in safe mode and try again.
http://encyclopedia2.thefreedictionary.com/Linux+Safe+Mode This shows how to Start all Computers in Safe Mode; Free Online Encyclopedia
Nope. Now on FF 58.0 (64 bit) [mint-1.0] and still crashing on some genuine sites like Deviant Arts (only when attempting to log) even when disabling multi-process. Slowly thinking of using alternatives if they provide an accessible way to handle bookmarks ...
Trying to find why the tab crashes (accessing Login screen of DeviantArts), I used Developer Tools. When I tracked Network activity, the tab didn't crash. Thereafter I recorded the activity using Performances and saved the result: the tab still didn't crash.
I called for more help. Please post the new crash reports.
kelumden can you type about:about with a : in Location (address) bar as this will list all of the about: urls you can use to see if the about:crashes is listed. Third-party builds of Firefox on Linux may not use and send crash report info to Mozilla.
Result of about:about in attached image ... about:crashes is available and I have send some of the crash reports already. I didn't send them all as I tend to reload the crashed tab resulting in many consecutive reports for the same context (see second image[just a fraction]). BTW, it also occur that one of the processes consume 2Gb of memory while Firefox as a whole uses about 3.7Gb, forcing Linux to uses around 2Gb of the swap area. The FF session running while I write this mail uses 1.1Gb. Thanks for the help.
You should submit and crash reports since the developers do look at them, and they might find a trend that needs working on.
Please submit the last 5 - 7 reports by clicking on them.
Here is the top of the list of submitted reports. Top three are fresh of the day. BTW, to be able to login with Deviant Arts, I first disabled Javascript, accessed the login page, re-enabled Javascript and proceed with the login procedure.
Using your mouse, mark the most recent 7 - 10 crash reports, and copy them. Now go to the reply box and paste them in.
Here, there are:
bp-f92bfcf7-4b46-4fb2-b191-c261b0180317 3/17/18 1:48 PM bp-0e025e57-4e18-42f4-99a9-621fd0180317 3/17/18 1:47 PM bp-cda6ea48-f841-4350-8b52-0f7360180317 3/17/18 1:47 PM bp-04f32c9e-45d3-4afa-8112-821a90180316 3/16/18 10:50 PM bp-009c0982-5aec-4f32-8880-23cd60180316 3/16/18 10:49 PM bp-0d83ef70-a1a3-40da-a277-bcaf40180316 3/16/18 10:49 PM bp-f9d35361-b5f4-4360-9eff-57fdc0180316 3/16/18 10:46 PM bp-a0d6693f-8c8f-483b-bfbe-342c51180316 3/16/18 10:13 PM bp-c5d7e459-b3b7-4fb5-9d66-4aad61180316 3/16/18 3:43 PM bp-699e0edb-0d5d-4221-b59d-337e11180316 3/16/18 3:42 PM bp-ef3f989f-0661-4f49-a3b6-310061180316 3/16/18 3:40 PM bp-df4acf6d-5b99-464f-8e5e-d9f0d0180316 3/16/18 3:35 PM
bp-f92bfcf7-4b46-4fb2-b191-c261b0180317 bp-0e025e57-4e18-42f4-99a9-621fd0180317 bp-cda6ea48-f841-4350-8b52-0f7360180317 bp-04f32c9e-45d3-4afa-8112-821a90180316 bp-009c0982-5aec-4f32-8880-23cd60180316
Signature: r300_dri.so@0x4f0d62
I called for more help.
That might be a problem with the graphics display driver (DRI). I see that you force hardware acceleration on.
- "layers.acceleration.force-enabled" = true
You can try to disable hardware acceleration in Firefox.
- Options/Preferences -> General: Performance
remove checkmark: [ ] "Use recommended performance settings"
remove checkmark: [ ] "Use hardware acceleration when available" - https://support.mozilla.org/en-US/kb/performance-settings
Close and restart Firefox after modifying the setting to make the change effective.
Disabling hardware acceleration didn't help. BTW, I moved to FF 58.0.2 ...
Last two crash reports: bp-c6d7387e-1aca-4856-958d-36fba0180318 3/18/18 11:07 AM bp-7e4acf4e-c899-4c4c-aca4-100fe0180318 3/18/18 11:04 AM
Found something: when starting in Safe mode, FF does not crash when accessing sites that would normally crash it ... will investigate further down the line !
No trouble due to themes (I use the default one), nor with extension. Hardware acceleration is still disabled, but FF keep on crashing.
Last 3 reports: bp-60dcdd97-4222-4fab-b74c-b0e740180318 3/18/18 11:27 AM bp-37961fae-7ee1-4bc3-ab0c-6f3f20180318 3/18/18 11:27 AM bp-2404bfee-fcc6-443d-9387-66c670180318 3/18/18 11:26 AM
Current installation: FF 59.0.1 (upgraded this day) No change in situation: bp-f3337ace-6e19-4db9-901c-6a6b80180322 3/22/18 11:08 PM
Due to a major crash after updating my configuration, I had to reinstall the OS (Linux Mint 18.3 Sylvia). Before testing FF, I installed all the upgrades to the OS, including FF 59.0.1. No change in behavior (see last crash report)
bp-5db5a606-8053-4462-9c71-5f9ad0180327 3/27/18 2:57 PM
What Firefox version are you using because the Socorro server doesn't recognize your build (buildID: 20180319141609)?
Is this a version from the official Mozilla server?