OverSightXPC peaks CPU usage on 11.3
8times4 opened this issue · comments
Hey there,
Since MacOS 11.3 update, OverSightXPC process seems to use around 70% cpu on multiple threads. CPU temp also hovers between 80-99 celsius with fans ramping up every minute above 4500 rpm.
OverSight 1.20 on Intel MBP 2018 15' base model.
Quitting OverSight allows the Mac to go silent with 2000 rpm.
Thanks,
Mark
Same here.
Can confirm, also starts to use up all RAM and running into swap after a while.
I have the same issue
Same issue on a 2018 Macbook Air
Same issue here.
Same here on 11.3 since the latest security update. Consumes 40GB of RAM and 100% CPU. (Intel CPU).
Same issue. macOS 11.3 and OverSight v 1.2.0. RAM maxing out and CPU spiking to 60%.
Yep, same here. The XPC is at 50 to 60% CPU, and the helper at 6 to 7%. In my case I noticed this when recording mp3 with ffmpeg using an Automator workflow.
(2018 Intel MBP i9)
Not sure what (yet), but clearly something in macOS 11.3 triggering an issue/bug in OverSight. Sorry! 😥
Digging into cause and will push out fix ASAP! Mahalo for your patience.
Hi, just to confirm that after update to 11.3 indeed the app becomes hell:
Glad I'm not the only one! Took me a bit to find out why the latest update was causing massive battery drain and sluggish performance but once I saw this running so high I investigated.
ok, beta with fix (and lots of other improvements!)
https://github.com/objective-see/OverSight/releases/tag/v2.0.0_beta
...note only monitors camera for now (will add microphone back in shortly).
If you like to test/report any issues, I'd be stoked!
2.0.0 runs stable so far :-)
Got Error on installation.
"May 3 20:10:43 laptop com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.system): com.objective-see.oversight.uninstallHelper (lint): Assuming EnablePressuredExit=false given EnableTransactions=false.
-Update-
After re-running installer it worked successfully although this time it said Install instead of Upgrade.
@MarcLaf, from the Terminal, can you run:
log show --predicate="subsystem='com.objective-see.oversight'"
...should provide more detailed error info. Thanks!
Ah that worked - I tried the command you had over on the main site (linked from the ? in the error message) but it just sat there.
2021-05-03 20:10:45.851457-0400 0xb2d0 Error 0x1f7ce 1784 0 com.objective-see.oversight.uninstallHelper: [com.objective-see.oversight:installer (helper)] ERROR: failed to execute config script
configure.sh (1)
Both macOS 11.3 and 11.3.1 have issues with version 1.20.0, but 2.0-beta is working without any problems so far 🚀
Thanks for the quick update! 🙌🏼
I've managed to install 2.0.0 after it having failed once, and the CPU usage is normal! 🎉
However I'm getting a warning from Little Snitch telling me the app is in translocation mode, which doesn't allow me to create permanent rules 😢. I'm launching it from the /Applications folder, so I don't understand why this is happening.
During install BlockBlock also points to a file in the app translocation folder, so perhaps that's related:
Looks really good so far. Indeed, had issue with installing it by upgrade. after uninstall it worked
Had the same overheating issue. Installed 2.0.0 beta and hopefully it fixes the heating issue.
The install went smoothly.
Fixed for me in v2.0.0 Beta 2
Might be the update checker, I did ask if that was what it was, Lulu cut off the end of the url
2.0 does fix the performance bug.
Afaik sentry.io is telemetry & bug reports, so we should allow connections, because it helps Patrick improve the software.
The "problem" in the screenshot --at least to me-- is, that due to the app running in this "App Translocation" we can't allow this request "for ever" but have to approve it with each restart of the app. Quite an annoyance.
The "problem" in the screenshot --at least to me-- is, that due to the app running in this "App Translocation" we can't allow this request "for ever" but have to approve it with each restart of the app. Quite an annoyance.
That's precisely it ☝🏼 Thank you 😄
That's weird, because the app and its installer are notarized. So there should be no translocation. You can run xattr -l /Applications/OverSight.app, and if the output says com.apple.quarantine, you should remove the XA with xattr -dr com.apple.quarantine /Applications/OverSight.app. At any rate, I have not problems on my system, i.e. no translocation.
Glad I found this thread. Current Intel based MacBook Pro on 11.3.1 with OverSight consuming 4.23GB of memory on a regular basis. Installed the 2.0.0-Beta and so far so good 👍🏻
That's weird, because the app and its installer are notarized. So there should be no translocation. You can run xattr -l /Applications/OverSight.app, and if the output says com.apple.quarantine, you should remove the XA with xattr -dr com.apple.quarantine /Applications/OverSight.app. At any rate, I have not problems on my system, i.e. no translocation.
Thanks for the tip! 🙏🏼
Mine did in fact still say com.apple.quarantine:
com.apple.quarantine: <4 digit code>;<8 digit code>;Firefox;<UUID>
Running that command cleared it. Not sure what caused this on my system though 🤷🏼
On a separate note, those already on 2.0.0-Beta - Does OverSight detect (and request) microphone access? On my system only camera access is requested (e.g. Zoom, Safari via Hangouts), which I'm finding weird 🤔
macOS Big Sur 11.3 (20E232)
MacBookPro16,1
@p4checo I'm running https://github.com/objective-see/OverSight/releases/tag/v2.0.0 and both, camera and mic access are detected. however.
I have 2 mics:
-
the internal one -> I can allow/deny the access
-
an external mic plugged in via USB -> I only get the message, that this device became active, but I can only choose "ok":
@swiknaba no luck here 😢 I only use the internal/built-in one, and it doesn't detect whether using the Mac's mic or one connected externally (e.g. apple earplugs cord mic).
Already tried erasing OverSight's preferences (com.objective-see.oversight.plist), removed all rules, still no mic detection.
EDIT: I stand corrected. I was being retarded and still using 2.0.0-Beta (didn't notice the newer builds) 🤦🏼♂️. Upgraded to v2.0.0 and audio is detected 💪🏼. After installing 2.0.0 it was no longer quarantined, so Little Snitch allowed me to create permanent rules.
Apologies for the noise 🙏🏼