The crash report shows a problem with Kaspersky. Update the program. If the problem continues, disable it.

Interestimg suggestion which hadn't occurred to me.

Been using Kaspersky for years and haven't had any issues.

Obviously I now have to rattle Kaspersky's cage. I can find a few references to Kaspersky in the bug reports I posted, but nothing which really identifies Kaspersky as a problem. Assuming I have to point the Kaspersky guys to something specific, how did you diagnose a Kaspersky issue? Which part of these bug reports should I bring to their attention?

I just really don't want to get into this loop where,

Adobe says it's a Firefox/Kaspersky problem Mozilla says it's a Kaspersky/Adobe problem Kaspersky says it's a Mozilla/Adode problem

so any ammunition you provide would be helpful

FredMcD said

The crash report shows a problem with Kaspersky. Update the program. If the problem continues, disable it.

If there is still a problem, then it may be something else. Be sure to post any new crash reports.

See also:

• https://support.mozilla.org/en-US/kb/keep-flash-up-to-date-and-troubleshoot-problems

Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration is causing the problem.

• switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Appearance
• do NOT click the "Refresh Firefox" button on the Safe Mode start window

• https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
• https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems

You can try to modify multi-process settings to see if this has effect.

• set dom.ipc.processCount to 1 if it is currently set to a higher value (4)
• disable multi-process windows in Firefox

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'll be careful" to continue.

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

• http://www.ghacks.net/2016/07/22/multi-process-firefox/

FredMcD said

FredMcD said

The crash report shows a problem with Kaspersky. Update the program. If the problem continues, disable it.

If there is still a problem, then it may be something else. Be sure to post any new crash reports.

I have submitted a bug notice to Kaspersky, and am waiting for them to get back to me

In the meantime, I tried disabling Kaspersky, and restarting Firefox. Shockwave flash still crashed after about 2mins, with crash report

bp-0d0217d0-4085-440b-9581-24da10170905 05/09/2017 11:06

I can still find references to Kaspersky in this report, even although it is *supposed* to be disabled. Not sure how significant that is

cor-el said

See also:

• https://support.mozilla.org/en-US/kb/keep-flash-up-to-date-and-troubleshoot-problems

Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration is causing the problem.

• switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Appearance
• do NOT click the "Refresh Firefox" button on the Safe Mode start window

• https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
• https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems

You can try to modify multi-process settings to see if this has effect.

• set dom.ipc.processCount to 1 if it is currently set to a higher value (4)
• disable multi-process windows in Firefox

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'll be careful" to continue.

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

• http://www.ghacks.net/2016/07/22/multi-process-firefox/

####################################################

Firefox and Adobe are both up-to-date. I have tried the suggestions in

https://support.mozilla.org/en-US/kb/keep-flash-up-to-date-and-troubleshoot-problems

None of them seem to change the Shockwave flash crash

Tried firefox in safe mode - this disables the shockwave flash plugin - so obviously this plug-in can't crash. Not sure what else this proves.

Went back to "normal" mode

The dom.ipc.processCount is set to 1 (I have never changed this)

browser.tabs.remote.autostart is set to false, but browser.tabs.remote.autostart.2 is set to true??? Not sure why because I have never (knowingly) changed this. Reluctant to reset this without some idea of what it is going to do???

Okay, let's totally remove Kaspersky. You can always reinstall it again later.

browser.tabs.remote.autostart is the master switch for multi-process and is false during the implementation of this feature. Numbered browser.tabs.remote.autostart.2 are special multi-process opt-in prefs and are used to enable multi-process, so you can try to toggle this pref to false with a double-click and close and restart Firefox.

FredMcD said

Okay, let's totally remove Kaspersky. You can always reinstall it again later.

Kasperksy Tech support gave me a list of things to try, none of these had any effect. Their last resource was also "uninstall" itt. So I did. Then rebooted, and restarted Firefox. The adobe plug-in crashed after about a minute

I would upload this new crash report here, but about:crashes has this crash report as 'pending' (normal for my setup) and nothing I do will change its status to "submitted" with the "BP-" on the front. I just get a spinnning blue disc for about 3mins, and then nothing happens.

Since the plug-in crash happens with their software uninstalled, Kaspersky are off the hook and I have closed my support request with their tech support

cor-el said

browser.tabs.remote.autostart is the master switch for multi-process and is false during the implementation of this feature. Numbered browser.tabs.remote.autostart.2 are special multi-process opt-in prefs and are used to enable multi-process, so you can try to toggle this pref to false with a double-click and close and restart Firefox.

With Kaspersky uninstalled, I used about:config to set

browser.tabs.remote.autostart.2 to false

closed firefox, checked my prefs.js file, and this setting is definitely false.

Restarted firefox, checked about:config, and browser.tabs.remote.autostart.2

is still set to false.

The shockwave flash plugin still crashed after about 1min :-(

So I'm setting this config entry back to true (mainly because, as far as I know), this is whhat the setting has always been

Were you able to get a crash report number?

FredMcD said

Were you able to get a crash report number?

I'm afraid I went a bit nuclear

I had Kaspersky uninstalled and seemed unable to submit any Mozilla crash reports, which got me really annoyed with Firefox. So I decided to uninstall Firefox, and Adobe Flash, then just reinstall Firefox/Flash/Kaspersky from scratch

The bad news is that I decided to clear out all unsubmitted Firefox crash reports as part of the uninstall - after all I can't submit them, so what use are they?

The good news is that since I have reinstalled everything (so far as I am aware I have exactly the same installation as before) the adobe flash plugin no longer crashes. But I have absolutely no idea why

I will continue to monitor, but for the moment, this problem *seems* to have gone away

It could have been a corrupt file that was overwritten.

FredMcD said

It could have been a corrupt file that was overwritten.

Possibly - I have no idea. I'm just going to monitor from this point on.

One thing that bothers me is that if you type something like "problem with firefox and flash" into your favourite search engine, you will get *so* many responses. And most of the suggested solutions are completely useless. (I know because I've tried most of them)

I mean if the actual answer is do a f******g reinstall, why doesn't anyone just make the simple admission - we have no idea what is causing the problem, but if you reinstall everything, your problem will (probably) go away??? Is this hard to admit?

Sometimes a standard answer solves the problem. Other times we need to experiment to find the answer.