You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running OpenVINS on ROS1 with stereo data from the RealSense T265 camera. I experienced sporadic crashing / freezing of the VIO under heavy CPU load.
According to GDB, sometimes a segmentation fault happens at
(and sometimes the VIO freezes with one of the threads being in the same location). I assume some elements are deleted from the _clones_IMU map by another thread while iterating over it.
where I assume the elements are being deleted from the map. So far it seems to have fixed the issue (I'm testing it by running OpenVINS along with CPU and fileio benchmarks using sysbench). Should I submit a pull request?
The text was updated successfully, but these errors were encountered:
Ok, I made the pull request. I tested it on some rosbag from the euroc dataset running along with the CPU benchmark as well and it seems to fix the issue.
I'm running OpenVINS on ROS1 with stereo data from the RealSense T265 camera. I experienced sporadic crashing / freezing of the VIO under heavy CPU load.
According to GDB, sometimes a segmentation fault happens at
open_vins/ov_msckf/src/state/State.h
Line 67 in 98c5525
_clones_IMU
map by another thread while iterating over it.Segmentation fault:
Backtrace:
I added mutex locks before the
for
cycleopen_vins/ov_msckf/src/state/State.h
Line 67 in 98c5525
open_vins/ov_msckf/src/state/StateHelper.cpp
Line 622 in 98c5525
sysbench
). Should I submit a pull request?The text was updated successfully, but these errors were encountered: