SoftFever / OrcaSlicer

G-code generator for 3D printers (Bambu, Prusa, Voron, VzBot, RatRig, Creality, etc.)
https://discord.gg/P4VE9UY9gJ
GNU Affero General Public License v3.0
7.33k stars 869 forks source link

Crash when trying to reprint remotely. #3913

Closed nakwada closed 3 months ago

nakwada commented 9 months ago

OrcaSlicer Version

1.9.0

OS version

Windows 10

Additional system information

No response

Printer

Bambulab P1S with AMS

How to reproduce

  1. Go to Device > MicroSD Card
  2. Go to Model tab
  3. Click Print on the thumbnail of any already printed plate.
  4. Hanging for a few seconds then crash, OrcaSlicer closes

Actual results

OrcaSlicer closes leaving some communication processes open with the printer. When I retry the operation a few times, Orca crashes and at some point indicates the printer is already in too many conversations. Still cannot restart a print at this point. Only solution is to reslice and resend to print.

Expected results

It should not close ^^ Under normal conditions the window to select the spool in the AMS and confirm the print should appear.

Project file & Debug log uploads

2023.01.31 - OrcaSlicer crash logs.zip

Checklist of files to include

nakwada commented 9 months ago

Additional informations about the printer: Printer is up to date with the latest firmware as of February 2024. Printer is connected to same network as laptop.

shledge commented 9 months ago

Getting this same issue too - it doen't happen if I open a 3mf file first, though.

Works fine in Bambuslicer, and seems to have only recently started to happen because of an update to the network plugin.

Jer406 commented 8 months ago

im having exactly the same issue

dartrax commented 6 months ago

Also reported in (later) #4899. The workaround is to open a random project file first, as shledge stated above.

github-actions[bot] commented 3 months ago

Orca bot: this issue is stale because it has been open for 90 days with no activity.

github-actions[bot] commented 3 months ago

Orca bot: This issue was closed because it has been inactive for 7 days since being marked as stale.