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.

Sign up for GitHub

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

Jump to bottom

Internal error: Calling AppConfig::save() from a worker thread! (twice) #4046

Closed
sprior opened this issue Jan 4, 2024 · 4 comments
Closed

Internal error: Calling AppConfig::save() from a worker thread! (twice) #4046

sprior opened this issue Jan 4, 2024 · 4 comments
Labels
fix is live in the last release Please download /build the last release and try to reproduce. problem

Comments

@sprior
Copy link

sprior commented Jan 4, 2024

What happened?

Sometimes when I exit SS I get a dialog box listing:
Internal error: Calling AppConfig::save() from a worker thread!
Internal error: Calling AppConfig::save() from a worker thread!

Project file & How to reproduce

Exit SS

Version

2.5.59.6

Operating system

Windows 11

Printer model

No response
@supermerill
Copy link
Owner

Can you replace (saving the previous one) the Slic3r.dll that is in the main directory by this one
Slic3r.zip
and try to reproduce the error?
The error message should be different.

@sprior
Copy link
Author

sprior commented Jan 15, 2024

I tried that dll and it completely lost my environment and opened the configuration wizard. Fortunately when I returned to the old dll everything came back.

@supermerill
Copy link
Owner

yes, it's just compiled with a different internal name (slic3r instead of superslicer)

@walkmanyy
Copy link

I tried new Slic3r.dll, the error message changes to: Internal error: calling GUI APP:: post_init() from a worker thread!

@supermerill supermerill added the fixed for the next version That means that you should be able to test it in the latest nightly build label Feb 7, 2024
supermerill added a commit that referenced this issue Feb 7, 2024
@supermerill
change exception to warning log for AppConfig::save() on badly named …
53e4f4b 
…thread.

On win11, the vent thread doesn't have the right name?
#4046
@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 Feb 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
fix is live in the last release Please download /build the last release and try to reproduce. problem
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sprior @supermerill @walkmanyy