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

PrusaSlicer 2.6 Beta1 crashes when opening Configuration Wizard #10556

Closed
1 of 2 tasks
Hovedskou opened this issue May 14, 2023 · 4 comments
Closed
1 of 2 tasks

PrusaSlicer 2.6 Beta1 crashes when opening Configuration Wizard #10556

Hovedskou opened this issue May 14, 2023 · 4 comments

Comments

@Hovedskou
Copy link

Hovedskou commented May 14, 2023

Description of the bug

When I open Configuration Wizard the PrusaSlicer crashes.
Tested on 3 different computers running Windows 11, and they all generate the same error and crashes.

Project file & How to reproduce

02
01

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

2.6 Beta1

Operating system

Windows 11 Pro build 25357

Printer model

MK4

@nifty1a
Copy link

nifty1a commented May 14, 2023

I have the same error
Edition Windows 11 Home
Version 22H2
Installed on ‎13/‎10/‎2022
OS build 22621.1702
Experience Windows Feature Experience Pack 1000.22641.1000.0

@Jan-Soustruznik
Copy link
Collaborator

@Hovedskou ,

thank you for report. We will try to fix in next release.

Issue created: SPE-1699

@Evovita
Copy link

Evovita commented May 16, 2023

The crash - at least for me - occurs on line 162 (and same problem also noticed on line 170) of /src/slic3r/GUI/ConfigWizard.cpp when the
\PrusaSlicer-beta\cache\EvoLabs.idx cannot be found after I copied my custom Vendor profile files, including EvoLabs.idx file (that work in PrusaSlicer 2.5.2 installed on the same machine), into C:\Users\{User Name}\AppData\Roaming\PrusaSlicer-beta\vendor prior to running a debug session.

If I remove my custom Vendor profile files, the Configuration Wizard window appears without error.

Problem

format function failing because it's expecting 2 placeholders instead of just 1:

if (!boost::filesystem::exists(idx_path)) {
    BOOST_LOG_TRIVIAL(error) << format("Could not load bundle %1% due to missing index %1%.", id, idx_path.string());
    continue;
}

Fix

  1. Include 2nd place holder in the format string:

BOOST_LOG_TRIVIAL(error) << format("Could not load bundle %1% due to missing index %2%.", id,idx_path.string());

  1. Make sure custom profile .idx file (e.g. EvoLabs.idx) is copied to \PrusaSlicer-beta\cache\, in addition to \PrusaSlicer-beta\vendor\

OS specs

Edition Windows 11 Pro
Version 22H2
Installed on ‎21/‎09/‎2022
OS build 22621.1702
Experience Windows Feature Experience Pack 1000.22641.1000.0

IDE

Microsoft Visual Studio Community 2022
Version 17.5.5
VisualStudio.17.Release/17.5.5+33627.172
Microsoft .NET Framework
Version 4.8.09032

Evovita added a commit to Evovita/PrusaSlicer that referenced this issue May 17, 2023
lukasmatena pushed a commit that referenced this issue May 17, 2023
@kocikdav
Copy link
Collaborator

This crash is fixed in 2.6.0-beta2. Thank you for reporting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants