Jump to content
maht

Now available: Ultimaker Cura 3.6 | Stable

Recommended Posts

Posted · Now available: Ultimaker Cura 3.6 | Stable

Hi,

Since installing Cura 3.6 I have found that it has a very large memory leak, I have disabled all plugins excepy octoprint and auto orientation, and I am find that after a print memory usage keeps going up until my PC (Windows 10) becomes unresponsive.

Cura using about 8gig of RAM.

Was previously using 3.5.1 and have never had this issue with Cura before.

 

Any Ideas

 

Thanks

 

Steve

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable
13 hours ago, BrianTheCookie said:

I understand that you guys are trying to optimize the print one at a time function for the Ultimaker, but other 3D printers, especially those that have a moving Y plate can do much more if this function is given more options and less boundaries and safety offsets.

1

It's up to the manufacturers of those machines to contribute these kinds of improvements back to us (or hope that an open source contributor does it for them)

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable
9 hours ago, 7s7 said:

Since installing Cura 3.6 I have found that it has a very large memory leak,

 

Could you test if this version of the plugin still exhibits the leak when you configure it not to display the camera image?
http://files.fieldofview.com/cura/OctoPrintPlugin-v5.0.0-2018-11-14T21_29_30Z.curapackage
Just drop the downloaded file into a running Cura window, and restart Cura.

 

I don't think this version will fix the memory leak (though it might), but it will help diagnose where/what is leaking. Version 3.5.2 of the plugin (which I think you have installed) has a bug that even when not displaying the image, it is still being streamed and interpreted (oops).

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable
16 hours ago, leliep said:

 

Similar for me. On my 2018 MacBook Pro it takes about 2...3 minutes to start up, using 100% CPU. During this time it displays "updating configuration", before it eventually shows the GUI and becomes responsible. This behavior is reproducible. I guess Cura 3.6 needs some kind of serious tuning 😉

 

Btw., I like the Gyroid infill!

 

 

1300232686_Bildschirmfoto2018-11-15um23_41_25.thumb.png.701f8bd8217023ece1242c2f3d3d6345.png

 

1259988939_Bildschirmfoto2018-11-15um23_41_44.thumb.png.c5f2e52be295b0c5600935c847e1a17a.png

 

 

I can confirm, cura starting from 3.5 version is unusable on macbook air 2011.

I just installed the 3.4.1 version and it's a lot better. Normal cpu usage during slicing and rotating view specially in layer view.

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable

On a Macbook Pro 2018 it is running fine with latest MacOS 10.14.1.

I guess it is related to some libraries which are too old in older MacOS versions.

Share this post


Link to post
Share on other sites
Posted (edited) · Now available: Ultimaker Cura 3.6 | Stable
30 minutes ago, Smithy said:

On a Macbook Pro 2018 it is running fine with latest MacOS 10.14.1.

I guess it is related to some libraries which are too old in older MacOS versions.

 

This is mine... brand new and up-to-date. And Cura 3.5x did run perfectly.

 

45949763_Bildschirmfoto2018-11-16um21_31_59.thumb.png.728e5b67f795353308e1c83f849b29da.png

Edited by leliep

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable

In my case I just installed osx high sierra. All other slicers are working fine (S3d, idea maker, Slic3r PE etc.) 

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable

What about this for a slow startup on MacOS...?

 

UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version:

 

~/Library/Application\ Support/cura/3.6/cura.log contains an endless number of lines with this kind of messages.

 

 

2018-11-15 22:53:20,838 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [422]: Loaded plugin FileLogger

2018-11-15 22:53:20,849 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [422]: Loaded plugin LegacyProfileReader

2018-11-15 22:53:20,860 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [422]: Loaded plugin SimpleView

2018-11-15 22:53:20,873 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [422]: Loaded plugin SolidView

2018-11-15 22:53:20,891 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [422]: Loaded plugin FirmwareUpdateChecker

2018-11-15 22:53:20,907 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [422]: Loaded plugin SupportEraser

2018-11-15 22:53:20,919 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [422]: Loaded plugin PrepareStage

2018-11-15 22:53:20,950 - DEBUG - [MainThread] UM.Backend.Backend._logSocketState [178]: Socket state changed to Listening

2018-11-15 22:53:20,979 - INFO - [MainThread] UM.Backend.Backend.startEngine [74]: Started engine process: /Applications/Ultimaker Cura.app/Contents/MacOS/CuraEngine

2018-11-15 22:53:20,983 - DEBUG - [MainThread] UM.Backend.Backend._backendLog [94]: [Backend] Calling engine with: ['/Applications/Ultimaker Cura.app/Contents/MacOS/CuraEngine', 'connect', '127.0.0.1:49674', '']

2018-11-15 22:53:20,987 - DEBUG - [Thread-18] UM.Backend.Backend._backendLog [94]: [Backend]

2018-11-15 22:53:20,997 - DEBUG - [Thread-18] UM.Backend.Backend._backendLog [94]: [Backend] Cura_SteamEngine version 3.6.0

2018-11-15 22:53:20,997 - DEBUG - [MainThread] UM.Backend.Backend._logSocketState [182]: Socket state changed to Connected

2018-11-15 22:53:21,000 - DEBUG - [Thread-18] UM.Backend.Backend._backendLog [94]: [Backend] Copyright (C) 2018 Ultimaker

2018-11-15 22:53:21,008 - DEBUG - [Thread-18] UM.Backend.Backend._backendLog [94]: [Backend]

2018-11-15 22:53:21,008 - DEBUG - [MainThread] UM.Backend.Backend._onSocketStateChanged [172]: Backend connected on port 49674

2018-11-15 22:53:21,011 - DEBUG - [Thread-18] UM.Backend.Backend._backendLog [94]: [Backend] This program is free software: you can redistribute it and/or modify

2018-11-15 22:53:21,016 - DEBUG - [Thread-18] UM.Backend.Backend._backendLog [94]: [Backend] it under the terms of the GNU Affero General Public License as published by

2018-11-15 22:53:21,021 - DEBUG - [Thread-18] UM.Backend.Backend._backendLog [94]: [Backend] the Free Software Foundation, either version 3 of the License, or

2018-11-15 22:53:21,028 - DEBUG - [Thread-18] UM.Backend.Backend._backendLog [94]: [Backend] (at your option) any later version.

2018-11-15 22:53:21,029 - INFO - [MainThread] UM.VersionUpgradeManager.upgrade [130]: Looking for old configuration files to upgrade.

2018-11-15 22:53:21,032 - DEBUG - [Thread-18] UM.Backend.Backend._backendLog [94]: [Backend]

2018-11-15 22:53:21,036 - DEBUG - [Thread-18] UM.Backend.Backend._backendLog [94]: [Backend] This program is distributed in the hope that it will be useful,

2018-11-15 22:53:21,039 - DEBUG - [Thread-18] UM.Backend.Backend._backendLog [94]: [Backend] but WITHOUT ANY WARRANTY; without even the implied warranty of

2018-11-15 22:53:21,043 - DEBUG - [Thread-18] UM.Backend.Backend._backendLog [94]: [Backend] MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the

2018-11-15 22:53:21,046 - DEBUG - [Thread-18] UM.Backend.Backend._backendLog [94]: [Backend] GNU Affero General Public License for more details.

2018-11-15 22:53:21,050 - DEBUG - [Thread-18] UM.Backend.Backend._backendLog [94]: [Backend]

2018-11-15 22:53:21,054 - DEBUG - [Thread-18] UM.Backend.Backend._backendLog [94]: [Backend] You should have received a copy of the GNU Affero General Public License

2018-11-15 22:53:21,058 - DEBUG - [Thread-18] UM.Backend.Backend._backendLog [94]: [Backend] along with this program.  If not, see <http://www.gnu.org/licenses/>.

2018-11-15 22:53:21,088 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: ./.DS_Store, skip it

2018-11-15 22:53:21,091 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: ./packages.json, skip it

2018-11-15 22:53:21,093 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: ./plugins.json, skip it

2018-11-15 22:53:21,097 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/.DS_Store, skip it

2018-11-15 22:53:21,101 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/plugins.json, skip it

2018-11-15 22:53:21,103 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/.DS_Store, skip it

2018-11-15 22:53:21,105 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/definitions/3.3.1/ultimaker2_extended, skip it

2018-11-15 22:53:21,108 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/definitions/3.3.1/ultimaker3_extended, skip it

2018-11-15 22:53:21,111 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/definitions/3.3.1/ultimaker3_extruder_left, skip it

