Internal error: Calling AppConfig::save() from a worker thread! Nvidia GPU error new driver.

[ghost]

Description of the bug

When booting into PrusaSlicer, no matter the version, the below errors appear, when I am using my dedicated GPU, not my integrated, and only since firmware update 528.02, and still with 528.24. After clicking OK twice the PrusaSlicer immediately closes itself.

Unhandled unknown exception; terminating the application.

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

My dedicated GPU is an NVidia RTX A2000 Notebook and the Integrated is Intel UHD Graphics with driver 31.0.101.4032
I can set the application to run using the iGPU, however in the long term I'd like to use the dGPU
CPU, in case it is relevant: i7-11850H

Project file & How to reproduce

Opening the program

Checklist of files included above

• Project file
• Screenshot

Version of PrusaSlicer

2.5.0

Operating system

Windows 10 Enterprise 19042.2486

Printer model

Prusa MINI+

[neophyl]

Did you even search the existing issues ? #9178

[ghost]

Did you even search the existing issues ? #9178

I did find both of the existing issues mentioning this before. Solution #9178 didn't work, I had to specify in windows settings to use the iGPU, which still doesn't fix the issues of using it with the RTX A2000 Notebook. Since the program is working fine with my RTX A4000 desktop GPU I'm wagering that the issue lies with Nvidia Optius and the Quadro series drivers and their interaction with API calls for Prusa Slicer. Solutions to #7839 also weren't applicable as much of that thread was based around virtual machines, something I'm not involved in my setup. I have found a patchwork solution however I wanted to document both that the issue exists and how to temporarily fix it for others having a similar issue.

[kubispe1]

@ADI-Garage-CRedding and what about this hack ? Does it help to you? #9370 (comment)

[ghost]

@ADI-Garage-CRedding and what about this hack ? Does it help to you? #9370 (comment)

I already have a temporary fix, I was hoping to get it permanently resolved and enable usage of my nvidia GPU with PrusaSlicer. I don't think this is something the community will be able to fix, this is an issue with the software itself.

[gregbo24]

I'm seeing this same issue, similar notebook (Dell Precision 5570, windows 10 pro, A2000 card). I also am having problems with the software I use for 3d scanning (EXStar from Einscan) and I'm pretty sure the problems started at the same time, and I think my computer ran a GPU driver update and that's what caused it, but I tried to revert to the old driver and it didn't fix it. Something with the GPU update is causing some fighting to happen between the CPU, integrated graphics, and the GPU.

[kubispe1]

Have you tried also 2.6.0? alfa 2? Please? Can you check ?

[gregbo24]

Same result after updating to 2.6.0 alpha 2 a couple of days ago. Currently using the sw-renderer workaround to run 2.6.

[bubnikv]

Do you guys run in any type of virtual machine? We have seen these reports when running PrusaSlicer in Windows Sandbox, which is a virtualized sandboxed Windows in Windows. The error message is likely just a false alarm and we may disable it in the future. pá 3. 2. 2023 v 17:30 odesílatel gregbo24 ***@***.***> napsal:

…

Same result after updating to 2.6.0 alpha 2 a couple of days ago. Currently using the sw-renderer workaround to run 2.6. — Reply to this email directly, view it on GitHub <#9420 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMPSI3RILVAWTJRPNCF7U3WVUXCXANCNFSM6AAAAAAUEG5VHU> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[bubnikv]

Hopefully fixed with 8472287
Implementing a test whether the current thread is the main (UI) thread
and using it on AppConfig::save() to assert if save is called
from a worker thread.
The old assert was using thread names, which did not always work
on Windows.

[lukasmatena]

Fixed, closing.