New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crashpad_handler running at 90% CPU on Mac OS #315
Comments
yep, I have it too. Killing it won't get it started again. |
Can confirm same problem when running on 10.11.6. Also noticed that the mds/mdworker metadata daemons for Spotlight were running haywire during this - probably indicating high disk output by the crashpad_handler processes - though I couldn't locate exactly what or where. |
63 is ready for testing. If this is still a problem, please report here. |
Still there... |
Could you guys report what arguments are passed into |
For reference, here's documentation for Crashpad: https://chromium.googlesource.com/crashpad/crashpad |
Quitting those two processes won't bring them back (until chromium restart) |
@tectiv3 Do those processes have any parents or children that should be noted? |
No children, parent is
|
Even better, sending them |
Hmm, well it seems none of the debugging options will be easy. Either we look through the code and patches, do a debug build/make modifications and debug at runtime, or both. I haven't worked with this area of Chromium before so I have no ideas. |
Can we just disable it all-together? |
I was thinking about it, but I'm not sure how integrated the crashpad client (or the whole client module) is in Chromium. It may not be that straight-forward to remove. That can cause some more unintended side-effects. It's an option we can take if we aren't able to fix crashpad_handler. |
Could you guys check to see if dbf4c0e changes anything? I doubt this is the cause, but I'd like to be certain. |
OK, I will try it a bit later. |
This happens on my machine too. |
@Eloston any progress on this bug? |
I have nothing to add as |
@stfnhrrs I just finished up major rework to the build system. I'm starting development on 64, so we can test again once I merge everything in. |
@stolendata nope, it refuses to build for me too. |
Patch for disabling crashpad handler on macOS Fixes #315
Patch for disabling crashpad handler on macOS Fixes ungoogled-software#315
I experienced this problem as well. I left my computer overnight to upload videos to a cloud using Google Chrome and my fans started to sound very loud to the point that they woke me up. After checking Activity Monitor, crashpad_handler was taking 199% CPU. Please see image below. How can this be troubleshooted? Thank you |
@sebvargo That process shouldn't be active. Maybe the patch is no longer valid |
@sebvargo If you experience this with 72.0.3626.109-1, please create a new issue. Thanks. |
thanks a lot.I thought my MacBook would bomb with the problem. |
apple is shit! mac is shit! crap! |
any solution ? crashpad_han running at 192 % cpu for me as well |
@krishnadamarla, are you using the current version? Try updating first if you're still on an older version. If the issue persists try a new profile: If this resolved it start migrating your settings/bookmarks etc. (always with Chromium not running) If it still persists, please open a new issue in the macOS repo. Remember to always have a backup first... |
End the process with the command: |
after ending the kernel_task from activity monitor, it fixed this situation for me |
This happened to me today, macOS Big Sur (11.1). The open files of this process suggest Visual Studio Code uses it.
I decided to reboot and, so far, it's behaving. Note: I don't have Chromium or Chrome installed. HTH |
This happened to me too. mac Big Sur (11.1). Fanning is running crazy. So Force quit "Chrome crashpad_handler" in Activity Monitor |
I've been hearing a number of applications breaking under Big Sur, so it could be a Chromium issue. Please open an issue on ungoogled-chromium-macos if this is a problem for you instead of posting on this old issue. |
Same here on Big Sur 11.2 M1 with vs code. I have Chrome installed but it was not open at that moment. I suspect vs code too. |
confirm its VScode. |
If you search for the process name chrome_crashpad_handler there are hits like this claiming its a virus. Hopefully that's just google spam? |
This is 3/2023, I just hit the same issue with M2 macbook air. I installed VS Code 2 days ago, and found the chrome_crashpad_handler process was sucking CPU and drove the CPU temperature to 180 F+. Killed it with kill -9 and now laptop is cool. |
Same issue on M1 Max with the latest vs code, kill -9 helps. |
re-spawn always, I renamed that process
|
@Leo7654 I'm not sure this issue is talking about the same "instance" of Still, in my case, I also had the CPU usage issue with the Android SDK-provided |
After installing version 62 crashpad_handler is using up to 56% cpu on two cores, causing a system wide slowdown and my fans sound like a jumbo jet taking off. Let me know what I can do to help debug.
The text was updated successfully, but these errors were encountered: