Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

"Internal Error - An uncaught exception" crash message - happens when any menu item is selected

  • 7 replies
  • 5 have this problem
  • 9 views
  • Last reply by hbmiller

more options

Running latest version (49.0.1) on MacOS Sierra 10.2 (also latest version). Worked perfectly until the v. 49 update. Same problem on both Macs running this version. This happens in safe mode as well as in regular operation. Completely stumped and cannot find an analogous problem/resolution pair in the support database.

Running latest version (49.0.1) on MacOS Sierra 10.2 (also latest version). Worked perfectly until the v. 49 update. Same problem on both Macs running this version. This happens in safe mode as well as in regular operation. Completely stumped and cannot find an analogous problem/resolution pair in the support database.

Chosen solution

FredMcD said

Please flag your last post as Solved Problem so others will know.

Flag? How?

Read this answer in context 👍 1

All Replies (7)

more options

Start your Computer in safe mode with networking. Then start Firefox. Try Safe websites. Is the problem still there?

Starting The Computer In Safe Mode;
Free Online Encyclopedia

more options

Firefox starts and runs properly when the Mac starts in Safe Mode. How do I find the crashing application?

more options

There is no way to tell. You will have to shut down to see for yourself. Check at the Mac forums for better help.

As a test, disable your protection programs.

Please let us know what happens. Good luck.

more options

In my case the culprit was Deskovery 2.3.3. When this utility is running I get always the "Internal Error" message when trying to access any menu item, without it Firefox works fine. Updating to Deskovery 3 (beta3) also helps.

Modified by resucami

more options

That was very good work. Well done. Please flag your last post as Solved Problem so others will know.

more options

Chosen Solution

FredMcD said

Please flag your last post as Solved Problem so others will know.

Flag? How?

more options

The lead was correct -- a startup program was the culprit and was causing Firefox to crash. In this case, the culprit was an older utility called RedQuits. Disabling it solved the problem entirely. Conventionally, it was necessary to disable all startup programs and then re-add them one at a time to detect the culprit. Thanks to all for your kind assistance.