Ugh :(That stupid thing again. It's one of those issues that rears it's ugly head every so often, but has proven to be a nightmare to find (and therefore fix).
Cursid Repeatedly Reoccurring Rogue Recursion Routine
Edited by GuestUgh :(That stupid thing again. It's one of those issues that rears it's ugly head every so often, but has proven to be a nightmare to find (and therefore fix).
Cursid Repeatedly Reoccurring Rogue Recursion Routine
Edited by GuestSorry to be the bearer of bad news. I've had this problem using Cura 2.4.0 a few times but I've also been using Cura 2.5B and haven't seen it in the beta yet. If it helps to know, I have Windows 7x64 and a UM3e. Are there known conditions that cause it or is it a true gremlin in the system?
Just adding my piece. I get it regularly, even with a simple 3DBenchy.
Mac OS Sierra (latest)
Cura 2.5.0-Beta
Just adding my piece. I get it regularly, even with a simple 3DBenchy.
Mac OS Sierra (latest)
Cura 2.5.0-Beta
Could you try with 2.5 final?
I'll grab it and give it a go, sure.
I get it every day in Cura 2.5.0.
Both with small objects (less than 100kb) as well as with large prints.
Extremely annoying!
I also have this problem sometimes with Cura 2.5 final on Debian Jessie. The message is:
"maximum recursion depth exceeded while calling a python object". If this error
occurred, i cannot save or open any project. After restarting Cura everything seems
fine. I played around a little bit with this issue, but unfortunately I cannot reproduce
this error clearly
Have we found a cure or fix? I just started having this problem in Cura 2.5 and I can't save any of my files because of it.
Have we found a cure or fix? I just started having this problem in Cura 2.5 and I can't save any of my files because of it.
This problem seems to have multiple causes and we have fixed all we are aware of in 2.6.0-BETA. Could you try to see if that versions works for you?
Recommended Posts
nallath 1,125
Ugh :( That stupid thing again. It's one of those issues that rears it's ugly head every so often, but has proven to be a nightmare to find (and therefore fix).
Link to post
Share on other sites