2018-11-15 22:53:21,114 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/definitions/3.3.1/ultimaker_original, skip it

2018-11-15 22:53:21,118 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/definitions/3.3.1/fdmprinter, skip it

2018-11-15 22:53:21,122 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/definitions/3.3.1/ultimaker_s5, skip it

2018-11-15 22:53:21,125 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/definitions/3.3.1/ultimaker2, skip it

2018-11-15 22:53:21,129 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/definitions/3.3.1/ultimaker3, skip it

2018-11-15 22:53:21,132 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/definitions/3.3.1/ultimaker2_extended_plus, skip it

2018-11-15 22:53:21,136 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/definitions/3.3.1/ultimaker2_go, skip it

2018-11-15 22:53:21,139 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/definitions/3.3.1/ultimaker2_plus, skip it

2018-11-15 22:53:21,142 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/definitions/3.3.1/ultimaker3_extruder_right, skip it

2018-11-15 22:53:21,146 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/definitions/3.3.1/imade3d_jellybox, skip it

2018-11-15 22:53:21,149 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/definitions/3.3.0/ultimaker3_extruder_left, skip it

2018-11-15 22:53:21,152 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/definitions/3.3.0/ultimaker3_extruder_right, skip it

2018-11-15 22:53:21,155 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/definitions/3.3.0-BETA/ultimaker3_extruder_left, skip it

2018-11-15 22:53:21,158 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/cache/definitions/3.3.0-BETA/ultimaker3_extruder_right, skip it

2018-11-15 22:53:21,161 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/quality/.DS_Store, skip it

2018-11-15 22:53:21,166 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/3.2/cache/definitions/3.2.1/ultimaker2_extended, skip it

2018-11-15 22:53:21,169 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/3.2/cache/definitions/3.2.1/ultimaker3_extended, skip it

2018-11-15 22:53:21,172 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/3.2/cache/definitions/3.2.1/cartesio, skip it

2018-11-15 22:53:21,175 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/3.2/cache/definitions/3.2.1/ultimaker3_extruder_left, skip it

2018-11-15 22:53:21,179 - WARNING - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [281]: Failed to get file version: 3.3/3.2/cache/definitions/3.2.1/ultimaker_original, skip it

