please : go to the Firefox 3 Bar Menu --> Options --> Privacy & Security panel and under Permissions check (put a tick in the box) the setting to Prevent Accessibility Services from accessing your browser.

Monitor in Task Manager. Should stay below 2 gigs. If excessive then do below and monitor and change if need to...Test and go up again , go back down, it will eventually get a zone you and it can live with.

Go to the 3 Bar Menu then Options --> General --> Performance and untick everything. change the recommended size lower then see how it runs. Note: 1 = No Multiprocessor = slow again. Try 2 Restart Firefox after making these changes please.

Please let us know if this solved your issue or if need further assistance.

Do you see any messages in the terminal window if you start Firefox that way

cd {path_to_firefox}
./firefox

1. Privacy & Security is not under options but preferences!

   Ticked box - done.

2. Only have two gigs total ram - Task manager shows less than one gig in use.

3. Unticked Use hardware acceleration

   Content process limit already set to 2 -> dual processor.

Will monitor and report back later.

Set it to 1 if need to as that was what Firefox used to use before if still continue to have issues. Hardware Acceleration is for your Video Card, determine if needs to stay ticked or not if video colors start to tear while viewing something. It just tells Video Card to do more work.

Please let us know if this solved your issue or if need further assistance.

cor-el - No messages seen

Pkshadow - changed settings have drastically slowed firefox but it still crashes almost constantly with only three tabs open. Once crashed, it will crash every time I reload the tab. Restarting after clearing the cache helps for perhaps two or three pages but after that the crashes start again. Task manager showing 730 -760 megs max in use.

I am having to use conkeror for most browsing tasks now. That has no problems whatsoever. is much faster, and takes far less memory. it shows Mozilla engines do work, just the browser part of firefox is rubbish.

Back to the original question - do I need to look elsewhere? Or which version was the last fully working, pre-Gah! firefox?

You can try to disable multi-process temporarily to see if that gives a more precise error message. Tab crashes only apply to multi-process and with multi-process disable the Firefox browser will likely crash if it still happens.

You can disable multi-process windows in Firefox by setting these prefs to false on the about:config page.

• browser.tabs.remote.autostart = false
• browser.tabs.remote.autostart.2 = false

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

• http://kb.mozillazine.org/about:config

cor-el browser.tabs.remote.autostart was already set to false. browser.tabs.remote.autostart2 was true, so set to false.

No Gah crash! Now a regular full crash with the Mozilla crash reporter popup appearing. Sometimes, but not always, followed by "Sorry. We’re having trouble getting your pages back."

Console start (./firefox) - still no message.

Is that progress?

That was my point: to see if you can get the crash reporter.

If you have submitted crash reports then please post the IDs of one or more recent crash reports that start with "bp-".

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

You can find the report ID of recent crash reports "on the "Help -> Troubleshooting Information" (about:support) page".

• click the "All Crash Reports" button on this page to open the about:crashes page and see all crash reports.

Alternatively you can open about:crashes via the location/address bar.

See also:

• http://kb.mozillazine.org/Mozilla_Crash_Reporter
• https://support.mozilla.org/en-US/kb/Mozilla+Crash+Reporter

bp-00456970-b256-4833-bb01-a926d1171230 12/30/17 7:55 PM bp-d05de5a0-3131-4ca2-9cfb-8a9341171230 12/30/17 7:54 PM bp-cfabbc9d-6a1c-4c00-83c8-602ec1171230 12/30/17 6:21 PM bp-d91ffeba-426d-46a3-8d0e-e87480171230 12/30/17 6:21 PM bp-03564d36-8c4a-4fe1-baef-a21731171230 12/30/17 1:17 PM bp-7cba7095-2896-4e39-b84a-4b3c51171230 12/30/17 1:15 PM bp-8d54f54c-cb6e-47b2-af34-3712b1171230 12/30/17 1:15 PM bp-79d6fbb1-edcd-4832-98c7-28c961171230 12/30/17 1:14 PM bp-1c68f2ce-9188-4645-acff-29d121171230 12/30/17 1:13 PM bp-9fbec41f-bf6e-4495-bb40-41cba1171230 12/30/17 1:13 PM bp-d386cfef-439c-463d-b838-c81291171230 12/30/17 1:12 PM bp-2dfc1098-6544-4faf-a7c3-fb6ed1171230 12/30/17 1:12 PM bp-7d317540-89b3-4d55-ba17-463a51171229 12/30/17 12:39 AM bp-713242b8-9f25-48d0-9670-e47941171229 12/30/17 12:37 AM

Take your pick! Time and date don't match but presumably these are the latest.

Here are some older ones from before I started changing things, but they apparently can't be found by mozilla site.

bp-79d3b6fb-cef8-44d3-a087-c4c0c0171228 12/28/17 12:49 PM bp-a06dfcf6-9b89-4ed6-b650-d9ff21171228 12/28/17 12:48 PM bp-45e2baff-9a49-48e1-89ad-592961171226 12/26/17 3:22 PM bp-2c82af31-ea95-4be2-a7a7-e401a1171226 12/26/17 12:13 PM bp-9a02052e-8876-4fb1-9e1f-951f91171226 12/26/17 12:12 PM bp-4129f651-addd-47a3-b3f8-3b7331171226 12/26/17 12:10 PM bp-6079b3e5-7eb6-490d-b000-647361171226 12/26/17 12:10 PM bp-50d445cb-edbb-4683-aeea-ddfe31171226 12/26/17 2:11 AM bp-014aa4be-7d8a-4529-8562-9698c1171226 12/26/17 2:09 AM bp-6ca27ee6-9c2a-4e68-9b8e-f8de41171226 12/26/17 2:09 AM bp-5dbddc18-c278-48b9-88d5-99f2c1171225 12/25/17 8:21 PM bp-1d798ef9-4ba1-46ce-a720-63cfa1171225 12/25/17 5:18 PM bp-40769b49-9de3-4957-965d-0e0f41171224 12/24/17 2:44 PM bp-3a1608c6-a0c3-4a9b-9cff-4fd711171222 12/23/17 1:19 AM bp-8b0aad4f-6611-4088-a49f-074681171222 12/23/17 1:19 AM bp-68a96cb6-8dd8-4e01-9e52-c36cd1171222 12/23/17 1:19 AM bp-f1cd2f4d-d6be-45fe-8533-040c11171222 12/23/17 12:47 AM bp-6d1d881b-ad05-465a-81c7-1b4500171222 12/23/17 12:46 AM bp-31715546-bb64-4255-a600-2c53c1171222 12/22/17 10:54 PM bp-5b0f032c-01be-4a20-a360-7e4e11171222 12/22/17 7:01 PM bp-42fcd900-8615-44da-94bf-8a3dc1171222 12/22/17 11:58 AM

All the crashes are with nouveau_dri.so and thus display driver related (DRI: Direct Rendering Infrastructure).

• Firefox 57.0.3 Crash Report [@ nouveau_dri.so@0x493d35 ]

Any luck with disabling hardware acceleration is that is currently enabled if that is possible on Linux.

Also make sure that all kernel drivers are updated.

Ah ha! So firefox is now attempting to spy on our computers! And failing miserably. As it should do on a properly configured Linux system - it simply does not have the permissions.

The fact is, I do not have a nouveau_dri.so anywhere on my system. Firefox could not find it so obviously has made a wrong guess. Nouveau is for nVidia cards - sorry, I don't have one of those!

Doesn't it appear strange to you that firefox is on it's 57th major version, and only now finds a problem with a video card driver? And a non-existant one at that! Sounds more like Google where ANY problem is always on the customer's machine and NEVER a fault of Google.

Well, you have answered my question. I DO need to go elsewhere!

57.0.4 Worse than ever! Corporate suicide. An embarrassment to the open source community.

krelay said

57.0.4 Worse than ever! Corporate suicide. An embarrassment to the open source community.

Post appropriate information that will help provide information to help you only. Is there a reason you are being so critical of help. Volunteer Support are trying to help you and have nothing to do with your criticisms. So let us help you please.

The modules list of the crash report shows these items when you search for nouveau:

• https://crash-stats.mozilla.com/report/index/00456970-b256-4833-bb01-a926d1171230#tab-modules
• libdrm_nouveau.so.2.0.0 (and more libdrm items)
• nouveau_dri.so