My Deploy background service was using 14.5 GB of memory yesterday. I restarted it to clear it, hoping it might be a one-time glitch. But this morning the service is already back to consuming 5.7 GB. Has anybody else seen this kind of thing?
For context, I recently moved our free version database from a shared server to my local workstation, as I'm now the only person who uses Deploy. My machine also has a Central Server client of PDQ Inventory. Whether these are related, I'm not sure.
A similar item is listed at https://support.pdq.com/hc/en-us/community/posts/211688527-High-Memory-Usage-and-Memory-Leak with some recent activity, but my issue is with everything sitting idle.
There's not much in the event log, but there was one entry that seemed a little odd:
Thread was being aborted.
Now: 1/4/2018 2:59:28 PM
started: 1/4/2018 2:51:54 PM
HResult: 0x0030 (19)
at AdminArsenal.Service.ServiceThread.TimerElapsed(Object sender, ElapsedEventArgs e)
It seems like this thread was stuck. Even though I wasn't running the console the background service was testing the repository files. Maybe that's normal, but since the DB recently changed machines it may not be happy with how some/many of the file moved around.