-
Notifications
You must be signed in to change notification settings - Fork 76
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
HIDHide Watchdog taking up large amounts of RAM #126
Comments
Uh oh. Do you have a relative feeling how long it ran until you noticed? What was the amount, roughly? Oh, a few hundred megs, yeah that is not normal indeed 😅 we're leaking somewhere. |
I actually saw it a few days ago, where it was 500MB in RAM, but I thought nothing of it and just simply terminated it. Did a few restarts from then till here cuz of drivers for some dumb camera that didn't end up working, and I decided to peek into task manager cuz something wasn't right with another program, and that's where I saw the Watchdog service at 300MB. I only booted up my PC just an hour ago so the memleak is likely fast. I've since disabled the service, since I've completely disabled Windows Update anyways, but I've re-enabled it for now and I'm just steadily watching it. |
Well, good to see that it was at least reproducible, would've been a nightmare if it was my system that caused it. |
I'll check |
Yeah the thread runs its checks every 5 seconds. |
and it's leaking even faster |
Because I changed 5 seconds to 50 milliseconds 😉 |
Yep, |
Found and fixed it! Thanks for reporting! Next release will contain the fixed version. |
nicely done, and good to hear! |
@rhobiusvoid could you test this new build pls before I make a release, thanks: HidHide_1.4.192_x64.exe.zip |
Bug description
The Watchdog service that ensures the configs are set properly between updates or system changes is taking huge proportions of RAM, upwards of 300MB.
Steps to reproduce
Actual result: Letting it run over time will just keep growing its RAM usage, likely as a result of some memory leak.
Expected result: Should just stay reasonable.
Screenshots
Would've posted one if I hadn't terminated it. Sorry.
Machine info
CPU-Architecture: x64
Windows version: Windows 10 LTSC 21H2
Software/driver version(s): Latest one, part of security bulletin, legacinated
Any other helpful information
n/a
The text was updated successfully, but these errors were encountered: