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.

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

robot_reach_study_node crash if there are too much points in point cloud #62

Open
vicltz opened this issue Aug 23, 2023 · 0 comments
Open

Comments

@vicltz
Copy link

vicltz commented Aug 23, 2023

I noticed that the robot_reach_study_node crashes if there are too much points in the point cloud. I thought it was a problem with my robot, but I was able to reproduce it with the demo.

The crash actually comes from the system that kills the process, because it consumes too much RAM (exit code -9)

The crash can occur either during the reach_study (+6000 points in the point cloud , my setup has 16GB of RAM) , or during the optimization loop (+4000 points in the point cloud).

I am not sure if it might be because of the design of the reach algorithm by itself or because of a memory leak your might have.

Note: probably related to the boost object that stores the results, because I was able to get this type of crash (too much RAM used) by loading reach.db.xml with a lot of markers inside (since the reach_study and optimization was already done).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant