Jump to content

Recommended Posts

Posted · All "5.X.X" versions of Cura crash a lot (OSX 12.4)

I have a little annoying problem where all versions of cura 5 and up crash a lot. The Creality slicer never does this and Cura versions below 5 dont seem to either. Any thoughts? I did once have chitubox installed, which I know can cause problems, but I got rid of it and did a fresh install of Cura for version 5.2.1 after.

 

Here's what I'm getting as an error i case anyone can lend a little insight, thanks! :

 

Traceback (most recent call last):

File "UM/Qt/Bindings/MainWindow.py", line 273, in resizeEvent

self._updateViewportGeometry(win_w, win_h)

File "UM/Qt/Bindings/MainWindow.py", line 321, in _updateViewportGeometry

view_width = round(width * self._viewport_rect.width())

ValueError: cannot convert float NaN to integer

 

Thread 0x000070001f3d4000 (most recent call first):

File "/Applications/Ultimaker-Cura.app/Contents/MacOS/share/cura/plugins/USBPrinting/USBPrinterOutputDeviceManager.py", line 88 in _updateThread

File "threading.py", line 946 in run

File "threading.py", line 1009 in _bootstrap_inner

File "threading.py", line 966 in _bootstrap

 

Thread 0x000070001e3d1000 (most recent call first):

File "/Applications/Ultimaker-Cura.app/Contents/MacOS/share/cura/plugins/RemovableDriveOutputDevice/RemovableDrivePlugin.py", line 61 in _updateThread

File "threading.py", line 946 in run

File "threading.py", line 1009 in _bootstrap_inner

File "threading.py", line 966 in _bootstrap

 

Thread 0x000070001d3ce000 (most recent call first):

File "threading.py", line 324 in wait

File "zeroconf/__init__.py", line 2534 in wait

File "zeroconf/__init__.py", line 1715 in run

File "threading.py", line 1009 in _bootstrap_inner

File "threading.py", line 966 in _bootstrap

 

Thread 0x000070001c3cb000 (most recent call first):

File "threading.py", line 324 in wait

File "threading.py", line 600 in wait

File "/Applications/Ultimaker-Cura.app/Contents/MacOS/share/cura/plugins/UM3NetworkPrinting/src/Network/ZeroConfClient.py", line 81 in _handleOnServiceChangedRequests

File "threading.py", line 946 in run

File "threading.py", line 1009 in _bootstrap_inner

File "threading.py", line 966 in _bootstrap

 

Thread 0x000070001b3c8000 (most recent call first):

File "zeroconf/__init__.py", line 1369 in run

File "threading.py", line 1009 in _bootstrap_inner

File "threading.py", line 966 in _bootstrap

 

Thread 0x000070001802a000 (most recent call first):

File "threading.py", line 320 in wait

File "threading.py", line 460 in acquire

File "UM/JobQueue.py", line 98 in _nextJob

File "UM/JobQueue.py", line 124 in run

File "threading.py", line 1009 in _bootstrap_inner

File "threading.py", line 966 in _bootstrap

 

Thread 0x0000700017027000 (most recent call first):

File "threading.py", line 320 in wait

File "threading.py", line 460 in acquire

File "UM/JobQueue.py", line 98 in _nextJob

File "UM/JobQueue.py", line 124 in run

File "threading.py", line 1009 in _bootstrap_inner

File "threading.py", line 966 in _bootstrap

 

Thread 0x0000700016024000 (most recent call first):

File "threading.py", line 320 in wait

File "threading.py", line 460 in acquire

File "UM/JobQueue.py", line 98 in _nextJob

File "UM/JobQueue.py", line 124 in run

File "threading.py", line 1009 in _bootstrap_inner

File "threading.py", line 966 in _bootstrap

 

Thread 0x0000700015021000 (most recent call first):

File "threading.py", line 320 in wait

File "threading.py", line 460 in acquire

File "UM/JobQueue.py", line 98 in _nextJob

File "UM/JobQueue.py", line 124 in run

File "threading.py", line 1009 in _bootstrap_inner

File "threading.py", line 966 in _bootstrap

 

Thread 0x000070001401e000 (most recent call first):

File "threading.py", line 320 in wait

File "threading.py", line 460 in acquire

File "UM/JobQueue.py", line 98 in _nextJob

File "UM/JobQueue.py", line 124 in run

File "threading.py", line 1009 in _bootstrap_inner

File "threading.py", line 966 in _bootstrap

 

Thread 0x000070001301b000 (most recent call first):

File "threading.py", line 320 in wait

File "threading.py", line 460 in acquire

