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

BambuStudio got an unhandled exception: Calling AppConfig::save() from a worker thread #1944

Closed
1 of 2 tasks
ferenj-gs opened this issue Jun 20, 2023 · 9 comments
Closed
1 of 2 tasks
Assignees
Labels
bug Something isn't working

Comments

@ferenj-gs
Copy link

Bambu Studio Version

1.6.2.4

Where is the application from?

Bambu Lab Official website

OS version

Windows 11

Additional system information

Processor 12th Gen Intel(R) Core(TM) i7-1260P, 2100 Mhz, 12 Core(s), 16 Logical Processor(s)
Installed Physical Memory (RAM) 32,0 GB
Adapter Type NVIDIA T550 Laptop GPU, NVIDIA compatible
Adapter Type Intel(R) Iris(R) Xe Graphics Family, Intel Corporation compatible

Printer

X1-Carbon

How to reproduce

  1. Create App profile under windows Graphics settings for bambu studio to use the dedicated T550 GPU
  2. Start Bambu Studio

Actual results

Crash happens immediately
image

after hitting ok:

image

Expected results

Bambu studio should start normally.

Project file & Debug log uploads

debug_network_Tue_Jun_20_10_58_31.zip

FYI: 0 byte logfile is generated, most probably as this is a startup issue

Checklist of files to include

  • Log file
  • Project file
@ferenj-gs ferenj-gs added the bug Something isn't working label Jun 20, 2023
@bambu123 bambu123 self-assigned this Jun 25, 2023
@bambu123
Copy link
Collaborator

bambu123 commented Jun 25, 2023

image

Please create a minidump when this dialog show. The dump is useful to analyze the problem and please send it to us.
You can create minidump with the following steps:

  • Open the Windows Task Manager
  • Find and select the Bambu Studio process in it
  • Right click the process and choose the 'Create Minidump File' menu item
  • Select a folder to save the file

@lanewei120
Copy link
Collaborator

@ferenj-gs
thanks for reporting this issue

is this issue reproducible?

from log
image
it seems the thread_name of BambuStudio is wrong in your environment
it cause the context check failed

and what does this mean "Create App profile under windows Graphics settings for bambu studio to use the dedicated T550 GPU"

@CrashTestCoder
Copy link

I reproduced this issue. same thread name, same error. I went into settings and told windows to make bambu studio use my T600 nVidia GPU.
image

@lanewei120
Copy link
Collaborator

is this issue reproducible?

@CrashTestCoder

is this issue 100% reproducible?

@CrashTestCoder
Copy link

Will verify when I get back to my computer in the morning. But it persisted through reinstalling the software and multiple reboots.

Disabling the manual gpu selection fixed it immediately

@CrashTestCoder
Copy link

I just tested on my old personal laptop and it is not reproducible with a Nvidia 940mx. So maybe its just a problem with quadros? Will report back in the morning

@CrashTestCoder
Copy link

CrashTestCoder commented Jul 27, 2023

Can confirm. 100% reproducible.
image
image
image

debug_Thu_Jul_27_07_19_04_23576.log
(removed ".0" from end of file name so github would let me upload it)

PC Hardware:

Device name
Full device name
Processor 11th Gen Intel(R) Core(TM) i5-11400H @ 2.70GHz 2.69 GHz
Installed RAM 32.0 GB (31.7 GB usable)
Device ID
Product ID
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

image
image

@lanewei120
Copy link
Collaborator

thanks very much
it should be a similiar issue as prusa3d/PrusaSlicer#9420
we will fix it soon

thanks

lanewei120 pushed a commit that referenced this issue Jul 31, 2023
corner cases

this patch is cherry-picked from PrusaSlicer's 84722876012ca310e29b291e10fef9d18ae26cea
thanks to 'Vojtech Bubnik' for the fix

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.
Fixes #7839 #9178 #9370 #9420
lanewei120 pushed a commit that referenced this issue Jul 31, 2023
corner cases

this patch is cherry-picked from PrusaSlicer's 84722876012ca310e29b291e10fef9d18ae26cea
thanks to 'Vojtech Bubnik' for the fix

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.
Fixes #7839 #9178 #9370 #9420
@lanewei120
Copy link
Collaborator

already fixed in v1.7.2.51 hotfix version

DzzD pushed a commit to DzzD/BambuStudio that referenced this issue Sep 24, 2023
…n some

corner cases

this patch is cherry-picked from PrusaSlicer's 84722876012ca310e29b291e10fef9d18ae26cea
thanks to 'Vojtech Bubnik' for the fix

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.
Fixes #7839 #9178 #9370 #9420
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants