strap-9021
commented
1 month ago I don't think Wayland is the problem I'm using x11 with kde 6.0.4 and it gives me the same error. I also tried running Appimage but it also gives the same errors
this is the result of valgrind
==27306== Invalid read of size 8
==27306== at 0x1F00069: wxMediaCtrl2::wxMediaCtrl2(wxWindow*) (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x1E7CDA1: Slic3r::GUI::StatusBasePanel::create_monitoring_page() (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x1E81484: Slic3r::GUI::StatusBasePanel::StatusBasePanel(wxWindow*, int, wxPoint const&, wxSize const&, long, wxString const&) (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x1E8AA59: Slic3r::GUI::StatusPanel::StatusPanel(wxWindow*, int, wxPoint const&, wxSize const&, long, wxString const&) (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x190956E: Slic3r::GUI::MonitorPanel::init_tabpanel() (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x1909D03: Slic3r::GUI::MonitorPanel::MonitorPanel(wxWindow*, int, wxPoint const&, wxSize const&, long) (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x16D18D5: Slic3r::GUI::MainFrame::init_tabpanel() (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x16D2F55: Slic3r::GUI::MainFrame::MainFrame() (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x1688DDB: Slic3r::GUI::GUI_App::on_init_inner() (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x168A1F9: Slic3r::GUI::GUI_App::OnInit() (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x41D8E26: wxEntry(int&, wchar_t**) (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x164BC1A: Slic3r::GUI::GUI_Run(Slic3r::GUI::GUI_InitParams&) (in /opt/orca-slicer/bin/orca-slicer)
==27306== Address 0x18 is not stack'd, malloc'd or (recently) free'd
==27306==
==27306==
==27306== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==27306== Access not within mapped region at address 0x18
==27306== at 0x1F00069: wxMediaCtrl2::wxMediaCtrl2(wxWindow*) (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x1E7CDA1: Slic3r::GUI::StatusBasePanel::create_monitoring_page() (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x1E81484: Slic3r::GUI::StatusBasePanel::StatusBasePanel(wxWindow*, int, wxPoint const&, wxSize const&, long, wxString const&) (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x1E8AA59: Slic3r::GUI::StatusPanel::StatusPanel(wxWindow*, int, wxPoint const&, wxSize const&, long, wxString const&) (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x190956E: Slic3r::GUI::MonitorPanel::init_tabpanel() (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x1909D03: Slic3r::GUI::MonitorPanel::MonitorPanel(wxWindow*, int, wxPoint const&, wxSize const&, long) (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x16D18D5: Slic3r::GUI::MainFrame::init_tabpanel() (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x16D2F55: Slic3r::GUI::MainFrame::MainFrame() (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x1688DDB: Slic3r::GUI::GUI_App::on_init_inner() (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x168A1F9: Slic3r::GUI::GUI_App::OnInit() (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x41D8E26: wxEntry(int&, wchar_t**) (in /opt/orca-slicer/bin/orca-slicer)
==27306== by 0x164BC1A: Slic3r::GUI::GUI_Run(Slic3r::GUI::GUI_InitParams&) (in /opt/orca-slicer/bin/orca-slicer)
==27306== If you believe this happened as a result of a stack
==27306== overflow in your program's main thread (unlikely but
==27306== possible), you can try to increase the size of the
==27306== main thread stack using the --main-stacksize= flag.
==27306== The main thread stack size used in this run was 8388608.
==27306==
==27306== HEAP SUMMARY:
==27306== in use at exit: 35,910,415 bytes in 389,967 blocks
==27306== total heap usage: 1,157,710 allocs, 767,743 frees, 128,835,219 bytes allocated
==27306==
==27306== LEAK SUMMARY:
==27306== definitely lost: 249,284 bytes in 1,345 blocks
==27306== indirectly lost: 334,677 bytes in 13,417 blocks
==27306== possibly lost: 402,718 bytes in 1,318 blocks
==27306== still reachable: 32,246,512 bytes in 353,197 blocks
==27306== of which reachable via heuristic:
==27306== newarray : 32,160 bytes in 26 blocks
==27306== multipleinheritance: 5,624 bytes in 42 blocks
==27306== suppressed: 368 bytes in 2 blocks
==27306== Rerun with --leak-check=full to see details of leaked memory
==27306==
==27306== For lists of detected and suppressed errors, rerun with: -s
==27306== ERROR SUMMARY: 2 errors from 1 contexts (suppressed: 0 from 0)
Segmentation fault (core dumped)
4e576rt8uh9ij9okp
LucHeart
EBADBEEF
Ginkooo
Is there an existing issue for this problem?
OrcaSlicer Version
latest (v2.0) github
Operating System (OS)
Linux
OS Version
Arch Linux x86_64
Additional system information
OS: Arch Linux x86_64 Host: NUC13ANHi3 M89901-203 Kernel: 6.8.9-arch1-2 Uptime: 1 day, 22 hours, 28 mins Packages: 763 (pacman), 13 (flatpak) Shell: bash 5.2.26 Resolution: 3840x1600 WM: sway Theme: Adwaita [GTK2/3] Icons: Adwaita [GTK2/3] Terminal: foot CPU: 13th Gen Intel i3-1315U (8) @ 4.500GHz GPU: Intel Raptor Lake-P [UHD Graphics] Memory: 5450MiB / 15516MiB
Printer
Custom Manta M8P + CB1 + Klipper + Mainsail
How to reproduce
Actual results
Expected results
Start the slicer
Project file & Debug log uploads
Look actual results
Checklist of files to include
Anything else?
I run on Sway Wayland, maybe this is an issue.