File "UM/JobQueue.py", line 98 in _nextJob

File "UM/JobQueue.py", line 124 in run

File "threading.py", line 1009 in _bootstrap_inner

File "threading.py", line 966 in _bootstrap

 

Thread 0x0000700012018000 (most recent call first):

File "threading.py", line 320 in wait

File "threading.py", line 460 in acquire

File "UM/JobQueue.py", line 98 in _nextJob

File "UM/JobQueue.py", line 124 in run

File "threading.py", line 1009 in _bootstrap_inner

File "threading.py", line 966 in _bootstrap

 

Thread 0x0000700011015000 (most recent call first):

File "threading.py", line 320 in wait

File "threading.py", line 460 in acquire

File "UM/JobQueue.py", line 98 in _nextJob

File "UM/JobQueue.py", line 124 in run

File "threading.py", line 1009 in _bootstrap_inner

File "threading.py", line 966 in _bootstrap

 

Current thread 0x00000001056d9600 (most recent call first):

File "cura/CrashHandler.py", line 397 in _logInfoWidget

File "cura/CrashHandler.py", line 182 in _createDialog

File "cura/CrashHandler.py", line 86 in __init__

File "cura_app.py", line 165 in exceptHook

File "UM/Qt/QtApplication.py", line 416 in exec

File "cura/CuraApplication.py", line 897 in run

File "cura_app.py", line 239 in <module>

 

  • Link to post
    Share on other sites

    Posted · All "5.X.X" versions of Cura crash a lot (OSX 12.4)

    Hey @widdershins,

     

    Welcome to the Ultimaker Community 🎉

     

    We have a known issue with crashes that happen with some models that are perfectly in the middle of the buildplate. If you move the model away slightly from the center of the buildplate you should be able to slice. Could it be that you are experiencing the same? 

    We are collecting cases here so the developers can solve the issue better. 
    https://github.com/Ultimaker/Cura/issues/13643
     

    Do you have a project file for us? It contains the printer and settings we need for troubleshooting. 
    To save a project file go to File -> Save project.

  • Link to post
    Share on other sites

    • 3 weeks later...
    Posted · All "5.X.X" versions of Cura crash a lot (OSX 12.4)

    The ValueError: cannot convert float NaN to integer raised because of Pandas doesn't have the ability to store NaN values for integers. 

     

    From Pandas v0.24, introduces Nullable Integer Data Types which allows integers to coexist with NaNs. This does allow integer NaNs . This is the pandas integer, instead of the numpy integer.  So, use Nullable Integer Data Types (e.g. Int64).

     

    df['x'].astype('Int64')

     

    NB: You have to go through numpy float first and then to nullable Int32, for some reason.

     

    Another solution is Using numpy.nan_to_num().  The numpy.nan_to_num() returns an array or scalar replacing Not a Number ( Not A Number ) with zero, positive_infinity with a very large number and negative_infinity with a very small (or negative) number.

     

    If you are not satisfied with the above solutions, you need to say what you want to do with NANs . You can either drop those rows df.dropna() or replace nans with something else (0 for instance: df.fillna(0) )

     

  • 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

      • Help Us Improve Cura – Join the Ultimaker Research Program
        🚀 Help Shape the Future of Cura and Digital Factory – Join Our Power User Research Program!
        We’re looking for active users of Cura and Digital Factory — across professional and educational use cases — to help us improve the next generation of our tools.
        Our Power User Research Program kicks off with a quick 15-minute interview to learn about your setup and workflows. If selected, you’ll be invited into a small group of users who get early access to features and help us shape the future of 3D printing software.

        🧪 What to Expect:
        A short 15-minute kickoff interview to help us get to know you If selected, bi-monthly research sessions (15–30 minutes) where we’ll test features, review workflows, or gather feedback Occasional invites to try out early prototypes or vote on upcoming improvements
        🎁 What You’ll Get:
         
        Selected participants receive a free 1-year Studio or Classroom license Early access to new features and tools A direct voice in what we build next
        👉 Interested? Please fill out this quick form
        Your feedback helps us make Cura Cloud more powerful, more intuitive, and more aligned with how you actually print and manage your workflow.
        Thanks for being part of the community,

        — The Ultimaker Software Team
        • 0 replies
      • Cura 5.10 stable released!
        The full stable release of Cura 5.10 has arrived, and it brings support for the new Ultimaker S8, as well as new materials and profiles for previously supported UltiMaker printers. Additionally, you can now control your models in Cura using a 3D SpaceMouse and more!
          • Like
        • 18 replies
    ×
    ×
    • Create New...