surepy / tf2_bot_detector

A handy little tool to gather, keep track and automatically votekick bots and bad actors in Team Fortress 2.
MIT License
61 stars 8 forks source link

[BUG] High CPU usage when the app is open #44

Open kamild1996 opened 1 day ago

kamild1996 commented 1 day ago

Describe the bug When the application is open, its CPU usage hovers at around 15% - while it doesn't sound like much, it's enough to cause severe in-game stutters when my game's framerate goes below the FPS cap. Closing TF2BD solves the stuttering issue entirely. What I've tried:

To Reproduce Simply open the app. Even without TF2 open, the CPU usage is already present, and seems to slightly increase even more when the game is open and TF2BD connects to it.

Expected behavior The CPU usage of the app is much smaller.

Logs debug_report.zip

Screenshots image image

Desktop (please complete the following information):

Additional context Unfortunately I'm not sure whether or not this problem is new or not. I've never noticed the app's CPU usage when playing on a 144 Hz monitor, but after upgrading to a 280 Hz one and seeing my stuttering issues when my FPS goes as far as a few frames below that cap, I started seeking answers, and closing TF2BD turned out to be the answer.

surepy commented 1 day ago

interesting, might have to look into the profiler again...

do you know what ur cpu usage was when it was the 144hz monitor or was it the same

realistically it should be like this:
image

p.s.
Disabling my antivirus software wtf don't do that ever

kamild1996 commented 20 hours ago

do you know what ur cpu usage was when it was the 144hz monitor or was it the same

Unfortunately I have no clue, I never checked the app's CPU usage before since I never really had performance issues before. But if I set my current monitor to 144 Hz, the CPU usage remains the same, so I'd wager I have had this problem for an unknown amount of time, it just never had a chance to bother me.

p.s. Disabling my antivirus software wtf don't do that ever

I know, it's just a troubleshooting step - especially since I don't use Defender like most people do.