Yes, serious crashes with Firefox 37.0.2, but IBM Trusteer issued an update around May 6th to fix the problem. Can you tell whether you have received the update by now? If not, please see this post: https://support.mozilla.org/questions/1061312#answer-726698

More recently, users reported there is a conflict between the NoScript extension and Rapport in Firefox 38. Accordingly, you would not see a problem in Firefox's Safe Mode where extensions are disabled. Could you try that test to see whether there is also a conflict with one of your extensions? (More info: Diagnose Firefox issues using Troubleshoot Mode.)

If Firefox is not running: Hold down the option key when starting Firefox.

If Firefox is running: You can restart Firefox in Safe Mode using either:

• "3-bar" menu button > "?" button > Restart with Add-ons Disabled
• Help menu > Restart with Add-ons Disabled

and OK the restart.

Both scenarios: A small dialog should appear. Click "Start in Safe Mode" (not Refresh).

Any less crashy?

I disabled the add-ons as per your instructions. Within 3 hours Firefox closed by itself and I received the same Mozilla Crash Reporter error message. The message says: “Your crash report will be submitted before you quit or restart.” but I always get this message after I quit or restart:" There was a problem submitting your report.”

If you have submitted crash reports then please post the IDs of one or more recent crash reports that have a "bp-" prefix:

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

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

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

If necessary then you can open about: pages via the location/address bar.

See:

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

Make sure that you have the latest updates of your Trusteer software. You can try to contact Trusteer for support.

• http://www.trusteer.com/support/rapport-installation-links
• http://www.trusteer.com/support/report-problem
• http://www.trusteer.com/support/submit-ticket

Try to update or uninstall and reinstall Trusteer Rapport and if that doesn't help then disable/stop the program for now.

• Start Menu > Programs > Trusteer Rapport > Stop Rapport

Mac:System Preferences -> Other -> Rapport -> Stop Rapport

• bug 1159484 - Firefox 37.0.2 crashes with Trusteer Rapport

Please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html

I don't know how to extract the crash data in those circumstances. Does the last section of the article "Troubleshoot Firefox crashes (closing or quitting unexpectedly)" help at all?

Download the current full installer for Rapport. After, uninstall that program. Restart the computer. Then try Firefox.

Do Not install Rapport at this time.

cor-el said

If you have submitted crash reports then please post the IDs of one or more recent crash reports that have a "bp-" prefix:

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

Here it is: bp-8fd5b677-4afa-463e-87ee-ee70a2150522

The crashing thread includes RapportTanzan380.dylib, so this id definitely an issue with Trusteer.

If updating Trusteer to the latest version doesn't help then you will have to disable Trusteer for now and contact their site for support. See my above post for details.

cor-el said

If updating Trusteer to the latest version doesn't help then you will have to disable Trusteer for now and contact their site for support. See my above post for details.

Thanks again. I have been in touch with Trusteer since early May and they would now like to run a remote access session with me so they can investigate the issue happening in real-time.

cor-el said

The crashing thread includes RapportTanzan380.dylib, so this id definitely an issue with Trusteer. If updating Trusteer to the latest version doesn't help then you will have to disable Trusteer for now and contact their site for support. See my above post for details.

I did not want Trusteer to run a remote access session with me so they could investigate the issue happening in real-time but I have kept a record and since June 6 (with Trusteer Rapport on) I have had no problem with Firefox v.38.0.