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

Crash when creating an Octoprint hardware printer #1631

Closed
laptop-laptop opened this issue Oct 11, 2021 · 14 comments
Closed

Crash when creating an Octoprint hardware printer #1631

laptop-laptop opened this issue Oct 11, 2021 · 14 comments
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.

Comments

@laptop-laptop
Copy link

Describe the bug

I am not sure if I did that incorrectly or it is a bug. For the past year on both SuperSlicer and PrusaSlicer, sometimes when I set up an Octoprint connection, the program exited by itself. For example, today I pressed the cogwheel icon under Printer Settings. I entered the name of the printer, octopi.local as the URL and the pasted the API from the web browser. Clicked the Test button and no error. SuperSlicer told me that the name of the printer already existed and asked if I would like to replace it. I clicked OK. Then, the program exited by itself. I had to launch the program again and re-enter the name, URL and API. Then, when through the same thing and the program exited for no reason again. Over the year, sometimes both programs exited when I pressed the Test button. I wonder if my way of setting up the Octoprint connection is wrong.

To Reproduce
See above

Desktop (please complete the following information):
Windows 10
SuperSlicer 2.3.56.9

@supermerill
Copy link
Owner

If it exits without a bug message, it's a bug.
But it may be a bit difficult to reproduce...
If you launch it on a command prompt (win+R, cmd)
with the command [...]\superslicer_console.exe --loglevel=3 (drag&drop the superslicer_sonsole.exe into the command line and add the --loglevel 3), can you copy & paste the last lines of logs, after making it crash?

@supermerill supermerill added the bug Something isn't working as intended label Oct 11, 2021
@supermerill supermerill changed the title What is the proper way to set up Octoprint to work with SuperSlicer? Crash when creating an Octoprint hardware printer Oct 11, 2021
@laptop-laptop
Copy link
Author

Yes, it exists without a bug message. Where is the logs located?

BTW, are we supposed to launch SuperSlicer by double clicking superslicer_console.exe or superslicer.exe? Usually I do the latter.

@supermerill
Copy link
Owner

Where is the logs located?

on the cmd window where you entered the command

@laptop-laptop
Copy link
Author

C:\Users\user1>C:\Users\user1\Desktop\SuperSlicer_2.3.56.9_win64_210906\superslicer_console.exe --loglevel=3
[2021-10-11 15:22:03.178277] [0x000004b4] [info] instance check: Another instance not found or single-instance not set.
[2021-10-11 15:22:03.226032] [0x000004b4] [info] Checking if indices need to be installed from resources...
[2021-10-11 15:22:03.760699] [0x000004b4] [info] Undo / Redo snapshot taken: New Project, Undo / Redo stack memory: 0MB WorkingSet: 64MB; PrivateBytes: 49MB; Pagefile(peak): 49MB(51MB)
[2021-10-11 15:22:05.181789] [0x00001e8c] [info] Downloading SuperSlicer online version from: https://api.github.com/repos/supermerill/SuperSlicer/releases
[2021-10-11 15:22:05.959222] [0x00001e8c] [info] Syncing configuration cache
[2021-10-11 15:23:24.381861] [0x000004b4] [info] OctoPrint: Get version at: http://octopi.local/api/version
[2021-10-11 15:23:51.286287] [0x000004b4] [info] Undo / Redo snapshot taken: Load Project: testing, Undo / Redo stack memory: 0MB WorkingSet: 174MB; PrivateBytes: 513MB; Pagefile(peak): 513MB(877MB)
[2021-10-11 15:24:16.551016] [0x000004b4] [info] OctoPrint: Get version at: http://octopi.local/api/version

@supermerill
Copy link
Owner

thanks
I'll add a bunch of logs to try t pinôint the moment when it crash. I'll come back to you this week.

@laptop-laptop
Copy link
Author

Thank you. Is there a limit on the number of times I execute "[...]\superslicer_console.exe --loglevel=3"?

As another test, I entered the printer name, url and API. Then, pressed the return key when the cursor was in the API entry box. Again it crashed.

I tried to get the logs but I can no longer use the command you listed to launch SuperSlicer. Windows keep telling me that the application cannot be executed on my PC.

@supermerill
Copy link
Owner

supermerill commented Oct 11, 2021

no limit, it's just a way to add --loglevel 3 as a parameter to the exe to enable logging. You can also use the level 5 to have even more logs.

@laptop-laptop
Copy link
Author

Is there a guide on how to set up Octoprint with SuperSlicer? Maybe I did not do it properly and caused the crash.

@supermerill
Copy link
Owner

I just copy the ip of my raspberry pi and copy/paste the key from the octoprint interface. Nothign special

supermerill added a commit that referenced this issue Oct 23, 2021
@laptop-laptop
Copy link
Author

After copy and paste the IP or the API, are we supposed to hit the return key? I recall that one time after I pasted the API value and hit the return key, it crashed.

@supermerill
Copy link
Owner

supermerill commented Oct 24, 2021

The return key validates the value, but clicking on something else out of it does the same thing.
The current nightly have more logs, can you make it crash and send me the new log?

@supermerill supermerill added the awaiting response Further information is requested label Oct 30, 2021
@SW0rden
Copy link

SW0rden commented Nov 4, 2021

I'm seeing this same issue. Spent some time setting up everything for print settings etc. and after "Add physical printer" and Octoprint settings, SS crashes to the desktop. Since I hadn't saved the presets (my bad), all was lost upon restarting SS.

Upon further testing, I have found that if you set your bed size (and a texture in my case), before you "Add physical printer", it will crash every time. If you set your bed size afterwards, it works fine.

Windows 10
SS Version 2.3.56.9

@supermerill
Copy link
Owner

Upon further testing, I have found that if you set your bed size (and a texture in my case), before you "Add physical printer", it will crash every time. If you set your bed size afterwards, it works fine.

can't make it crash.
What are the exact steps?

@SW0rden
Copy link

SW0rden commented Nov 5, 2021

Open SS, go to Printer Settings tab, Bed Shape/Set, change the bed size and OK, Edit Physical Printer and set it up for Octoprint, hit OK.......crash to desktop.

If you Edit Physical Printer and set up for Octoprint first and then set the bed size, your fine.

@supermerill supermerill added fixed for the next version That means that you should be able to test it in the latest nightly build and removed awaiting response Further information is requested labels Nov 5, 2021
@supermerill supermerill added fix is live in the last release Please download /build the last release and try to reproduce. and removed fixed for the next version That means that you should be able to test it in the latest nightly build labels Nov 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.
Projects
None yet
Development

No branches or pull requests

3 participants