memory buildup with outdoor lidar scan #165
Description
Has anyone had the issue of memory buildup with outdoor velodyne lidar scan with LOAM? I am seeing the memory consumption of the system going up with the time as LOAM is run with Lidar data from velodyne. Any reason for this? Is this because of 3D map storage? I cannot figure out if this is a memory leak or not as I don't see any memory allocation in the code.