-
Notifications
You must be signed in to change notification settings - Fork 271
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
RAM filling up rapidly #11
Comments
I am facing the same issue too, the huge memory consumption mainly comes from the odom estimation node. |
Hi did you find any solution for this problem? |
I faced a similar issue while running floam on the Newer College dataset recorded with an Ouster OS1-64. |
Hey @JanQuenzel I am also facing issues with queues filling up with my Ouster OS0-64. Have you implemented the changes you suggested yet by any chance? Cheers |
OK I just saw commit 5f592a2106400b775e00ed2d04af177af973b1d9 in your forked floam repo. I'll check it out :-) |
Hi
I am testing FLOAM with the ouster 64 Lidar ROS dataset available from their website.
I have a 32 GB RAM, running the ROS melodic. The FLOAM is quickly filling up all the RAM within minutes of running the node.
Can you suggest something to solve this?
Thanks
The text was updated successfully, but these errors were encountered: