Anyone else seen this with Cura ? Those were 4 stuck processes,

3D Printing
, , ,
1

Anyone else seen this with Cura ? Those were 4 stuck processes, Cura was not even “running”…

847e830d390890fe33e7f193d75f58f2.jpeg

2

Wats that mean?

3

Means that Cura processes got stuck (zombie processes) and they were taking all of my CPU even after I had quit Cura.

4

@Elly_May_Clampett If you don’t know what the question means, it’s doubtful you can help. Doubly so if you can’t spell.

@Andre_Courchesne1 For what it’s worth, I haven’t seen that behaviour with Cura. (I have, however, noticed that MatterControl seems to eat up a lot more system resources, even when not actively doing anything.) What version of Cura are you running?

5

@Patrick_Ryan Running Cure 14.09 under OSX Yosemite

6

@Andre_Courchesne1 Can you replicate it? Does it happen every time you quit Cura? I just checked 14.09 on machines running Mavericks and Yosemite, and neither one is doing it for me.

7

FYI it seems to happen only after a print. If I start Cura and close it, no remaining processes. If I start Cura, do a print and quit it, I’m left with a task running.

Andres-MacBook-Pro:~ courchea$ ps aux | grep -i cura
courchea 82150 100.0 0.5 2564420 39116 ?? R 8:19am 1:26.20 /Applications/Cura/Cura.app/Contents/MacOS/Cura --serialCommunication /dev/cu.usbmodem1a1211:AUTO

I have to do a ‘kill -s SIGKILL’ on the task to kill it.

8

An other thing I noticed with Cura is if you cancel a print it will not turn off the hotend…
I looked at the Github Cura project and issues resolution seems low (122 issues open…)

9

I don’t think I’ve ever used Cura to do a print directly - I usually use it to slice, then use Repetier to print the gcode. (I like Cura for its support generation, which is why I use it as an external slicer. Though I’ve been playing with MatterControl just recently, as a possible all-in-one solution.) I’ll give it a try and see what happens.

10

@Patrick_Ryan Did not know about MatterControl. I’ll give it a shot. I also like the Cura slicer better.
Used to print via OctoPrint/OctoPi but my Pi is currently used for an other project right now. I saw that the latest OctoPrint version had incorporated the Cura slicer I think.

11

Well, that’s interesting. Cura works fine on my dedicated 3D printing machine, running Mavericks. It printed fine, then quit out OK, leaving no processes behind. It seems completely broken on my daily-use machine, running Yosemite - loaded models don’t display at all, no option to save gcode or print. Dunno whether that’s new since Yosemite, or whether it was broken before, because I don’t use this machine for 3D printing much/at all any more. It does kill all its processes, though…

I dunno - seems to me that, as you point out, Cura doesn’t seem to be getting a lot of its outstanding issues resolved. It wouldn’t surprise me if Yosemite broke it completely.

12

Looks like it forgot to set daemon more on some threads. So you exit the ui cura us still running because threads have hung and not being daemon prevents the app from eciting. Setting them to daemon in cura would at least ensure a clean exit though not necessarily fix the underlying issue

13

It’s not just yosemite, mavericks also has the issue. I’ve been working on that issue, because it will also prevent the computer from going completely to sleep. It’s hard. Your process list definitely helps, thank you.

14

@Justin_Nesselrotte Anything I can do to help let me know. I seem to be able to reproduce it as will.