Jump to content
Ultimaker Community of 3D Printing Experts

Cura 4.3.0 memory/resource leak


Recommended Posts

Posted · Cura 4.3.0 memory/resource leak

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.

  • Link to post
    Share on other sites
    Posted · Cura 4.3.0 memory/resource leak

    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.

  • Link to post
    Share on other sites
    Posted · Cura 4.3.0 memory/resource leak
    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?

  • Link to post
    Share on other sites
    Posted · Cura 4.3.0 memory/resource leak

    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.

  • Link to post
    Share on other sites
    Posted · Cura 4.3.0 memory/resource leak

    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

  • Link to post
    Share on other sites
    Posted · Cura 4.3.0 memory/resource leak

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

  • Link to post
    Share on other sites
    Posted · Cura 4.3.0 memory/resource leak
    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?

  • Link to post
    Share on other sites
    Posted · Cura 4.3.0 memory/resource leak

    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.

  • Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    • Our picks

      • Ultimaker Transformation Summit

        On April 20 - April 23 we will host the Ultimaker Transformation Summit. Come talk to us via Live chat and get inspired by any of our relevant presentations!
        • 5 replies
      • New here? Register your Ultimaker for free 3D printer onboarding course
        Hi,
         
        Often getting started is the most difficult part of any process. A good start sets you up for success and saves you time and energy that could be spent elsewhere. That is why we have a onboarding course ready for
        Ultimaker S5 Pro Bundle, Ultimaker S5, Ultimaker S3 Ultimaker 2+ Connect.   
        They're ready for you on the Ultimaker Academy platform. All you need to do to gain access is to register your product to gain free access. 
        Ready? Register your product here in just 60 seconds.
          • Like
        • 0 replies
    ×
    ×
    • Create New...