-
Notifications
You must be signed in to change notification settings - Fork 201
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 on laser scan #213
Comments
@cottsay can you triage this issue? |
@jacobperron, you changed the faulting code pretty heavily in Eloquent (#121). The bit that is breaking was removed here: 046df60#diff-724ff79b0edd5a83f8a62b5e2ffa085cL378 Since you have context in this space, do you think this bug was fixed by your change? Could the relevant part of that change be backported to resolve the segfault? |
@maxlein Please provide exact steps to reproduce the problem. |
I am running eloquent now. Exactly this segfault I am not seeing anymore.
|
Seems this is happening when buffer is full. geometry2/tf2_ros/include/tf2_ros/message_filter.h Lines 420 to 426 in f1b00a4
|
Hmm.. glancing at the code, it doesn't look like we're locking access to
Just a shot in the dark: Maybe adding locks at these places would resolve the issue, like we do here,
|
I'm not able to reproduce any crashes. I tried playing around with Rviz and the dummy laser scanner (after looking at #485), but everything looks fine on my end. Are you able to reproduce the Rviz crash reliably? And if so, can you try changing the dummy robot code to match your setup to help me reproduce the issue? |
Reproducing reliably is a bit of a problem. The last times I got this, was with the global planner of nav2 stack. ( We got the error on live system and with gazebo ) |
I tried with dummy sensors code and I also get a crash:
|
Any news on this? |
I ran a modified dummy sensors laser publisher and RViz all night and didn't see a crash. I did see many "message dropped" logs. I had compiled with debug symbols. I'll try again without them. |
Seems I didn‘t write that I tried with eloquent deb package and branch sources. |
I've also tried eloquent debs, but using the default rmw implementation (Fast-RTPS), still no segfault. Is it also happening with Fast-RTPS too? When you run RViz, can you see the laser scans or are they not rendering? |
I believe that this is solved in the latest code, so I'm going to go ahead and close this. Feel free to reopen if you run into this again. |
I got some SIGABRT and SIGSEGV when using message filters in slam_toolbox.
Maybe you guys can better help out here.
The issue is described in detail here.
Basically what I saw is that memory usage is increasing and after ~1,2 hours the node crashes.
The text was updated successfully, but these errors were encountered: