aspis said

Moreover, I consider abnormal the fact that when I open a single FF instance with the new version, there are 5 (five) firefox.exe processes

More than one process is normal for the current Firefox. http://www.ghacks.net/2016/07/22/multi-process-firefox/

Multi-process Firefox is codenamed "e10s". https://wiki.mozilla.org/Firefox/multiprocess

aspis said

1) FF crashed **for no apparent reason**

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

FredMcD said

aspis said

Moreover, I consider abnormal the fact that when I open a single FF instance with the new version, there are 5 (five) firefox.exe processes

More than one process is normal for the current Firefox. http://www.ghacks.net/2016/07/22/multi-process-firefox/

Multi-process Firefox is codenamed "e10s". https://wiki.mozilla.org/Firefox/multiprocess

Well, two, even three is OK. But five? What other app in the universe does that? Anyway, as I said, this is no problem per se, and it's OK if FF works more effectively in this way, but as long as some of these processes do not stay in memory after FF terminates, which I've seen it happening once. And I can't know how many times this happens because I don't check TM every time FF terminates!

FredMcD said

aspis said

1) FF crashed **for no apparent reason**

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

Thank you. OK, I did that and here are the last five: 5eef2c51-e367-462f-b12f-05a639cf9e23 5/21/2018 2:40 PM b0913ea7-5b77-4292-816d-053d768d70bc 5/21/2018 2:40 PM 902aa35b-26a8-46ca-b9dc-a875d9a2aeeb 5/19/2018 1:14 PM 003ae226-d8ce-462b-926f-6159575d290a 5/18/2018 1:41 PM

If this doesn't help, here are the links to the IDs found in two of them: https://crash-stats.mozilla.com/report/index/566aed5d-e823-4dc9-077-9220a0180522 (May 21) https://crash-stats.mozilla.com/report/index/cb84b42b-e753-43b2-bebb-6a0d90180522' (May 19)

I hope this helps.

When you see 5 processes running Firefox is working properly. There are browsers/tabs, extensions, sandbox all are running as they should as Firefox is a Multi-Thread, Multi-Process Browser.

If you are having issues with crashing as you state please try below : Go to Options --> Privacy & Security and down to Permissions. Please ensure that the box for Prevent Accessibility Services from accessing your browser is Checked, You will need to Re-start Firefox

If was Checked and are still having issues : Please go to Options --> General --> Performance and uncheck the box for Use Recommended Settings and try changing the Process count to 2 and can also go up but note more cpu and ram will be used. You will need to re-start Firefox after making any changes.

If still having problems and this is a older system with little ram move to the Extended Support Release 60.0.1esr : https://support.mozilla.org/en-US/kb/switch-to-firefox-extended-support-release-esr Firefox ESR does not come with the latest features but it has the latest security and stability fixes.

Optimize Win 7

• https://support.microsoft.com/en-ca/help/15055/windows-7-optimize-windows-better-performance
• https://www.techrepublic.com/blog/10-things/10-ways-to-speed-up-windows-7/
• https://www.sevenforums.com/tutorials/11728-optimize-windows-7-a.html

If do not like the looks you can change it in something like 250 million ways but will need to know :

• https://www.howtogeek.com/334716/how-to-customize-firefoxs-user-interface-with-userchrome.css/

Or use a theme :

• https://addons.mozilla.org/en-US/firefox/themes/

and Customize :

• https://www.howtogeek.com/333110/how-to-customize-firefox-quantum-and-remove-the-white-space-around-the-title-bar/#

Please stop replying by quoting what was sent. Thank You. Just quote what is needed only and use the tags : https://www.w3schools.com/tags/tag_blockquote.asp

@Pkshadow, I normally don't use "Quote" for reply, but in this case I had to reply to two persons ... Anyway, I will use the member's alias from know on.

Now, about your "article" -- quite huge reply :) -- on handling crashes, I can't promise I will do all this at the moment. But I will try to, if I see FF keeps crashing. Thank you a lot, anyway, for this detailed reply!

aspis said

Thank you. OK, I did that and here are the last five:
5eef2c51-e367-462f-b12f-05a639cf9e23 5/21/2018 2:40 PM
b0913ea7-5b77-4292-816d-053d768d70bc 5/21/2018 2:40 PM
902aa35b-26a8-46ca-b9dc-a875d9a2aeeb 5/19/2018 1:14 PM
003ae226-d8ce-462b-926f-6159575d290a 5/18/2018 1:41 PM

Any crash report without a bp- first were not sent to the Mozilla servers. Please click on them. Then post the updated numbers.

aspis said

If this doesn't help, here are the links to the IDs found in two of them:
https://crash-stats.mozilla.com/report/index/566aed5d-e823-4dc9-077-9220a0180522 (May 21)
https://crash-stats.mozilla.com/report/index/cb84b42b-e753-43b2-bebb-6a0d90180522' (May 19)

These links are no good.

@FredMcD, I sent you the name of 5 reports WITHOUT A BP-PREFIX (as you can very easily see). I then clicked on 2 of them and I sent you the resulting links. What else do you want? What do you mean by "updated numbers"???

In case you mean the new Report IDs of Submitted Crash Reports added at the end of the page, here they are:

bp-8bc15397-b1b9-4300-a3ca-598570180522 5/22/2018 7:05 PM bp-cb84b42b-e753-43b2-bebb-6a0d90180522 5/22/2018 11:52 AM bp-566aed5d-e823-4dc9-a077-9220a0180522 5/22/2018 11:46 AM

Note that I have not submitted any Report on May 22, as it is shown above. Except if by clicking on an Unsubmitted Reports they are automatically submitted!. (BTW "Unsubmitted" is the wrong word, because it means that they are submitted and then tye are un-submitted! The correct word is "Non-Submitted" or "Not-Submitted" .)

@FredMcD, about the links a sent you: You are just rejecting them as if they are totally irrelevant to the ussue. Well, there's nothing else one can do with these report IDs links. You don't help much with all this, you know. And I am not willing to spend more time with this issue. I hope it will be fixed in the next FF version. Thank you for your efforts, though.

bp-8bc15397-b1b9-4300-a3ca-598570180522 Signature: IPCError-browser | ShutDownKill

Attention Sumo's No system information in the crash report

Attention Sumo's there are 30 related bug reports including; You are not authorized to access bug 1452499

No Modules listed in the report ++++++++++++++++++++++++++++++++++++++++++ Product Firefox Release Channel release Version 60.0.1 Build ID 20180516032328 OS Windows 7 OS Version 6.1.7600

bp-cb84b42b-e753-43b2-bebb-6a0d90180522 Signature: IPCError-browser | ShutDownKill

Attention Sumo's there are 30 related bug reports including; You are not authorized to access bug 1452499

igd10umd32.dll = Intel(R) Graphics Technology +++++++++++++++++++++++++++++++++++ bp-566aed5d-e823-4dc9-a077-9220a0180522 Signature: RtlpWaitOnCriticalSection | RtlpDeCommitFreeBlock | arena_dalloc | je_free | JSScript::maybeSweepTypes

The first report shows; ShutDownKill In general, this means that something about Firefox was not responding.

Only Modulators and above can access bug 1452499 I called for more help.

igd10umd32.dll = Intel(R) Graphics Technology Check that all of your drivers/programs are up-to-date.

OK, @FredMcD. Thanks.

A post was flagged as Solved Problem. If the problem is not solved, please remove that flag. If you don’t, others that can help may not read this post.

Go to that message, and use the Undo link to its right.

OK, @FredMcD, I "undid" it.

Hi, fyi :

@FredMcD, I sent you the name of 5 reports WITHOUT A BP-PREFIX (as you can very easily see). I then clicked on 2 of them and I sent you the resulting links.

When you send a report the report goes elsewhere to be figured out and to be worked on as per it is a known bug. Your information helps others with the issue.

The bp- + the #'s is what we access on a different website than this one.

No as per my long post you have not confirmed if you have done anything that was asked of you re these : Go to Options --> Privacy & Security and down to Permissions. Please ensure that the box for Prevent Accessibility Services from accessing your browser is Checked, You will need to Re-start Firefox

If was Checked and are still having issues : Please go to Options --> General --> Performance and uncheck the box for Use Recommended Settings and try changing the Process count to 2 and can also go up but note more cpu and ram will be used. You will need to re-start Firefox after making any changes.

@Pkshadow, my quote that you used was not for you; it starts with @FredMcD. And @FredMcD has responded to me about that and the matter has been cleared. Please try not to get involved where you shoudn't. Otherwise, thank you anyway for your help.

Hi all

About 20 days have passed since the last comment posted in this thread, but I don't want to start a new on on the same subject, so I update/extend this one with my experience of the latest installed FF version (60.0.2) . I had also installed version 60.0.1esr before that. In the 2 days I have been using FF v60.0.2:

1) After going back and forth in the webpages of a site, at some point It has slowed down considerably and the Developer Toolbar didn't pop up (with Shift-F2 or via Tools menu). I had to restart it twice, with Add-ons disabled, since it's the only other way I know for restating if you want to keep your tags of opened URLs. 2) It has stopped responding temporarily, i.e. for about 10-15 seconds, and it didn't respond to keyboard or mouse. This happened after not being used for about 15 minutes during which time other applications were used (Notepad, Word, etc.)

In short, FF is still problematic. And I wonder if it has reached to a "point of no return" to its previous non-problematic functioning. And I am very curious what FF people mean with the word "update". Because simple and useful things that worked in the past stopped working, e.g. hot keys in the Privacy page like Shift+Alt+A (Accept cookies), Shift+Alt+R (Remember logins). It seems more a "degrade" to me.

Hi all

One month and 10 days have passed since I posted this issue, and I feel I have to update it, as a way to watch its progress. I am on FF v60.0.2.

1) FF not always stalls, as I explained before, to a point you can hardly type anything or do anything -- but still responding somehow -- but everything else -- the programs/apps opened at that moment -- gets stalled. This is something dreadful to see. I finally managed to restart it. Well, what do you know? It -- and everything else -- got immediately alive and well again!! As when you throw back in the water a fish that could hardly breathe and move.

2) Today I saw a new thing that has never but never happened before. The buttons in "Manage Cookies and Site Data" popup window have withered away to a point of non usability. See the screenshot.

All this confirms what I have said already, namely that FF gets degraded with time. People at Mozilla please throw it back in the water!