-
Notifications
You must be signed in to change notification settings - Fork 93
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
- I have searched open and closed issues for duplicates
- I am submitting a bug report for existing functionality that does not work as intended
- I have read the project documentation and not found a solution to my problem there
- This isn't a feature request or a discussion topic
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
- Unsure how to reproduce this, or what the actual environment for it is, but the watchdog service just seems to keep growing in RAM usage until the user notices and terminates it, letting it start over again.
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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working