-
Notifications
You must be signed in to change notification settings - Fork 2k
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
slicer GUI build not slicing on Mac OS (compilation issues) - crashes on gyroid infill #3182
Comments
Could you try to run the executable with parameter |
@Anmol6 I have the same issue . Please let me know if you have made some progress. Thanks |
@Anmol6 @norre-daroy Could either of you provide that log? Also try to go to Print Settings->Infill and choose different pattern than Gyroid (which is the default in our profiles), there was recently an issue with it. |
@Anmol6 @norre-daroy Could you please retest with latest master 32d7947 ? A serious bug has been fixed with dd59945, there is a chance it was a cause of your crashes as well. |
@lukasmatena I tried to build it again with the latest master 32d7947 changes and I got these errors |
@norre-daroy What you posted is just a report that an error appeared at some point before. You must upscroll to see the actual error message. The "expected unqualified-id" sounds serious, but I cannot see where exactly it comes from (could be the Config.cpp or anything included by it). The commit builds fine on my Ubuntu 16.04, but the master branch is under rapid development and it is possible that some recent change broke build on OSX (or at least under some circumstances). I need to see the whole |
@lukasmatena Sorry, I upscroll and pasted the message Scanning dependencies of target imgui |
@norre-daroy Thanks, I tried to fix it with bbb519a. Please, try that. |
@lukasmatena The fix bbb519a worked. But the slicer GUI still not slicing. Below is the log Norres-MacBook-Air:build ninja.n$ /Users/ninja.n/WebDev/ORDSolutions/PrusaSlicer/build/src/prusa-slicer --loglevel 9
< HTTP/1.1 200 OK
< HTTP/1.1 200 OK
< HTTP/1.1 200 OK
|
@norre-daroy Thank you very much. The log indicates it crashed during infill generation, which may be a sign of more bugs in recently reworked gyroid infill calculation. You can try to verify that by turning the infill off (Print Settings->Infill density - set to 0%) or setting different infill than gyroid. Could you please enclose a 3MF (File->Save As) so we can try to reproduce the issue here? (The 3MF contains the model and all config.) Thanks. |
@lukasmatena It didn't crash when I turned off the infill and changed the infill gyroid. I also enclosed the 3MF. However, I also noticed that it hangs when 'generating g-code' in the terminal |
@norre-daroy Thanks. It does not crash on my Ubuntu 16.04, but @FidelCapo managed to reproduce it on OSX. I enclose an ASAN report that he provided for reference. Probably @bubnikv will be interested. Note: it is necessary to turn on gyroid infill after loading the 3MF. ASAN report==55892==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x603000c80d60 at pc 0x00010fc5b88e bp 0x7000052d65f0 sp 0x7000052d65e8 READ of size 8 at 0x603000c80d60 thread T17 #0 0x10fc5b88d in Slic3r::mark_boundary_segments_touching_infill(std::__1::vector >, std::__1::allocator > > > const&, std::__1::vector >, std::__1::allocator > > >&, Slic3r::BoundingBox const&, std::__1::vector > const&, double, double)::Visitor::operator()(int, int) (PrusaSlicer:x86_64+0x10029888d) #1 0x10fc52c17 in void Slic3r::EdgeGrid::Grid::visit_cells_intersecting_line >, std::__1::allocator > > > const&, std::__1::vector >, std::__1::allocator > > >&, Slic3r::BoundingBox const&, std::__1::vector > const&, double, double)::Visitor>(Slic3r::Point, Slic3r::Point, Slic3r::mark_boundary_segments_touching_infill(std::__1::vector >, std::__1::allocator > > > const&, std::__1::vector >, std::__1::allocator > > >&, Slic3r::BoundingBox const&, std::__1::vector > const&, double, double)::Visitor&) const (PrusaSlicer:x86_64+0x10028fc17) #2 0x10fc52586 in Slic3r::mark_boundary_segments_touching_infill(std::__1::vector >, std::__1::allocator > > > const&, std::__1::vector >, std::__1::allocator > > >&, Slic3r::BoundingBox const&, std::__1::vector > const&, double, double) (PrusaSlicer:x86_64+0x10028f586) #3 0x10fc551e4 in Slic3r::Fill::connect_infill(std::__1::vector >&&, Slic3r::ExPolygon const&, std::__1::vector >&, Slic3r::FillParams const&) (PrusaSlicer:x86_64+0x1002921e4) #4 0x10fc6ba84 in Slic3r::FillGyroid::_fill_surface_single(Slic3r::FillParams const&, unsigned int, std::__1::pair const&, Slic3r::ExPolygon&, std::__1::vector >&) (PrusaSlicer:x86_64+0x1002a8a84) #5 0x10fc51125 in Slic3r::Fill::fill_surface(Slic3r::Surface const*, Slic3r::FillParams const&) (PrusaSlicer:x86_64+0x10028e125) #6 0x10fc45093 in Slic3r::Layer::make_fills() (PrusaSlicer:x86_64+0x100282093) #7 0x1103821ec in tbb::interface9::internal::start_for, Slic3r::PrintObject::infill()::$_3, tbb::auto_partitioner const>::execute() (PrusaSlicer:x86_64+0x1009bf1ec) #8 0x111a036a8 in tbb::internal::custom_scheduler::local_wait_for_all(tbb::task&, tbb::task*) (PrusaSlicer:x86_64+0x1020406a8) #9 0x1119f7059 in tbb::internal::arena::process(tbb::internal::generic_scheduler&) (PrusaSlicer:x86_64+0x102034059) #10 0x1119fe424 in tbb::internal::market::process(rml::job&) (PrusaSlicer:x86_64+0x10203b424) #11 0x1119ff437 in tbb::internal::rml::private_worker::run() (PrusaSlicer:x86_64+0x10203c437) #12 0x1119ff3d8 in tbb::internal::rml::private_worker::thread_routine(void*) (PrusaSlicer:x86_64+0x10203c3d8) #13 0x7fff73b2d2ea in _pthread_body (libsystem_pthread.dylib:x86_64+0x32ea) #14 0x7fff73b30248 in _pthread_start (libsystem_pthread.dylib:x86_64+0x6248) #15 0x7fff73b2c40c in thread_start (libsystem_pthread.dylib:x86_64+0x240c) |
Version
version_2.1.0-485-g050a9adf3
Operating system type + version
OS: Mac OS Mojave 10.14.6
Behavior
So I built the slicer for mac os following the instructions provided. When I click on the
build/src/prusa-slicer
file, the gui opens just fine. However, when I load any stl and try to slice it, I get a segmentation fault. Here's what the corresponding terminal showsWould appreciate any help!
Is this a new feature request? No
The text was updated successfully, but these errors were encountered: