Ask Your Question
0

how to find a memory leak in a manager nodelet in indigo

asked 2016-02-18 09:36:44 -0500

mpatalberta gravatar image

updated 2016-02-18 09:38:13 -0500

PID %CPU %MEM VIRT RSS 8961 153 1.2 1979600 198448 ? Ssl 12-Feb 2273:44:00 /opt/ros/indigo/lib/nodelet/nodelet manager __name:=kinect2tnl_cam1 __log:=/home/mpatalberta/.ros/log/e27c5f9e-d19e-11e5-81af-c03fd563536f/kinect2tnl_cam1-1.log 0 9420 8961 150 1.2 1979600 207868 ? Ssl 12-Feb 10703:12 /opt/ros/indigo/lib/nodelet/nodelet manager __name:=kinect2tnl_cam1 __log:=/home/mpatalberta/.ros/log/e27c5f9e-d19e-11e5-81af-c03fd563536f/kinect2tnl_cam1-1.log

The nodelet leaks 207868 - 198449 = 9040

How do I find the memory leak in the kinect2tnl_cam1-1 process?

Any ideas?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2016-02-18 10:55:32 -0500

updated 2016-02-18 10:56:20 -0500

Compiling as DEBUG and running the nodelet manager with an additional

launch-prefix="valgrind --tool=memcheck --leak-check=yes --track-origins=yes --log-file=YOUR_LOG_FILE_PATH_AND_NAME_HERE"

where it is launched in a launch file worked well for me before.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2016-02-18 09:36:44 -0500

Seen: 271 times

Last updated: Feb 18 '16