Cura 4.3.0 memory/resource leak

[Abrasive 4]

I've noticed that when I changed versions of Cura from 4.2 to 4.3 that a new problem showed up.  For context I generally leave Cura open all the time and up until now this has not been an issue. I am prototyping robot parts a lot of the time and when I get the print settings correct I will just keep Cura oepn to reduce the shance for error when swapping out the new prototype of a model to print. 

Lately if I leave Cura open for 24 hours it is using increased memory and CPU and is generally sluggish to use.  If I leave it open 48 hours it is downright annoying to use it is so slow.  Any longer and I end up closing it so clicking on things does not take forever.  I didn't screenshot any of the resource usage in my task manager but I can if needed.  I did look at task manager a few times and Cura was definitely getting out of control with CPU and memory usage.

 

Basically repro steps are:
1. Open a model in Cura.
2. Send it to the printer to print.
3. Leave Cura open for a long time .

 

I'm not actually sure steps one and two are required to reproduce, I just am always using Cura so that's the information I have to go on.

[ahoeben 1,948]

What OS do you use? Do you have any plugins installed from the Marketplace?

[Abrasive 4]

16 minutes ago, ahoeben said:

What OS do you use? Do you have any plugins installed from the Marketplace?

 

No plugins installed and I am using Windows 10 with the May 2019 update installed.

[ahoeben 1,948]

Good to hear it is not one of my plugins 😉

 

Does it make a difference if you keep the monitor tab open? Do you use it at all?

[nallath 1,120]

To be honest, we don't really test leaving Cura open for 24 hours (or longer). Actually profiling something for that long also makes it really difficult to figure out what is going wrong.

 

But anyway, I have some ideas as to what might be causing it. Do you happen to use the printer connectivity of Ultimaker printers? We're using a library there that has had some tendency of hogging resources in some conditions.

[Abrasive 4]

7 hours ago, ahoeben said:

Good to hear it is not one of my plugins 😉

 

Does it make a difference if you keep the monitor tab open? Do you use it at all?

 

I don't really use it at all as the printer is close by.

 

4 hours ago, nallath said:

To be honest, we don't really test leaving Cura open for 24 hours (or longer). Actually profiling something for that long also makes it really difficult to figure out what is going wrong.

 

But anyway, I have some ideas as to what might be causing it. Do you happen to use the printer connectivity of Ultimaker printers? We're using a library there that has had some tendency of hogging resources in some conditions.

 

I do use the printer connectivity. Have used that all along to save myself from having to use sneakernet to transfer files to the printer.  What conditions might those be?

[nallath 1,120]

We don't know yet. That's the problem 😞 Our suspicions are that it has to do with the network infrastructure, but it's one of those extremely illusive and hard to debug issues.

[Abrasive 4]

I'll disconnect Cura from the printer, close it, open a new Cura and leave it open for a day or two to see if the same symptoms occur

[nallath 1,120]

You should disable the UM3Networking plugin. I believe the automatic discovery might be the culprit.

[Abrasive 4]

18 hours ago, nallath said:

You should disable the UM3Networking plugin. I believe the automatic discovery might be the culprit.

 

Well I didn't do that, but more than 24 hours later it is still nice and snappy.  So appears to possibly be related to being connected to the printer somehow.  Does auto discovery try to do anything when you have no printers connected?  When does auto discovery try to do things?

[nallath 1,120]

The auto discovery thing is always listening for printers that are broadcasting themselves.

 

But at least now we have some idea where the issue is located.