You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have recently discovered a GPU memory leak when using the ROS node. I haven't found the time yet to fix this.
Symptoms:
GPU memory allocated by ROS node increases with the number of messages processed and crashes after a while (depending on GPU memory size) with a cudnn allocation error:
When playing 10 fps rosbags we experienced an increase in memory from ~1.3GB over 15 minutes.
Possible problem:
I suspect that this is a problem that arises somewhere at the interface between NVIDIA TensorRT and Instance Stixels. We haven't experienced this with the PyTorch based Cityscapes evaluation script.
The text was updated successfully, but these errors were encountered:
We have recently discovered a GPU memory leak when using the ROS node. I haven't found the time yet to fix this.
Symptoms:
GPU memory allocated by ROS node increases with the number of messages processed and crashes after a while (depending on GPU memory size) with a cudnn allocation error:
When playing 10 fps rosbags we experienced an increase in memory from ~1.3GB over 15 minutes.
Possible problem:
I suspect that this is a problem that arises somewhere at the interface between NVIDIA TensorRT and Instance Stixels. We haven't experienced this with the PyTorch based Cityscapes evaluation script.
The text was updated successfully, but these errors were encountered: