This article describes how to handle crash and freeze problems on various operating system platforms.
On the Windows platform, we will record dump information in the log directory of the application. Please attach the * .dmp files when reporting a crash issue.
You can use the same non-install version of Bambu Studio from Releases · bambulab/BambuStudio
For example, the non-install version of v1.7.4.52 is like this(please make sure to use the same version as your installed one)
After this issue is reproduced by using the non-install version, please help to send the following logs to us for our debugging:
When the application no longer responds to user actions, especially when an unresponsive pop-up dialog appears, please use the following steps to obtain dump information.
On macOS, your crash dumps are automatically handled by Crash Reporter.
You can save the text to a file and send it to us for analysis.
You can also find crash reports by executing Console and going to the Crash Reports group.
Or you can locate them in ~/Library/Logs/DiagnosticReports. Please attach the * .ips files when reporting a crash issue.
When the application no longer responds to user actions, especially when an unresponsive pop-up dialog appears, you can force Bambu Studio to close. Diagnose Reporter will create diagnose dumps.
You can save the text to a file and send it to us for analysis.
You can also find diagnostic reports by executing Console and going to the Diagnostic Reports group.
Or you can locate them in ~/Library/Logs/DiagnosticReports. Please attach the * .diag files when reporting a freeze issue.
On the Linux platform, when you encounter a crash problem with Bambu Studio, you need to debug Bambu Studio through gdb.
When debugging with gdb, you need to find a way to reproduce the crash problem. The steps to debug with gdb are:
When the application no longer responds to user actions, especially when an unresponsive pop-up dialog appears, you can debug Bambu Studio through gdb.
The steps to debug with gdb are: