Segmentation fault: 11 on osx Big Sur with the latest nightly builds

[liftbag]

Version

2.3.55.3 fix build C/C++ CI macos #194
2.3.55.3 fix for naming thread when restricted to one thread. C/C++ CI macos #195
2.3.55.3 fix linux vuild C/C++ CI macos #196
2.3.53.3 #764 bridge acceleration only set when using bridge flow C/C++ CI macos #197

Operating system type + version

Behavior

The program closes at start with error: segmentation fault: 11
The latest working release is the 2.3.55.3 fix error in Voron.ini update ender3 manual mmu C/C++ CI macos #192

[cknic]

I have the same exact issue with the latest as well.

[liftbag]

The "revert deps missing C/C++ CI macos #199" version still doesn't work.

[liftbag]

I enclose the Apple crash report, maybe it is useful?

SuperSlicer segmentation fault 11.zip

[supermerill]

The crash report doesn't report anythign that i can fix, as it's in the wxwidget lib that the problem occur.
will merge with latest prusa update for macos.

[liftbag]

The crash report doesn't report anythign that i can fix, as it's in the wxwidget lib that the problem occur.
will merge with latest prusa update for macos.

Ok. So, something has changed with wxwidget from the fix error in Voron.ini update ender3 manual mmu C/C++ CI macos #192 version?

[issic]

Any update on this?

[issic]

Will this help?
change this in PrusaSlicer-master/deps/wxWidgets/wxWidgets.cmake:
-DwxUSE_LIBPNG=builtin
and rebuild deps and compile again.

and fixed in the latest master branch of PrusaSlicer, you must:
Delete all the previous build artifacts including the dependencies and start from scratch.

[gretel]

2.3.55.2 working fine on osx 11.3 Beta (20E5172i) for me.

[liftbag]

2.3.55.2 working fine on osx 11.3 Beta (20E5172i) for me.

2.3.55.2 works fine. The issue is related to the latest nightly builds based on 2.3.55.3.

[royal32]

Hey all,

I've figured out this crash- PrusaSlicer encountered the same thing in Nov. It's mentioned here, and was caused by a wxWidgets version that is no longer compatible with macOS 11 Big Sur. This commit which forces every mac build (not just M1 macs) to use wxWidgets 3.1.4-patched.
I've confirmed this and successfully built SS 2.3.55.5 on Big Sur 11.2.1.
I've tagged merill on discord so he is aware.

[royal32]

Prusa has now made 3.1.4-patched the version used to build on all platforms.
@supermerill can we get the new wxWidgets.cmake merged so that we have mac builds again :)

[gretel]

that'd be 🥳

[LazaroFilm]

Hey all,

I've figured out this crash- PrusaSlicer encountered the same thing in Nov. It's mentioned here, and was caused by a wxWidgets version that is no longer compatible with macOS 11 Big Sur. This commit which forces every mac build (not just M1 macs) to use wxWidgets 3.1.4-patched.
I've confirmed this and successfully built SS 2.3.55.5 on Big Sur 11.2.1.
I've tagged merill on discord so he is aware.

Could you share your build?

[royal32]

Hey all,
I've figured out this crash- PrusaSlicer encountered the same thing in Nov. It's mentioned here, and was caused by a wxWidgets version that is no longer compatible with macOS 11 Big Sur. This commit which forces every mac build (not just M1 macs) to use wxWidgets 3.1.4-patched.
I've confirmed this and successfully built SS 2.3.55.5 on Big Sur 11.2.1.
I've tagged merill on discord so he is aware.

Could you share your build?

Here you go

[gretel]

@royal32 thanks! still crashing (on slicing) on 11.3 on a m1 mac.

Thread 10 Crashed:: slic3r_BgSlcPcs
0   libc++.1.dylib                	0x00007fff204b8437 std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::operator=(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) + 9
1   com.merill.slic3r/            	0x0000000102de7f25 Slic3r::GCodeProcessor::apply_config(Slic3r::PrintConfig const&) + 421
2   com.merill.slic3r/            	0x0000000102e0c15a Slic3r::GCode::_do_export(Slic3r::Print&, __sFILE*, std::__1::function<void (std::__1::vector<Slic3r::ThumbnailData, std::__1::allocator<Slic3r::ThumbnailData> >&, std::__1::vector<Eigen::Matrix<double, 2, 1, 2, 2, 1>, std::__1::allocator<Eigen::Matrix<double, 2, 1, 2, 2, 1> > > const&, bool, bool, bool, bool)>) + 122
3   com.merill.slic3r/            	0x0000000102e0aa26 Slic3r::GCode::do_export(Slic3r::Print*, char const*, Slic3r::GCodeProcessor::Result*, std::__1::function<void (std::__1::vector<Slic3r::ThumbnailData, std::__1::allocator<Slic3r::ThumbnailData> >&, std::__1::vector<Eigen::Matrix<double, 2, 1, 2, 2, 1>, std::__1::allocator<Eigen::Matrix<double, 2, 1, 2, 2, 1> > > const&, bool, bool, bool, bool)>) + 1014
4   com.merill.slic3r/            	0x000000010301be31 Slic3r::Print::export_gcode(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, Slic3r::GCodeProcessor::Result*, std::__1::function<void (std::__1::vector<Slic3r::ThumbnailData, std::__1::allocator<Slic3r::ThumbnailData> >&, std::__1::vector<Eigen::Matrix<double, 2, 1, 2, 2, 1>, std::__1::allocator<Eigen::Matrix<double, 2, 1, 2, 2, 1> > > const&, bool, bool, bool, bool)>) + 657
5   com.merill.slic3r/            	0x0000000103334fba Slic3r::BackgroundSlicingProcess::process_fff() + 426
6   com.merill.slic3r/            	0x0000000103337a20 Slic3r::BackgroundSlicingProcess::thread_proc() + 304
7   com.merill.slic3r/            	0x00000001033393e2 boost::detail::thread_data<Slic3r::BackgroundSlicingProcess::start()::$_1>::run() + 18
8   com.merill.slic3r/            	0x000000010385c118 boost::(anonymous namespace)::thread_proxy(void*) + 120
9   libsystem_pthread.dylib       	0x00007fff2051e954 _pthread_start + 224
10  libsystem_pthread.dylib       	0x00007fff2051a4a7 thread_start + 15

