Visiting the "Device" page causes Segfault

[ndom91]

Is there an existing issue for this problem?

• [x] I have searched the existing issues

OrcaSlicer Version

v2.3.0-rc

Operating System (OS)

Linux

OS Version

NixOS

Additional system information

Using the latest nixpkgs orca-slicer package, which is building from tag v2.3.0-rc (https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/by-name/or/orca-slicer/package.nix#L65)

• Intel Core Ultra 7 155U
• w/ Xe graphics

Printer

Bambu A1

How to reproduce

1. Launch OrcaSlicer
2. Without any project loaded, go to "Devices" page
3. Segfault crash

Actual results

Segfault crash.

When executing orca-slicer with the --debug 5 flag, there is no additional helpful output regarding the crash in the terminal nor the debug logs.

This happens when there is no project loaded either.

I also tried to remove my entire ~/.config/OrcaSlicer config directory and restart Orca. I went through the onboarding wizard and logged back into my bambu accuont, and immediately thereafter visiting the "Device" page causes the Segfault crash again.

Interestingly, if I wipe my orcaslicer config, relaunch and go through the wizard again, but do not sign in to my BambuLab account - then I do not experience this issue.

This seems to indicate that something in one of my synced profiles/settings/account is causing an issue here. Anything else I cna provide to help debug this?

Expected results

Device page loads

Project file & Debug log uploads

The dbeug log also doesn't include anything help. This is the entire contents:

[warning]       2025-03-17 19:09:48.299154[Thread 0x00007f17f6052980]:get_network_function, can not find function bambu_network_del_subscribe
[warning]       2025-03-17 19:09:48.299328[Thread 0x00007f17f6052980]:get_network_function, can not find function bambu_network_get_model_id_from_desgin_id
[warning]       2025-03-17 19:09:48.299374[Thread 0x00007f17f6052980]:get_network_function, can not find function bambu_network_get_profile_3mf
[error] 2025-03-17 19:09:50.017585[Thread 0x00007f17f6052980]:calc_exclude_triangles:Unable to create exclude triangles
[error] 2025-03-17 19:09:51.724016[Thread 0x00007f17f6052980]:calc_exclude_triangles:Unable to create exclude triangles

That was from the loading of OrcaSlicer though, the crash happened minutes later once I navigated to the "Devices" page.

Checklist of files to include

• [x] Log file
• [x] Project file

Anything else?

No response

[ndom91]

Okay a bit more interesting info.. since I noticed not signing into my Bambu account caused the issue to not appear, I began playing around with the ~/.config/OrcaSlicer/user/* files a bit.

Emptying one-by-one the user,process, and machine profile directories all did not help, i.e. even if all three of htose directories were empty and not containing any of my json file profiles, the issue still appears if I'm logged into my Bambu account.

I noticed that the app remains interactive, i.e. I can hover over the page buttons and see their outline appear, for a split second before crashing. Apparently the crash occurs as soon as my machine info gets loaded, I can see the spool color get loaded correclty off of what I currently set on the device and in that second the application is no longer interactive and has crashed.

For what it's worth my A1 has been on the same firmwrae for months (01.04.00.00) and OrcaSlicer worked fine with my account / device for a long time as well. This issue just started appearing about a week ago, I can't htink of what I've changed around then though 🤔 I'll continue to investigate what's loaded here

[Noisyfox]

Does your system create core dumps and crash logs when app crashes?

[ndom91]

All of a sudden this doesn't happen anymore 🤔 🤷

I haven't changed any settings or configuration on orca slicer or used a different version. So in addition to the previous evidence, I'm pretty sure this was due to some data either on the printer itself or on bambu cloud pertaining to the device that was loaded lazily when visiting the device page, and this data has now changed behind the scenes. Or maybe a formatting error like including a trailing comma in some JSON payload from Bambu or something 😂

[ndom91]

Does your system create core dumps and crash logs when app crashes?

No, don't have either of them unfortunately. I included the only contents of any ~/.config/OrcaSlcier/log/* file(s) that weren't empty above, and those log lines occured way earlier to the crash happening. There was nothing printed either shortly before or after the crash :(

[ndom91]

Andd it's back 😂

[zzz541]

I'm having same issue. Leaving UI blank it shows Welcome to moonraker page. Entering the ip or ip:port both start loading correct page then crash. I am linux with latest orcaslicer. I have to enter ip:port to get orca not to crash when adding printer for sending files.

[Noisyfox]

I'm having same issue. Leaving UI blank it shows Welcome to moonraker page. Entering the ip or ip:port both start loading correct page then crash. I am linux with latest orcaslicer. I have to enter ip:port to get orca not to crash when adding printer for sending files.

That's a different problem, given the OP uses BBL printers. For yours, check https://github.com/SoftFever/OrcaSlicer/issues/7210

[ndom91]

I tried following the advice here and using an older version of the bambu ntework plugin. No luck.

However, that caused my device to not be auto-selected, and I noticed that visiting the device page without a printer selected is fine. When I select my A1, hwoever, it seg-faults.

EDIT: Oh also I now noticed that there's a (not very helpful) message printed when running with --debug 5 before the segfault.

BambuTunnel::GetMsg(1)
Segmentation fault (core dumped)

[ndom91]

Quick update - I decided to move to LAN Only mode last night. Blocked the A1 from internet access via my firewall and used homeassistant to monitor/control it remotely/locally.

This also had the positive side effect of "fixing" this issue. I can now visit the "Device" page in Orcaslicer without any issue.

[githubuser853]

This started happening to me today also however, I'm on an M2 Macbook Air, MacOS Sequoia 15.4 (24E248).

I fully re-installed Orca from scratch (including renaming the ~/Library/Application Support/OrcaSlicer/ directory before starting the fresh install).

When attempting to login to my makerworld account it immediately crashed Orca Slicer.

This is with Orca Slicer v2.3.0.

[Noisyfox]

This started happening to me today also however, I'm on an M2 Macbook Air, MacOS Sequoia 15.4 (24E248).

I fully re-installed Orca from scratch (including renaming the ~/Library/Application Support/OrcaSlicer/ directory before starting the fresh install).

When attempting to login to my makerworld account it immediately crashed Orca Slicer.

This is with Orca Slicer v2.3.0.

Could you provide the crash log? You could find it in the "Console" app. Thanks!

[githubuser853]

Here you go.

I can definitely reproduce this if you need me to.

On Wed, Apr 2, 2025 at 8:43 PM Noisyfox @.***> wrote:

This started happening to me today also however, I'm on an M2 Macbook Air, MacOS Sequoia 15.4 (24E248).

I fully re-installed Orca from scratch (including renaming the ~/Library/Application Support/OrcaSlicer/ directory before starting the fresh install).

When attempting to login to my makerworld account it immediately crashed Orca Slicer.

This is with Orca Slicer v2.3.0.

Could you provide the crash log? You could find it in the "Console" app. Thanks!

— Reply to this email directly, view it on GitHub https://github.com/SoftFever/OrcaSlicer/issues/8942#issuecomment-2774116532, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDTZLVI2XFC5JWQVVC6VQE32XSG5RAVCNFSM6AAAAABZGGT2GSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZUGEYTMNJTGI . You are receiving this because you commented.Message ID: @.***> [image: Noisyfox]Noisyfox left a comment (SoftFever/OrcaSlicer#8942) https://github.com/SoftFever/OrcaSlicer/issues/8942#issuecomment-2774116532

This started happening to me today also however, I'm on an M2 Macbook Air, MacOS Sequoia 15.4 (24E248).

I fully re-installed Orca from scratch (including renaming the ~/Library/Application Support/OrcaSlicer/ directory before starting the fresh install).

When attempting to login to my makerworld account it immediately crashed Orca Slicer.

This is with Orca Slicer v2.3.0.

Could you provide the crash log? You could find it in the "Console" app. Thanks!

— Reply to this email directly, view it on GitHub https://github.com/SoftFever/OrcaSlicer/issues/8942#issuecomment-2774116532, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDTZLVI2XFC5JWQVVC6VQE32XSG5RAVCNFSM6AAAAABZGGT2GSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZUGEYTMNJTGI . You are receiving this because you commented.Message ID: @.***>

[Noisyfox]

Unfortunately I don't think attachments works when you reply via email.

[githubuser853]

OrcaSlicer-2025-04-02-210049.ips.txt

[Noisyfox]

Thanks, that seems to be a different problem. Somehow it crashed when trying to launch an external browser for login. Could you raise another issue and provide few more details like what region did you select, what login method did you selected etc, so I could try reproduce with the same actions.

[githubuser853]

Thanks, that seems to be a different problem. Somehow it crashed when trying to launch an external browser for login. Could you raise another issue and provide few more details like what region did you select, what login method did you selected etc, so I could try reproduce with the same actions.

I have raised issue #9199

[github-actions[bot]]

Orca bot: this issue is stale because it has been open for 90 days with no activity.

[github-actions[bot]]

Orca bot: This issue was closed because it has been inactive for 7 days since being marked as stale.