Firefox-Hilfeforum

In making this post I am following instructions found at https://support.mozilla.org/en-US/kb/troubleshoot-firefox-crashes-closing-or-quitting, which include the statement "Fill out the Details section of the next page..." which seems to refer to THIS page, but I see no Details section here, so I'll just put the details where they seem to apply.

Firefox Version 102, installed today, shows the same symptom I've been seeing for several weeks, perhaps months: whenever Firefox is closed, a crash report popup appears on the screen (after a minute or two). I've been submitting these on a regular basis and hoped that Version 102 would contain a fix, but the issue continues.

So today I've created some minimum-to-reproduce examples, in each case using the same setup, but closing Firefox in a different manner:

Setup: Firefox for Windows V 102 installed today. Windows 10 is up to date. I open Firefox in troubleshooting mode, which displays my home page, located on a shared server that I use for a website and other stuff I want to be able to access from anywhere. Nothing exotic, just a list of links. That works.

Then, without doing anything else (for purposes of these tests), I close Firefox via one of the following (with associated report ID):

• Click on large X in the upper right corner of the window.

   bp-e31ef7d6-8d17-41c8-a204-0e53c0220630e

• In the window menu, select File > Exit.

  bp-d15f97c8-267f-4550-9d42-69eb70220630

• On the task bar, RMB on Firefox, then select 'Close window'.

 bp-39756c12-ccb7-4f83-998a-ec8030220630

My system is an HP laptop with AMD Vision A6 processor. My wife uses a Dell all-in-one on the same wired network and does not experience the crash-on-close symptom. This makes me suspect my hardware, but just tested with other browsers:

Chrome - Blocked my home page (never saw that before, but I use Firefox...) until I removed the block from Settings. Closed without crashing. Edge - Updated itself, then gave me the same "Not secure" warning as Chrome, but displayed the home page anyway. Closed without crashing.

In all cases, the link to my home page is specified as http://, not https:// My wife's system is set up the same way.

My question: How can I get Firefox to close gracefully, without spitting out a crash report 1-2 minutes later? Note that I can OPEN Firefox and use it for hours without incident, but if I close it and do something else, when I close THAT, there's the Firefox crash report window underneath.

I just ran the w3.org validator on my home page and I see that a few errors have crept in,. mostly unencoded ampersands. I'll fix those, but if that caused a problem for Firefox, would it wait until much later to crash? And why only on my system, not my wife's?

Suggestions?

This morning I re-installed an update to Zoom (on Linux - ElementaryOS / Ubuntu 18.04). Since installing, I've not been able to follow links from Firefox to Zoom (zoommtg links don't open the app). However, they still work from Epiphany.

The slight confounding factor is that I realised that I've been updated to FF 104 overnight, so that might be an issue.

I've been looking at network.protocol-handler.... settings in about:config, based on this article: https://superuser.com/questions/1343020/how-to-configure-firefox-open-zoom-urls-using-zoom-application#1351073

I've also been looking at xdg-settings (based on this article) https://www.reddit.com/r/kde/comments/i83m8i/zoom_desktop_client_isnt_launching_from_browser/ which suggests the problems might be to do with xdg-settings calling /usr/share/applications/zoom.desktop when the available file is /usr/share/applications/Zoom.desktop However, I have not been able to alter the xdg-settings parameter - when I try: $ xdg-settings set default-url-scheme-handler zoommtg zoom.desktop it does not change the setting - it remains as Zoom.desktop

I should mention that the version of FF I'm running is delivered as a snap - but this was not a problem before 104 / my latest Zoom installation. Also, this version of FF has no problem opening up MS Teams meetings or Slack groups. handlers.json includes : ... "slack":{"action":4},"snap":{"action":4},"zoommtg":{"action":4},"msteams":{"action":4}}, .... so I am thinking the problem must lie somewhee else.

Any suggestions would be gratefully received.

thanks Andy