2018-11-15 22:53:21,182 - WARNING - [MainTh...

 

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable
1 hour ago, leliep said:

This is mine... brand new and up-to-date. And Cura 3.5x did run perfectly.

 

I don't know, but 3.6 is staring as fast (or slow) as all other previous versions. Cura isn't the fastest app when starting, but it takes no longer than 10 seconds.

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable
5 minutes ago, Smithy said:

 

I don't know, but 3.6 is staring as fast (or slow) as all other previous versions. Cura isn't the fastest app when starting, but it takes no longer than 10 seconds.

 

For me it takes 184 seconds.

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable

Definitely too long.

 

You could try to delete Cura and delete everything in your <home>/Library/Application Support/cura 

But make a backup before if you have a lot of customizations (profiles, materials, etc)

Then try again with a fresh copy of Cura 3.6. I guess that there is a problem converting the older configurations which are all stored in the above location.

  • Like 1

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable

Anyone else find that when gyroid infill is used that the time to print in cura is way out from real life? (Using Ultimaker S5 to print) In Cura it said 14 hours 12min, but real world was 19 hours 37 min what i find to be way way out next to using one of the normal infills i used before 3.6

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable

Hello @Carla_Birch. Yes, I noticed that the gyroid infill appears to take longer to print than the estimated time. Sorry, I don't know why that is. My guess is that there is a mismatch between the values that Cura is using to calculate the time (distances, acceleration, jerk values, etc.) and the values used by the printer firmware. The gyroid infill gcode does not add any explicit delays or require much travel.

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable
On 11/15/2018 at 3:34 PM, BrianTheCookie said:

@maht {snip}

One more change I would like to suggest would be to reinstate the filament diameter option in the sidebar. This will allow users to easily adjust flow if a particular spool of filament is over or under spec. Thank you.

I second this. Please put it back in - that would help a lot on my end.

 

Thank you,

 

Gary

--

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable
On 11/16/2018 at 9:59 PM, ahoeben said:

 

Could you test if this version of the plugin still exhibits the leak when you configure it not to display the camera image?
http://files.fieldofview.com/cura/OctoPrintPlugin-v5.0.0-2018-11-14T21_29_30Z.curapackage
Just drop the downloaded file into a running Cura window, and restart Cura.

 

I don't think this version will fix the memory leak (though it might), but it will help diagnose where/what is leaking. Version 3.5.2 of the plugin (which I think you have installed) has a bug that even when not displaying the image, it is still being streamed and interpreted (oops).

Thank you, I will test and see

 

Steve

Share this post


Link to post
Share on other sites
Posted (edited) · Now available: Ultimaker Cura 3.6 | Stable
On 11/16/2018 at 5:35 PM, Smithy said:

[...] Then try again with a fresh copy of Cura 3.6. I guess that there is a problem converting the older configurations which are all stored in the above location.

 

FWIW: Loading Cura 3.6.0 on a MacBook Air 2014 with 1.7GHz i7 8GB RAM and SSHD running 10.14.1 Mojave takes about 14 seconds. This is an install over 3.5.1 with a couple of printer profiles customized.

Edited by bobstro

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable

14 seconds sounds ok, mine needs 10 seconds to start, so depending on the profiles it could take 4 seconds longer.

Share this post


Link to post
Share on other sites
Posted (edited) · Now available: Ultimaker Cura 3.6 | Stable

The problem for me is after program charging. Any click on GUI halt cura for at least 7/10 seconds Each time. Then layer view is almost unresponsive. 🤐

What happened after 3.4.1? That is the last version that is working fine

I saw that development moved to a newer version of QT. Could this be the problem? 

 

Edited by pieri70

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable

Cura 3.6 seems to print support brims before it starts printing the normal skirt. This way, if there is some residue on the nozzle, it's not on the skirt but instead get's wiped on the brim, which is bad.

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable
1 hour ago, pieri70 said:

I saw that development moved to a newer version of QT. Could this be the problem? 

I guess it is, but there were also some problems before. For example, the custom settings after you enter something in the search field, the items are shown only after some seconds and then only one by one.

 

I think it is a mix of new Cura version with some changes in the libraries and Apple changes some default libraries too.

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable

The problem was with both mac os el capitain and high sierra.

So I think much of the problems are by cura itself..

It's a pity.

I'll get stuck with Idea Maker

Thanks

Pietro

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable

I have such problems always when the application is available for multiple platforms. It works but it is not as fast as native apps and there is always a very little delay in using the gui. Native MacOS apps don't rely on these libraries I guess and therefore they are much faster and more responsive. When I look back, there were a lot of Java apps, all for several platforms available and they were all slow and sometimes unresponsive. Cura frontend is written in Python but I think it relies also on those shared libraries for generating, viewing the gui elements and windows.

 

For me it is usable, not fast as a native app, but not so slow that I can say, I cannot use it. And nothing has changed for me between 3.4.1 and 3.6., speed (starting, using) is/was always the same.

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable

System specs for you? 

I'll try with my sister macbook air as she will come and see me. It's last year model.. 

 

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable

I guess a dedicated graphics card is a lot better than the built-in Intel chip. Most Macbooks don't have dedicated graphics, only the 15" Pros or if you order it.

 

Here is mine, also without a dedicated graphic card.

2000536581_Bildschirmfoto2018-11-18um19_15_38.thumb.png.863f87b884d6bda82cb839ee3f279a9b.png

 

And it has nothing to do with memory because at my office I have an iMac 2017 i5 with 24GB memory and speed is the same there.

Share this post


Link to post
Share on other sites
Posted · Now available: Ultimaker Cura 3.6 | Stable

Hi, I am quite new to this, have an Ender 3 printer. 
Now, when first beginning a print, the extruder heater will not start to heat up until the bed has fully heated up. It was not like this on Cura 3.5.1  where both extruder heater and bed heater started up together and reached final temperature pretty much together. Makes a difference in my cold basement. Can 3.6 be made to work like 3.5.1 ?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Our picks

    • Ultimaker Cura 4.0 | Stable available!
      Ultimaker Cura 4.0 is mainly focused on the improved user interface and cloud integration.
      As always, we want to collect your user feedback for this release. If there are any improvements you can think of, feel free to mention it here and help us to shape the next release.
      • 98 replies
×
×
  • Create New...

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!