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

Erroneous use of sensor_msgs::ImageConstPtr leads to extravagant memory overflow #7

Open
zx1239856 opened this issue Sep 22, 2019 · 1 comment

Comments

@zx1239856
Copy link

zx1239856 commented Sep 22, 2019

In our experiment with Nvidia Jetson TX2, memory utilization of vins-gpu could go up to 85% (as mentioned in #2 ) and would eventually escalate sigkill. After we examined the main entry of ROS node rosNodeTest.cpp, we found you have used queue<sensor_msgs::ImageConstPtr> in line 29,30, which may bring about miserable results such as failure of memory deallocation of sensor_msgs::Image, thus causing memory panic.
After making some minor changes, i.e. using queue<cv::Mat> and convert msgs just in time, this problem can be addressed. Note: extra care should be taken since cv::Mat wouldn't save extra info such as timestamp, which means you have to store it somewhere else manually.
Hope this helps

@zx1239856 zx1239856 changed the title Erroneous use of sensor_msgs::ImageConstPtr leads to extravagent memory overflow Erroneous use of sensor_msgs::ImageConstPtr leads to extravagant memory overflow Sep 22, 2019
@mmp52
Copy link

mmp52 commented Jan 16, 2020

@zx1239856 I have also noticed a memory leakage, after running vins in nvidia xavier. Have you explicitly modified the code and solved the problem ?

Thanks,
Metin

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

2 participants