-
Notifications
You must be signed in to change notification settings - Fork 32
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
Segmentation fault in mapping thread #2
Comments
Thanks for your comment! It seems like is trying to access to a surface point that is out of the index in the vector. It seems a bug, I will take a look this weekend and I tell you if I find some bug on Monday, Thanks! |
I try it but did not get any segmentation fault. Can you send me more information to try to replay the error? |
Thank you for looking into it! Sure, I'll include more details below. SummaryCompiling
Modifications to 'simple_camera.cc' --> 'vi.cc'In a nutshell, here I basically replaced the loading of a video file with the loading of images from a folder). Dataset usedI used the Mandala0 dataset from
Running DefSLAMMy arguments for executing DefSLAM are
(1) Run with debugger
Running DefSLAM in debug mode, with gdb, I got the segfault error like I posted above (crash at the 30-somethingth frame). Some more output lines:
Thread info from gdb:
(2) Normal run without debugger
Interestingly though, I just tried to run DefSLAM normally without using gdb and got the same error, however the crash happens much sooner at around Frame 4
Remark(s)
Hope that was detailed enough so that you can reproduce the error. If I should include anything else, please let me know. Thanks again, and I really appreciate the help! |
Yes, there are three main threads, but there are small parts of the program that use internally multithreading like Ceres or the b-bspline third-party. I didn't get to repeat it yet :S, does it work fine with the simple_camera.cc? |
I see, that makes sense, thanks for clearing that up! |
Initially, if the flag save_result is False DefSLAMGT does not use the right image, if I do not forget something... To make it faster, you can always use the parallel mode uncommenting line 22 in modules/settings/set_MAC.h. Could you make sure you that the save_results flag is in False and it works with DefSLAMGT? |
Sure thing. Is it the Viewer.SaveResults parameter in the yaml file? If so, yes it was previously set to 1 and I have since changed it to 0. Tried it out with both DefSLAM and DefSLAMGT... DefSLAM still produces the same error regardless, but DefSLAMGT works fine once SaveResults was set to 0! |
Saw that you had a new commit changing the DefTracking.cc function; I just pulled and recompiled DefSLAM. Now DefSLAM runs without errors too... Closing with thanks! |
I'm happy it works now! I was taking a look and I think that there was some issue with the multithreading... I am not totally sure in any case. Let me know if the problem reappears eventually, |
Hello,
First of all thanks for providing the DefSLAM library! I'm getting a segmentation fault while running the DefSLAM executable (I
to load the mandala left camera images) with the Mandala0 dataset.
The sequence runs for several frames, but then crashes due to the segmentation fault.
.
The error occurs in the mapping thread, specifically at
Here is the gdb output:
The backtrace:
Any ideas what could have gone wrong here?
Thanks!
The text was updated successfully, but these errors were encountered: