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

[OrcaSlicer 2.1.1] Segfault when going to machine's g-code twice #6069

Closed
3 tasks done
brunetton opened this issue Jul 9, 2024 · 10 comments
Closed
3 tasks done

[OrcaSlicer 2.1.1] Segfault when going to machine's g-code twice #6069

brunetton opened this issue Jul 9, 2024 · 10 comments
Labels
bug Something isn't working stale

Comments

@brunetton
Copy link

brunetton commented Jul 9, 2024

Is there an existing issue for this problem?

  • I have searched the existing issues

OrcaSlicer Version

2.1.1

Operating System (OS)

Linux

OS Version

Ubuntu 23.10

Additional system information

Intel Core i5-8250U 64 / RAM 16 GiB / Intel UHD Graphics 620

Printer

Personalized version of Ender 3

How to reproduce

  1. open OrcaSlicer
  2. open printer configuration
  3. goto g-code
  4. close printer configuration
  5. open printer configuration again
  6. goto g-code

Actual results

the app crashes, segmentation fault in console logs

Expected results

I should be able to visualize and edit printer's G-code

Project file & Debug log uploads

Untitled.zip

[error]	2024-07-09 13:23:15.695937[Thread 0x0000712fe05db380]:calc_exclude_triangles:Unable to create exclude triangles
[error]	2024-07-09 13:23:15.712983[Thread 0x0000712fdd1246c0]:Unable to open the file/tmp/.mount_OrcaSl7Eg1XY/resources/calib/tolerance_test/OrcaToleranceTest.stl
[warning]	2024-07-09 13:23:16.427503[Thread 0x0000712fe05db380]:01:23:16 PM: Warning: Error running JavaScript: Unsupported result type
[warning]	2024-07-09 13:23:16.497883[Thread 0x0000712fe05db380]:01:23:16 PM: Warning: Error running JavaScript: Unsupported result type
[warning]	2024-07-09 13:23:16.502055[Thread 0x0000712fe05db380]:01:23:16 PM: Warning: Error running JavaScript: Unsupported result type
[warning]	2024-07-09 13:23:16.611137[Thread 0x0000712fe05db380]:01:23:16 PM: Warning: Error running JavaScript: Unsupported result type
[error]	2024-07-09 13:23:18.743566[Thread 0x0000712fe05db380]:calc_exclude_triangles:Unable to create exclude triangles
[warning]	2024-07-09 13:23:18.815036[Thread 0x0000712fe05db380]:get_version, get_version not supported,return 00.00.00.00!
[error]	2024-07-09 13:23:20.262547[Thread 0x0000712fe05db380]:calc_exclude_triangles:Unable to create exclude triangles

Checklist of files to include

  • Log file
  • Project file

Anything else?

@brunetton brunetton added the bug Something isn't working label Jul 9, 2024
@timnolte
Copy link

I believe this is a duplicate of #6020

@henrivdr
Copy link
Contributor

This could be a duplicate, but my reproduction steps are closer to this one.

@serhii-nakon
Copy link
Contributor

I have the same issue

@serhii-nakon
Copy link
Contributor

For me last working stable version is 2.0.0, and not working 2.1.0 and newer

@serhii-nakon
Copy link
Contributor

Looks like it related with new Mesa due my friend use 2.1.1 with Debian 12 and main differences are - mesa, kernel, desktop environment

kernel: my - 6.9.7 (git), friends - default Debian's 6.1.99
mesa: my - 24.1.2 (git), friends - default Debian's 22.3.6
DE: my - Gnome, friends - KDE (both default Debian's)

And that are all differences between our systems.

@JooJooBee666
Copy link

JooJooBee666 commented Jul 21, 2024

Same here. 2.1.1 just seg faults shortly after opening.
KDE 6.1, X11, Latest Mesa
AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 18.1.6, DRM 3.57, 6.9.9-200.fc40.x86_64) (0x73df)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.3.0-devel

Tried older versions, but the result is the same, segfault right after opening. Version 2.0.0, 2.1.0 and 2.1.1 app images. Very sad today. :(

@serhii-nakon
Copy link
Contributor

Looks like it related with new Mesa due my friend use 2.1.1 with Debian 12 and main differences are - mesa, kernel, desktop environment

kernel: my - 6.9.7 (git), friends - default Debian's 6.1.99 mesa: my - 24.1.2 (git), friends - default Debian's 22.3.6 DE: my - Gnome, friends - KDE (both default Debian's)

And that are all differences between our systems.

I just checked with older Mesa and issue still exist, also I tried with Xorg and Wayland - still exist, and looks like one main difference between my system and my friends is DE or list of libraries.

@SoftFever Where I can find debug symbols for latest builds? To get more information why it segfault in my case. I found that latest build with debug symbols was 2.0.0 but for me sqgfault starts from 2.1.0

@JooJooBee666
Copy link

I's working again for me after updating to Plasma 6.1.3 and Mesa.

AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 18.1.6, DRM 3.57, 6.9.9-200.fc40.x86_64)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.3.0-devel
Release : 0.3.20240723.10.8f9a157.fc40

Copy link

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

@github-actions github-actions bot added the stale label Oct 22, 2024
Copy link

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

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale
Projects
None yet
Development

No branches or pull requests

5 participants