New: Ultimaker Cura 3.5

[ahoeben 1,948]

Marketplace should have an updated OctoPrint plugin.

[Adam324 13]

Thanks.  I didn't wait long enough the first time.  It only showed uninstall but after a few seconds it shows update.  I saw uninstall only the first time and just exited the window before update appeared.  It will be interesting to see if the memory issue comes back.

[ahoeben 1,948]

8 hours ago, Adam324 said:

It will be interesting to see if the memory issue comes back.

 

The memory issue that I reproduced is fixed, in both 3.5 and 3.6 (the new version of the OctoPrint plugin is compatible with both). But there could be another (or a new) leak that I don’t yet know about, so please test and let me know.

[Adam324 13]

Cura crashed yesterday night likely from memory issue.

 

I did another test today and found out where memory starts climbing about 2MBytes in both private and commit memory until it consumes all memory.  I created a manual Cura.DMP crash dump file (using task manager) before I quit the app if you want it.  If you have a way to look at the crash dump, you might be able to see what memory is leaking.  If you want the Cura.DMP file let me know.  It is 2.7 GBytes and 1.8 GBytes in a compressed .zip file.

 

Cura 3.6 beta with octoprint plugin enabled but with video/pic disabled so that it doesn't show video.

 

Memory values are shown in MBytes

Time   Memory private/commit  Description
9:25am 407/666 MBytes First launch
9:27am 406/665 Loaded large Snake https://www.thingiverse.com/thing:1776785
9:28am 407/665 Sliced
9:30am 407/655 added post processing Pause at height (Octoprint) after layer 5 and sliced
9:31am 418/547 added post processing Pause at height (Octoprint) after layer 46 and sliced
9:44am 409/536 was sitting idle from 9:31am
9:45am 420/545 After sent/print to octoprint (Now in Monitor view)
9:55am 417/550 No interaction and sitting at Monitor view since 9:45am
12:12pm 142/633 No interaction and still sitting at Monitor view since 9:45am
1:28pm 164/700 No interaction and still sitting at Monitor view since 9:45am
1:35pm Switched to Prepare view (nothing else was done)
---- memory starts climbing about 2MBytes/sec from here in both private and commit memory
1:38pm 598/1050 3 minutes After I switched to prepare view
1:41pm 905/1425 6 minutes After I switched to prepare view
1:43pm 1232/1772 8 minutes After I switched to prepare view
1:45pm 1535/2070 10 minutes After I switched to prepare view
1:47pm 1720/2260 12 minutes After I switched to prepare view
---- Still continuing... it seem like it would keep going eventually consume all memory
---- I created a manual cura.dmp
---- Quit the app

 

Edited November 3, 2018 by Adam324

[Smithy 1,144]

Thanks for the deep analyses, I hope this helps the developers to find the leak.

 

I don't know the code, but I think Cura must do something on a regular basis and this function/process causes the memory leak. So I was asking me what this could be? The only function could be a regular request to the printers, asking for their status. Maybe this is also done regardless if you are on the monitoring page or not. So another test would be great with a network disconnected pc after you sent your job to the printer. 

 

I think in the direction, that if Cura cannot ask the printers because of the disconnected network, that the process/function which is probably the reason for the leak, will not start fully, stops or throws an exception. If memory is then stable, it should be clearer which part of Cura causes the leak.

[Adam324 13]

It is seems to be communicating with the printer through Octoprint.  I can send another print when this is happening based on previous experience and the printer status updated when the print was done.  I haven’t recorded memory usage for that scenario though.