Access violation on prevoius and current version on some modelk

Bambu Lab Software Bambu Studio
1

Bambu Studio Access Violation When Slicing Specific Model

Summary

Bambu Studio consistently crashes with an Access Violation when attempting to slice one particular model.

The same model slices successfully in OrcaSlicer, which suggests that the geometry is valid enough to slice and that this may be a Bambu Studio-specific issue.

Environment

  • OS: Windows

  • Previous Bambu Studio version: 2.8.0.50

  • Current/latest Bambu Studio version: same problem after upgrade

  • Model created/exported from Autodesk Fusion

Problem

When slicing the modified flasher body, Bambu Studio terminates with an Access Violation.

The crash is reproducible.

I initially suspected a problem with the 3MF file, but the same behaviour occurs after exporting the model as STL, so it does not appear to be caused by 3MF project metadata.

Tests Performed

  • Original 3MF in Bambu Studio → Access Violation

  • STL exported from the same model in Bambu Studio → Access Violation

  • 3MF in OrcaSlicer → slices successfully

  • STL in OrcaSlicer → slices successfully

  • Upgraded Bambu Studio to the latest available version → same Access Violation

The issue therefore appears to be specific to Bambu Studio’s handling of this particular geometry rather than a generally invalid model.

Expected Behaviour

Bambu Studio should slice the model normally, as OrcaSlicer is able to do with the same geometry.

Actual Behaviour

Bambu Studio crashes during slicing with an Access Violation.

Reproduction

  1. Start Bambu Studio.

  2. Import the affected 3MF or STL model.

  3. Start slicing.

  4. Bambu Studio crashes with an Access Violation.

Additional Information

The model is a modified version of an existing design which previously sliced without problems. The crash started after changes to the geometry.

The model is commercially sensitive, so I would prefer not to attach it publicly to the report. However, I am happy to share the model privately with Bambu Lab engineers/support if they are interested in reproducing and investigating the issue.

I can also provide the original working model for comparison, together with Bambu Studio logs or crash dumps if required.

2

Usually a repeatable crash on a specific model during SLICING [not loading, editing, etc] are due to invalid model definitions[nonmanifold, missing data, etc] or obscene excessive triangle count (1billion+).

You’d need to attach the file / a test file that shows the same problem here otherwise everythign is speculaiton

IMO check it via a 3d object repair tool [if running slicers on windows, can be done from within the slicer, right click the object]. If its actually just got a couple billion extra triangles, simplify the mesh a couple times till it calms down

3

As I wrote, I can’t share this model on a public forum. I can send it to someone from dev team to investigate

I did of course all that repair magic.

4

This isn’t where they read, you need to put this in a support ticket or a GitHub issue

5

The best place to submit bug/crash reports would be GitHub Issues. I’ve yet to see any developer response here on the forums (though there’s a first time for everything I suppose). The issue form will ask for logs (they’re encrypted already with a key BL employees can access) and a crash dump. They do ask for a project file, but just mention that you can’t post it publicly.

Thanks,
-Max

6

Ok, then can you find/create a model that does have the issue that you can instead?