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

GPU Memory release #7103

Open
Mariusmarten opened this issue Jan 31, 2024 · 2 comments
Open

GPU Memory release #7103

Mariusmarten opened this issue Jan 31, 2024 · 2 comments
Assignees

Comments

@Mariusmarten
Copy link

Mariusmarten commented Jan 31, 2024

I observed the following problem: Carla does not release the GPU 'freed' by destroying sensors.

CARLA version: 0.9.14

Platform/OS: carlasim/carla:0.9.14 docker image

Problem: GPU memory usage keeps on increasing. Once spawned sensors continue to occupy GPU space after being destroyed, the space is partially freed up before the GPU is almost full but this leads still to the data generation crashing at some point. Just to be clear the number of actors (vehicles and cameras) stays constant they are just spawned and destroyed multiple times.

The error I get is:

Signal 11 caught.
Malloc Size=65538 LargeMemoryPoolOffset=65554
CommonUnixCrashHandler: Signal=11
Engine crash handling finished; re-raising signal 11 for the default handler. Good bye.
Segmentation fault

Expected: The GPU is directly freed up when the sensor is destroyed.

Steps to reproduce: Create and destroy sensors multiple times (e.g., spawn 24 camera sensors and destroy them 100 times in a loop).

Other information: I could not find further information about others experiencing similar problems or whether this is potentially expected behavior.

Potentially related to: this, this, this and this

@Mariusmarten
Copy link
Author

Mariusmarten commented Mar 11, 2024

Hi, I am on a Linux-based server system in a docker build on carlasim/carla:0.9.14 using this whl carla-0.9.14-cp38-cp38-manylinux_2_27_x86_64.whl. I have no problem running Carla otherwise. For me, the crash is very deterministically due to the not-released GPU memory when sensors are deleted and respawnd.

@Blyron
Copy link
Contributor

Blyron commented Nov 6, 2024

This should be fixed in latest versions of ue4-dev branch

@Blyron Blyron self-assigned this Nov 6, 2024
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

3 participants
@Mariusmarten @Blyron and others