Memory leak with PerformanceCounter about thetis HOT 10 CLOSED

Cannot confirm. Thetis x64 running on WIN7 SP1 for several hours on "thetis only" without observable increase on mem usuage.

from thetis.

Cannot confirm. Thetis x64 running on WIN7 SP1 for several hours on "thetis only" without observable increase on mem usuage.

this only happens when using process filtered PerformaceCounters, such as the Thetis Only option in the status bar. It has been temporarily removed until a fix is found. It does however seem to be a .net/core issue, so may not get fix in the short term. System cpu% is fine, which uses the _Total performance counter.

Richie.

from thetis.

this only happens when using process filtered PerformaceCounters, such as the Thetis Only option in the status bar. It has been temporarily removed until a fix is found. It does however seem to be a .net/core issue, so may not get fix in the short term. System cpu% is fine, which uses the _Total performance counter.

Yes, i have recompiled with reverted changes and run with "Thetis only" option. (VS2019, target x64 release)

Walter.

from thetis.

Yes, i have recompiled with reverted changes and run with "Thetis only" option. (VS2019, target x64 release)

Walter.

I ran it for about 6 hours, and noticed a gradual increase. Without it there is no gradual increase. I also noticed that memory use increases quite fast and then GC's back down again, but I feel there is perhaps something left over. If you set the CPU Meter (ms) in setup-Display-General to 100ms you can see this happen quite fast. It is probably best left out for now until there is more investigation on what is actually happening.

Richie.

from thetis.

hmm, I wonder if it is a windows 11 issue? At the moment the memory profiler is broken in vs2022.

from thetis.

On WIN8.1 it looks exactly the same.
But it resets every time to the same value, no long term increase. Maybe the sawtooth is just a garbage collection effekt.

Just testing WIN7...

Edit: The 8.1 test was on QRL with an older build of thetis.
At home, WIN7 and self compiled thetis there is no sawtooth, Private Bytes stable at 748.6MB !

from thetis.

It is over 100MB of GC'ed just for a processcounter which is somewhat nasty. I have looked at the .net source but didn't really spot anything obvious. It doesn't really hinder much atm as there are so many other apps to check cpu usage of the process.

from thetis.

The 8.1 test was on QRL with an older build of thetis.
At home, WIN7 and self compiled thetis there is no sawtooth, Private Bytes stable at 748.6MB !

from thetis.

It has to be a later windows issue in that case Walter. I will spend some time investigating that at some point, but low down on priority atm. At least you can get it working your end if you want to use the feature. Cheers, Richie.

from thetis.

re-enabled in latest releases. Think this is a non issue now. We can re-open if needed.

from thetis.