Memory leak about fast_lio HOT 15 CLOSED

@Ecstasy-EC sorry, https://drive.google.com/drive/folders/1blQJuAB4S80NwZmpM6oALyHWvBljPSOE?usp=sharing

The 20 gig bag

I will look into it but please patiently wait for several days.

from fast_lio.

I’ve detected that its cause is something related to rviz visualization but I don’t know how to solve it

from fast_lio.

Does the memory leak appear when you close the rviz? The rviz will accumulate point clouds for visualization thus increasing the memory consumption.

from fast_lio.

If i use rviz:=false , the memory leakage slows down, but still exist and happens
@Ecstasy-EC

from fast_lio.

@Ecstasy-EC I am waiting for your response, this issue is really important I guess , I have noticed that some people had the same issue before, your code is working really good but the memory leak prevents us to enjoy it :)

from fast_lio.

@Ecstasy-EC I am waiting for your response, this issue is really important I guess , I have noticed that some people had the same issue before, your code is working really good but the memory leak prevents us to enjoy it :)

Hi @SabraHashemi. Sorry for my late reply. Would you please provide me with the memory-time plot to see how fast it increases? And is the odometry working normally? Besides, the last person who met this problem solved it by updating with the latest commit in this repo. Did you check that everything was on the latest version?

from fast_lio.

@Ecstasy-EC actually I’ve got the code recently ( 2 weeks ago) so I’m using your latest version and I’m using melodic Ros, odometry is working normally
About memory time plot, i will provide it soon , but to know more about my issue
I’m using a 16 g Ram , and with a data from velodyne in the repo, and i can see that every 2 sec memory usage will increased about 0.01 gig

from fast_lio.

@Ecstasy-EC actually I’ve got the code recently ( 2 weeks ago) so I’m using your latest version and I’m using melodic Ros, odometry is working normally About memory time plot, i will provide it soon , but to know more about my issue I’m using a 16 g Ram , and with a data from velodyne in the repo, and i can see that every 2 sec memory usage will increased about 0.01 gig

Quite weird. Could you please also provide me with a rosbag and a config file in your test? Which type of LiDAR do you use?

from fast_lio.

I’m using velodyne HE 32 data you have provided in the repo ( the ine which is about 22 gig)
And your velodyne.yaml file , the only differences is that i have changed lidar topic to : points_raw
The imu topic: imu_raw
Save pcd to false
@Ecstasy-EC

from fast_lio.

I know that you are busy, so consider this as a kind reminder @Ecstasy-EC

from fast_lio.

I know that you are busy, so consider this as a kind reminder @Ecstasy-EC

Could you provide your rosbag for me to have a look?

from fast_lio.

@Ecstasy-EC sorry,
https://drive.google.com/drive/folders/1blQJuAB4S80NwZmpM6oALyHWvBljPSOE?usp=sharing

The 20 gig bag

from fast_lio.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from fast_lio.

Hi @Ecstasy-EC
Any updates on this issue?

from fast_lio.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from fast_lio.