Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cura 3.1 crash on initialization #2930

Closed
draput opened this issue Dec 7, 2017 · 9 comments

Comments

@draput
Copy link

commented Dec 7, 2017

Hi,

I want to report a crash at initialization at the "Set-up scene..." phase. Windows7 64 bit. Cura 3.0.4. is working without problems.

Best regards,
Draghi

P.S. Here is an excerpt from cural.log

2017-12-07 16:57:24,699 - INFO - FirmwareUpdateChecker.FirmwareUpdateChecker._onContainerAdded [52]: You have a 'Custom FDM printer #2' in printer list. Let's check the firmware!
2017-12-07 16:57:24,699 - INFO - FirmwareUpdateChecker.FirmwareUpdateChecker._onContainerAdded [52]: You have a 'Custom FDM printer' in printer list. Let's check the firmware!
2017-12-07 16:57:24,699 - DEBUG - UM.Settings.ContainerRegistry.load [231]: Loading data into container registry took 6.810009717941284 seconds
2017-12-07 16:57:25,089 - DEBUG - UM.Controller.setActiveView [86]: Setting active view to SolidView
2017-12-07 16:57:26,319 - DEBUG - OctoPrintPlugin.OctoPrintOutputDevice.connect [333]: Connection with instance A8-Octo with url http://xxxxxxxxxxxxxxxxx:80/ started
2017-12-07 16:57:27,089 - CRITICAL - cura.CrashHandler.init [62]: An uncaught exception has occurred!
2017-12-07 16:57:27,099 - CRITICAL - cura.CrashHandler.init [65]: Traceback (most recent call last):
2017-12-07 16:57:27,099 - CRITICAL - cura.CrashHandler.init [65]: File "", line 969, in _find_and_load
2017-12-07 16:57:27,099 - CRITICAL - cura.CrashHandler.init [65]: File "", line 958, in _find_and_load_unlocked
2017-12-07 16:57:27,099 - CRITICAL - cura.CrashHandler.init [65]: File "", line 664, in _load_unlocked
2017-12-07 16:57:27,099 - CRITICAL - cura.CrashHandler.init [65]: File "", line 634, in _load_backward_compatible
2017-12-07 16:57:27,099 - CRITICAL - cura.CrashHandler.init [65]: File "startup.py", line 12, in
2017-12-07 16:57:27,099 - CRITICAL - cura.CrashHandler.init [65]: File "", line 969, in _find_and_load
2017-12-07 16:57:27,109 - CRITICAL - cura.CrashHandler.init [65]: File "", line 958, in _find_and_load_unlocked
2017-12-07 16:57:27,109 - CRITICAL - cura.CrashHandler.init [65]: File "", line 664, in _load_unlocked
2017-12-07 16:57:27,109 - CRITICAL - cura.CrashHandler.init [65]: File "", line 634, in _load_backward_compatible
2017-12-07 16:57:27,109 - CRITICAL - cura.CrashHandler.init [65]: File "Console.py", line 24, in
2017-12-07 16:57:27,109 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\bin\cura_app.py", line 83, in
2017-12-07 16:57:27,109 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\CuraApplication.py", line 681, in run
2017-12-07 16:57:27,109 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\BuildVolume.py", line 107, in init
2017-12-07 16:57:27,119 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\CuraApplication.py", line 733, in getMachineManager
2017-12-07 16:57:27,119 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\Settings\MachineManager.py", line 1234, in createMachineManager
2017-12-07 16:57:27,119 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\Settings\MachineManager.py", line 109, in init
2017-12-07 16:57:27,119 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\Settings\MachineManager.py", line 357, in setActiveMachine
2017-12-07 16:57:27,119 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\UM\Application.py", line 156, in setGlobalContainerStack
2017-12-07 16:57:27,119 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\UM\Signal.py", line 212, in emit
2017-12-07 16:57:27,119 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\UM\Signal.py", line 315, in __performEmit
2017-12-07 16:57:27,119 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\BuildVolume.py", line 500, in _onStackChanged
2017-12-07 16:57:27,129 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\BuildVolume.py", line 597, in _updateDisallowedAreas
2017-12-07 16:57:27,129 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\BuildVolume.py", line 956, in _getEdgeDisallowedSize
2017-12-07 16:57:27,129 - CRITICAL - cura.CrashHandler.init [65]: ValueError: max() arg is an empty sequence

@ChrisTerBeke

This comment has been minimized.

Copy link
Member

commented Dec 7, 2017

Did you by any chance use the 3.1 beta before this?

@igorepi

This comment has been minimized.

Copy link

commented Dec 9, 2017

I have exactly same problem with Cura 3.1 and W7 x64 :

2017-12-09 13:38:14,596 - DEBUG - UM.Backend.Backend._logSocketState [178]: Socket state changed to Connected
2017-12-09 13:38:14,597 - DEBUG - UM.Backend.Backend._onSocketStateChanged [168]: Backend connected on port 49674
2017-12-09 13:38:24,449 - DEBUG - AutoSave.AutoSave._onTimeout [48]: Autosaving preferences, instances and profiles
2017-12-09 13:38:28,046 - INFO - FirmwareUpdateChecker.FirmwareUpdateChecker._onContainerAdded [52]: You have a 'Tevo Tarantula' in printer list. Let's check the firmware!
2017-12-09 13:38:28,049 - DEBUG - UM.Settings.ContainerRegistry.load [231]: Loading data into container registry took 13.454769611358643 seconds
2017-12-09 13:38:28,581 - DEBUG - UM.Controller.setActiveView [86]: Setting active view to SolidView
2017-12-09 13:38:28,789 - CRITICAL - cura.CrashHandler.init [62]: An uncaught exception has occurred!
2017-12-09 13:38:28,791 - CRITICAL - cura.CrashHandler.init [65]: Traceback (most recent call last):
2017-12-09 13:38:28,792 - CRITICAL - cura.CrashHandler.init [65]: File "", line 969, in _find_and_load
2017-12-09 13:38:28,794 - CRITICAL - cura.CrashHandler.init [65]: File "", line 958, in _find_and_load_unlocked
2017-12-09 13:38:28,795 - CRITICAL - cura.CrashHandler.init [65]: File "", line 664, in _load_unlocked
2017-12-09 13:38:28,796 - CRITICAL - cura.CrashHandler.init [65]: File "", line 634, in _load_backward_compatible
2017-12-09 13:38:28,798 - CRITICAL - cura.CrashHandler.init [65]: File "startup.py", line 12, in
2017-12-09 13:38:28,799 - CRITICAL - cura.CrashHandler.init [65]: File "", line 969, in _find_and_load
2017-12-09 13:38:28,800 - CRITICAL - cura.CrashHandler.init [65]: File "", line 958, in _find_and_load_unlocked
2017-12-09 13:38:28,802 - CRITICAL - cura.CrashHandler.init [65]: File "", line 664, in _load_unlocked
2017-12-09 13:38:28,803 - CRITICAL - cura.CrashHandler.init [65]: File "", line 634, in _load_backward_compatible
2017-12-09 13:38:28,804 - CRITICAL - cura.CrashHandler.init [65]: File "Console.py", line 24, in
2017-12-09 13:38:28,806 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\bin\cura_app.py", line 83, in
2017-12-09 13:38:28,807 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\CuraApplication.py", line 681, in run
2017-12-09 13:38:28,809 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\BuildVolume.py", line 107, in init
2017-12-09 13:38:28,810 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\CuraApplication.py", line 733, in getMachineManager
2017-12-09 13:38:28,811 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\Settings\MachineManager.py", line 1234, in createMachineManager
2017-12-09 13:38:28,813 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\Settings\MachineManager.py", line 109, in init
2017-12-09 13:38:28,814 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\Settings\MachineManager.py", line 357, in setActiveMachine
2017-12-09 13:38:28,815 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\UM\Application.py", line 156, in setGlobalContainerStack
2017-12-09 13:38:28,817 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\UM\Signal.py", line 212, in emit
2017-12-09 13:38:28,818 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\UM\Signal.py", line 315, in __performEmit
2017-12-09 13:38:28,820 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\BuildVolume.py", line 500, in _onStackChanged
2017-12-09 13:38:28,821 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\BuildVolume.py", line 597, in _updateDisallowedAreas
2017-12-09 13:38:28,822 - CRITICAL - cura.CrashHandler.init [65]: File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\BuildVolume.py", line 956, in _getEdgeDisallowedSize
2017-12-09 13:38:28,824 - CRITICAL - cura.CrashHandler.init [65]: ValueError: max() arg is an empty sequence

@padizar

This comment has been minimized.

Copy link

commented Dec 9, 2017

Сonfirm this problem

@ChrisTerBeke

This comment has been minimized.

Copy link
Member

commented Dec 10, 2017

Again: did any of you use the 3.1 beta before using the 3.1 stable? If so, remove your 3.1 data folder and try 3.1 stable again. If it then still gives error's we'd like the complete log files for reproduction.

@igorepi

This comment has been minimized.

Copy link

commented Dec 10, 2017

No, I didn't use 3.1 beta.
cura.log

@draput

This comment has been minimized.

Copy link
Author

commented Dec 10, 2017

No, I did NOT used the 3.1 beta. I have used 3.0.4.

@ChrisTerBeke

This comment has been minimized.

Copy link
Member

commented Dec 10, 2017

@LipuFei related to that fix you did on Friday?

@ChrisTerBeke

This comment has been minimized.

Copy link
Member

commented Dec 10, 2017

Related to #2798?

@ChrisTerBeke

This comment has been minimized.

Copy link
Member

commented Dec 10, 2017

I'm closing this issue in favor of the already existing #2798. Please keep an eye on that one to track the status of fixing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
5 participants
You can’t perform that action at this time.