Arch Linux

xtian

Member

Registered: 2013-08-25

Posts: 179

[solved] What's the way to diagnose Firefox crash?

I was checking out some posts at a web site Core77 1, 2.

When I scroll to the bottom of the page, the screen goes black and Firefox crashes. The only thing that shows up in /var/logs is a `faillog` and a `btmp` file with gibberish.

Last edited by xtian (2015-03-26 21:29:50)

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 13,720

Website

Re: [solved] What's the way to diagnose Firefox crash?

Journalctl and coredumpctl are the best places to start looking.

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

nullified

Member

From: Massachusetts, USA

Registered: 2013-12-09

Posts: 468

Re: [solved] What's the way to diagnose Firefox crash?

Run it from a terminal and you can get:

[GFX1]: Failed to create similar cairo surface! Size: Size(52,23) Status: 1

Unfortunately, I couldn't find much on DDG about this.

---

"We may say most aptly, that the Analytical Engine weaves algebraical patterns just as the Jacquard-loom weaves flowers and leaves." - Ada Lovelace

alphaniner

Member

From: Ancapistan

Registered: 2010-07-12

Posts: 2,810

Re: [solved] What's the way to diagnose Firefox crash?

It's kind of backwards from normal troubleshooting, but you could install NoScript and selectively enable things to see if you can pin down the culprit domain or object.

---

But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

xtian

Member

Registered: 2013-08-25

Posts: 179

Re: [solved] What's the way to diagnose Firefox crash?

... you could install NoScript

That did the trick. `$coredumpctl` only showed firefox,

Thu 2015-03-26 16:00:00 EST    4051  1000  1000  11 * /usr/lib/firefox/plugin-container
Thu 2015-03-26 16:00:01 EST    5661  1000  1000  11 * /usr/lib/firefox/plugin-container
Thu 2015-03-26 16:08:34 EST    6466  1000  1000  11 * /usr/lib/firefox/plugin-container
Thu 2015-03-26 16:08:37 EST    6358  1000  1000  11 * /usr/lib/firefox/firefox
Thu 2015-03-26 16:09:43 EST    6660  1000  1000  11 * /usr/lib/firefox/plugin-container
Thu 2015-03-26 16:09:43 EST    6554  1000  1000  11 * /usr/lib/firefox/firefox
Thu 2015-03-26 16:20:15 EST    6689  1000  1000  11   /usr/lib/firefox/firefox
Thu 2015-03-26 16:20:16 EST    6888  1000  1000  11 * /usr/lib/firefox/plugin-container
Thu 2015-03-26 16:54:22 EST    1327  1000  1000  11 * /usr/lib/firefox/plugin-container
Thu 2015-03-26 16:54:28 EST    1207  1000  1000  11 * /usr/lib/firefox/firefox
Thu 2015-03-26 17:06:48 EST    2194  1000  1000  11 * /usr/lib/firefox/plugin-container
Thu 2015-03-26 17:06:49 EST    1770  1000  1000  11 * /usr/lib/firefox/firefox
Thu 2015-03-26 17:20:31 EST    1685  1000  1000  11 * /usr/lib/firefox/plugin-container
Thu 2015-03-26 17:20:35 EST    1207  1000  1000  11 * /usr/lib/firefox/firefox

I turned off plugins, and the problem kept happening.

After fiddling around with NoScript, I found evidence of what I expected. The host's own script was causing the trouble. With some more investigation and maybe firebug I can look for the offending script...

Thank you all for your help.

Last edited by xtian (2015-03-26 21:30:57)