An update, its been 3 hours 20 minutes. With the polling at 1 minute for the ObserverIP memory is at 8.4 which is completely reasonable. Ill keep letting it run, but more and more wondering if the issue was the prior request wasn't complete when the next one fired at 16 seconds which somehow caused the leak. Will update later tonight or tomorrow based on how much memory uses changes.
Also thank you for responding so quickly, always great when an author hops on issues like this asap! (especially during the holidays).
Also thank you for responding so quickly, always great when an author hops on issues like this asap! (especially during the holidays).
Comment