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

Firefox hangs, trustd CPU usage soars (Mac)

  • 3 replies
  • 1 has this problem
  • 12 views
  • Last reply by FredMcD

more options

Beginning yesterday after installing a set of fresh MacOS updates, Firefox is repeatedly hanging on my iMac. My computer CPU spins up and Activity Monitor tells me that the process trustd is having a field day, up to 99% CPU usage. Then Firefox stops everything and in the middle of something basic like opening a search engine page or scrolling on an already-open page, I get a spinning rainbow ball of death and have to Force Quit from the taskbar several times before it closes.

Here is what I have tried to resolve:

  • Deleting and reinstalling
  • Troubleshooting mode
  • Downgrading to version 93.0
  • Stopping and restarting the trustd process from both Activity Monitor and from Terminal
  • Full deletion of all Firefox files from command line and installing 96.0.2.

The same problem keeps recurring. For reference, it's on a 2020 iMac running macOS Catalina (10.15.7), i9/16GB. My other machines are not affected. I have not yet upgraded to Big Sur or Monterrey on advice of workplace sysadmin.

Is anyone else seeing this issue with trustd? I am not seeing this problem with other software, just Firefox, but I can't figure out when Firefox calls trustd and what it asks it to do when it does.

Advice warmly welcome.

Beginning yesterday after installing a set of fresh MacOS updates, Firefox is repeatedly hanging on my iMac. My computer CPU spins up and Activity Monitor tells me that the process trustd is having a field day, up to 99% CPU usage. Then Firefox stops everything and in the middle of something basic like opening a search engine page or scrolling on an already-open page, I get a spinning rainbow ball of death and have to Force Quit from the taskbar several times before it closes. Here is what I have tried to resolve: * Deleting and reinstalling * Troubleshooting mode * Downgrading to version 93.0 * Stopping and restarting the trustd process from both Activity Monitor and from Terminal * Full deletion of all Firefox files from command line and installing 96.0.2. The same problem keeps recurring. For reference, it's on a 2020 iMac running macOS Catalina (10.15.7), i9/16GB. My other machines are not affected. I have not yet upgraded to Big Sur or Monterrey on advice of workplace sysadmin. Is anyone else seeing this issue with trustd? I am not seeing this problem with other software, just Firefox, but I can't figure out when Firefox calls trustd and what it asks it to do when it does. Advice warmly welcome.

All Replies (3)

more options

Hey there!

See the following website on what to do to fix the performance issue:

https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-or-cpu-resources

Hope I helped!

Kind regards,

Bithiah

Helpful?

more options

Thanks, Bithiah! I just resolved the problem with reference to an old Apple discussion thread where the user was having the same problem with trustd - provoked by some issue with the keychain: https://discussions.apple.com/thread/8070027

I deleted just the keychain file that was relevant to Firefox in the Keychain manager but it didn't do anything. When I removed /Library/Keychains/System.keychain, the Firefox problem is resolved and everything loads properly. I suppose something got corrupted in my keychain along the way. That said, I also removed content-prefs.sqlite just now just in case. (This is after a clean install etc.)

Hopefully this is helpful for the next person who has this issue! I appreciate your help too!

Helpful?

more options

That was very good work. Well Done. Please flag your last post as Solved Problem as this can help others with similar problems. Go to that post and click the 'Solved' button to its right.

Helpful?

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.