3.7.3-DEV on 5.2.1?

[St-Aris]

Tried installing this to resolve memory leak issues - but it does not install. Should it work on 5.2.1 - installer I used was listed as 5.0.

Thanks,

[fieldOfView]

How did you try installing it, and can you elaborate on "it does not install"?
The 5.0 curapackage should work on Cura 5.0 and newer.

[St-Aris]

I wasn't exactly testing for this specifically - just messing around and noticed. I will try this again tomorrow and look more closely.

When I go into the dialog it does say 'Checking the API key' - so it must be doing something. Having restarted Cura - it falls back to about 450MB memory use with a model loaded in and sliced. When I go to preview, it jumps to about 530MB - and if I go to monitor, about 536MB.

Are you unable to reproduce this yourself?

[fieldOfView]

Opening the dialog will destroy and recreate the zeroconf object if discovery is enabled, but it should not exist in the first place with the "Automatically discover local OctoPrint instances" box unchecked.

Are you unable to reproduce this yourself?

In all honesty, I never leave Cura open long enough to notice. In addition, I don't use printers connected via OctoPrint myself much lately; I hope that will change again in the future.

[fieldOfView]

The last time I investigated a memory leak that was not caused by zeroconf, it turned out the memory was leaking somewhere in Qt. This makes things hard to debug:
#88 (comment)

What could be happening is that there's a leak in the network calls I make periodically to get the state of OctoPrint.

I'll try to make some time to see if I can reproduce the leak.

[St-Aris]

Let me know if there are any further tests you may find helpful for me to try.

Microsoft SDK provides a utility called UMDH - I could potentially figure it out and capture some memory usage info - but I suspect it might be better if someone familiar with the underlying code did that.

[St-Aris]

Playing around some more. Longer you leave it, the more it leaks. Sometimes it releases the memory - sometimes not (I have to restart to release memory).

[St-Aris]

Hope you are still interesting in what i'm seeing - if not, let me know.

Left it on for several days - it went to about 3GB. I went to the octoprint menu and clicked on 'connect to octoprint' and it suddenly cleared the memory down to 500mb. I did this again several days later when it went to about 2.2gb - and I was unable to clear the excess memory like this again. What I did see though was that while I could print from cura directly to octoprint - the monitor page on cura did not show any live information about the print as it usually does. I restarted, and then this worked again. I can't quite pinpoint what is going on and reliably reproduce any of these scenarios - it is just general weirdness. Hope this helps.

[St-Aris]

I note there is a new release which fixes some memory leaks - this particular memory leak is still present though.

[fieldOfView]

Good to know. The recent update was mostly the same as the 3.7.3-DEV you tested.
I have not had much time to further investigate this, but it is on my todo-list.

[St-Aris]

Great - thanks for the update. If you need any further info or repro/debug info - just comment on this thread and i'll do my best to help.