[supermerill]

someone here can try the latest nightly build?
https://github.com/supermerill/SuperSlicer/suites/2281540987/artifacts/47710605

[royal32]

someone here can try the latest nightly build?
https://github.com/supermerill/SuperSlicer/suites/2281540987/artifacts/47710605https://github.com/supermerill/SuperSlicer/suites/2281540987/artifacts/47710605

Works great on macOS 11.2.1! :D

[gretel]

@supermerill thanks; on 11.3 it's still crashing on slicing:

Thread 10 Crashed:: slic3r_BgSlcPcs
0   libc++.1.dylib                	0x00007fff204c8437 std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::operator=(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) + 9
1                                 	0x0000000103125dd5 Slic3r::GCodeProcessor::apply_config(Slic3r::PrintConfig const&) + 421
2                                 	0x000000010314a00a Slic3r::GCode::_do_export(Slic3r::Print&, __sFILE*, std::__1::function<void (std::__1::vector<Slic3r::ThumbnailData, std::__1::allocator<Slic3r::ThumbnailData> >&, std::__1::vector<Eigen::Matrix<double, 2, 1, 2, 2, 1>, std::__1::allocator<Eigen::Matrix<double, 2, 1, 2, 2, 1> > > const&, bool, bool, bool, bool)>) + 122
3                                 	0x00000001031488d6 Slic3r::GCode::do_export(Slic3r::Print*, char const*, Slic3r::GCodeProcessor::Result*, std::__1::function<void (std::__1::vector<Slic3r::ThumbnailData, std::__1::allocator<Slic3r::ThumbnailData> >&, std::__1::vector<Eigen::Matrix<double, 2, 1, 2, 2, 1>, std::__1::allocator<Eigen::Matrix<double, 2, 1, 2, 2, 1> > > const&, bool, bool, bool, bool)>) + 1014
4                                 	0x000000010335a3c9 Slic3r::Print::export_gcode(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, Slic3r::GCodeProcessor::Result*, std::__1::function<void (std::__1::vector<Slic3r::ThumbnailData, std::__1::allocator<Slic3r::ThumbnailData> >&, std::__1::vector<Eigen::Matrix<double, 2, 1, 2, 2, 1>, std::__1::allocator<Eigen::Matrix<double, 2, 1, 2, 2, 1> > > const&, bool, bool, bool, bool)>) + 649
5                                 	0x000000010367374a Slic3r::BackgroundSlicingProcess::process_fff() + 426
6                                 	0x00000001036761b0 Slic3r::BackgroundSlicingProcess::thread_proc() + 304
7                                 	0x0000000103677b72 boost::detail::thread_data<Slic3r::BackgroundSlicingProcess::start()::$_1>::run() + 18
8                                 	0x0000000103b9b7b8 boost::(anonymous namespace)::thread_proxy(void*) + 120
9   libsystem_pthread.dylib       	0x00007fff2052e954 _pthread_start + 224
10  libsystem_pthread.dylib       	0x00007fff2052a4a7 thread_start + 15

besides, the url you posted is borked :)

[supermerill]

@gretel i don't see what's wrong where it crashs. Can you share your project file that crashs on slicing? Maybe it's not something macos-related.

besides, the url you posted is borked :)

Was too ctrl+v happy.

[gretel]

@gretel i don't see what's wrong where it crashs. Can you share your project file that crashs on slicing? Maybe it's not something macos-related.

sure, here's the stl:
maquet.stl.zip

[liftbag]

The last nightly #944 Spiral vase mode should turn off some of SuperSlicer's new settings opens without errors. I think we can close the issue.

[gretel]

@liftbag all the builds referred to in this issue open on big sur; but crash on slicing for me.

[supermerill]

@gretel

sure, here's the stl:

I need the project file : before clicking on the "clice" button that would makes it crash, please click on file-> save as and zip & paste the file here.

[gretel]

I need the project file : before clicking on the "clice" button that would makes it crash, please click on file-> save as and zip & paste the file here.

@supermerill there you go:
maquet.3mf.zip

[gretel]

@supermerill thanks