Latest bambu is insanely slow and laggy

[chamsters]

Bambu Studio Version

2.7.1.57

Where is the application from?

Bambu Lab Official website

OS version

Mac OS - latest

Additional system information

macbook pro m4 pro
32gb ram

This isn't an issue with my laptop - previous releases are all OK

Printer

X2D

How to reproduce

Open any file with bambu studio. There's a 1 minute + lag to open anything.

Actual results

Takes over a minute to open a file.

Expected results

Open immediately like in previous releases.

Project file & Debug log uploads

n/a

Checklist of files to include

• Log file
• Project file

[JiaYun-Bambu]

We’re very sorry for the inconvenience. We’re doing our best to track down this issue. In the meantime, you may try a temporary workaround suggested by another user ([rustyshelf] ) in this ticket(#10968): after opening the software, minimize and then maximize the window to see if it returns to normal.

[trusteeoil]

Additional crash analysis + workaround confirmation

System: Mac Mini M2, 8GB RAM, macOS Tahoe 26.5.1
Version: 2.7.1.57
Printers on account: Multiple (A1, X2D, P2S)

Workaround confirmation

The minimize → maximize workaround from #10968 works for me.

---

Crash log analysis

I have a full crash log from this version. The actual fault is a segfault in Thread 31:

Thread 31 Crashed:
0  BambuStudio  SendMakerlabList()::$_9::operator()(std::string&&)
1  BambuStudio  get_makerlab_list(...)::$_12::operator()(std::string&&, unsigned int&&)
2  BambuStudio  Slic3r::Http::priv::http_perform()

Exception: EXC_BAD_ACCESS (SIGSEGV) — KERN_INVALID_ADDRESS at a likely corrupted pointer (possible pointer authentication failure on ARM64).

This looks like a use-after-free or dangling pointer in the MakerLab HTTP callback. The HTTP request completes and fires the callback, but the object it's trying to write back into has already been freed or moved.

---

Main thread freeze mechanism

While Thread 31 is doing its MakerLab HTTP work, Thread 0 (main UI thread) is blocked here:

wxWebViewWebKit::RunScriptSync()
wxWebViewWebKit::RunScript()
wxWebViewWebKit::AddScriptMessageHandler()
WebView::CreateWebView()
wxEventLoopBase::YieldFor()

The UI is stuck in YieldFor while WebKit initializes and registers script message handlers. This is the 30–120 second freeze window where buttons gray out and clicks are ignored. The UI only recovers once WebKit finishes init — or crashes if Thread 31 fires its bad callback first.

---

Additional observations

Wi-Fi disabled → freeze still occurs. Rules out network latency as the root cause. Something in the locally-stored login/session state is triggering the MakerLab request and the bad callback even with no active network.

Logged out → mostly stable. Logged in → freezes/crashes every launch. The MakerLab panel appears to only activate post-login, consistent with the crash being in the MakerLab list fetch path.

Disabling cloud sync, auto-sync presets, home page online content — none prevented the issue.
Cache wipe / fresh config — no change.

M2 chip — confirms this is not isolated to M4 hardware as most other reports have been.

---

[PlaczkiewiczPawel]

I have the same problem. After launching, it runs smoothly on the main page, but as soon as I switch to any tab, the application barely works - everything freezes and becomes very laggy. It's impossible to do anything.

But if you minimize and then maximize the application, everything becomes smooth again.

Bambu Studio 2.7.1.57
MacBook Pro M2 with the latest OS.

[Talmadge3000]

Seeing the same issues with
Bambu Studio 2.7.1.57
Macbook Pro Apple M2 Max
Tahoe 26.5.1

[JohnSmithCYM]

Thank you everyone for your continued attention and feedback regarding the recent Studio issues. We have identified the root cause as a loading error with WebView on specific versions of macOS from 26.5 or newer.

We have developed an emergency fix, but we want to ensure it covers all Mac OS versions effectively. We are reaching out to all Mac users (especially those on macOS 26.5 and newer) for help in verifying this build.

Test Build Download (Dropbox): Bambu_Studio_mac-v02.07.01.57.dmg

If you have experienced issues, please test this version and leave your feedback in the comments below. Please include your macOS version and hardware model (e.g., M1/M2/M3 or Intel).

Once confirmed by the community, we will officially release this update as soon as possible to get everyone back on track. We sincerely appreciate your support and help!

cc @tonghao-bbl @walterwongbbl @rouyuanzi-bambu

The same with #10968

[ssgolov]

Same issue.
macOS 12.7.6
Bambu Studio 2.7.1.57
Works normal after minimize and then maximize.

[fmancini]

Same issue :/
macOS 12.7.6 / Apple M4 Max
Bambu Studio 2.7.1.57
Tahoe 26.5 (25F71)

[JohnSmithCYM]

@ssgolov @fmancini Did you try my Test Build or just get studio package from Github release page or Bambulab official website ?

[ssgolov]

I downloaded the app from the official Bambulab website.

For context, I'm completely new to 3D printing and recently ordered an A1 Mini. While waiting for it to be delivered, I installed the app to get familiar with the interface and settings.

After installing the software, I ran into this issue and started searching GitHub for a solution.

For now, I've rolled back to Bambu Studio 2.6.0 Public Release, which seems to work without any problems.

[JohnSmithCYM]

Thanks for your feedback. Can you give it a try with a test build: https://github.com/bambulab/BambuStudio/releases/download/v02.07.00.55/Bambu_Studio_mac-v02.07.01.57.dmg

[JiaYun-Bambu]

@ssgolov @fmancini @Talmadge3000 @PlaczkiewiczPawel @trusteeoil @chamsters
We have developed an emergency fix, but we want to ensure it covers all Mac OS versions effectively. We are reaching out to all Mac users (especially those on macOS 26.5 and newer) for help in verifying this build.

https://github.com/bambulab/BambuStudio/releases/download/v02.07.01.57/Bambu_Studio_mac-v02.07.01.57-pre_release.dmg

If you have experienced issues, please test this version and leave your feedback in the comments below. Please include your macOS version and hardware model (e.g., M1/M2/M3 or Intel).

Once confirmed by the community, we will officially release this update as soon as possible to get everyone back on track. We sincerely appreciate your support and help!