Skip to content
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.

Sign up for GitHub

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

Jump to bottom

memory buildup with outdoor lidar scan #165

Open
ashsifat opened this issue Nov 9, 2021 · 0 comments
Open

memory buildup with outdoor lidar scan #165

ashsifat opened this issue Nov 9, 2021 · 0 comments

Comments

@ashsifat
Copy link

ashsifat commented Nov 9, 2021

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ashsifat