02-24-2023 03:33 PM
Checked with colleagues involved and they knew of a RoCo memory leak (internal bug 2242225) that is not addressed yet. But they did not know of customers running into it out in the wild. Now they do. I don't have an ETA for a fix unfortunately.
02-24-2023 03:44 PM
Very interesting, is there anything you can think of that may be a quick fix or to help mitigate the effects while waiting for a proper fix? Thank you again for all your help!
02-27-2023 11:04 AM - edited 02-27-2023 11:04 AM
If possible in your particular circumstances, and when your application isn't running, use a Command Prompt launched as Administrator and run:
net stop niroco
net start niroco
Let me know if this helps!