Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Carla [0.9.2] getting slower after each repetition of scenario_runner

See original GitHub issue

In scenario_runner --version 0.1. I found that the FPS of Carla Server drops after every repetition. I think the problem being that actors are not properly destroyed from the server. After the end of scenario I get this output:

LIFETIME: WARNING! the following objects were not destructed. 
LIFETIME: Actor 168 (sensor.other.collision) still alive. 
LIFETIME: tcp client 94 still alive. 
LIFETIME: Actor 163 (vehicle.tesla.model3) still alive. 
LIFETIME: tcp client 89 still alive. 
LIFETIME: tcp client 88 still alive. 
LIFETIME: Actor 159 (sensor.other.collision) still alive. 
LIFETIME: Actor 155 (vehicle.tesla.model3) still alive. 
LIFETIME: Actor 152 (sensor.other.collision) still alive. 
LIFETIME: tcp client 82 still alive. 
LIFETIME: Actor 151 (sensor.other.collision) still alive. 
LIFETIME: Actor 148 ( still alive. 
LIFETIME: Actor 147 (vehicle.tesla.model3) still alive. 
LIFETIME: tcp client 77 still alive. 
LIFETIME: Actor 144 (sensor.other.collision) still alive. 
LIFETIME: tcp client 76 still alive. 
LIFETIME: Actor 143 (sensor.other.collision) still alive. 
LIFETIME: Actor 167 (sensor.other.collision) still alive. 
LIFETIME: Actor 139 (vehicle.tesla.model3) still alive. 
LIFETIME: tcp client 28 still alive. 
LIFETIME: Actor 164 ( still alive. 
LIFETIME: Actor 120 (sensor.other.collision) still alive. 
LIFETIME: Actor 55 (sensor.other.collision) still alive. 
LIFETIME: Actor 156 ( still alive. 
LIFETIME: Actor 136 (sensor.other.collision) still alive. 
LIFETIME: tcp client 23 still alive.

I am doing actor.destroy() and actor = None after each repetition and they are being destroyed (I cannot see them in the server) but the memory still not being released and I get above output.

Could someone help me how to destroy the actors properly??

Issue Analytics

  • State:open
  • Created 5 years ago
  • Reactions:2
  • Comments:5 (1 by maintainers)

github_iconTop GitHub Comments

danmoucommented, Feb 28, 2019

I’m seeing the same problem when using Carla from the normal client API.

TigerStone93commented, Nov 1, 2022

Is this problem solved?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Carla 0.9.2 gets slower after every iteration of scenario_runner
I am running Carla in benchmark mode with fps = 10hz and after every repetition framerate drops (frame rate = 3 Hz after...
Read more >
CARLA Talks 2020 - Introducing ScenarioRunner - YouTube
Start creating scenarios and routes to train or validate your AD stacks using the ScenarioRunner module.
Read more >
Release Notes - CARLA ScenarioRunner
Fixed a bug with repetitions / scenario groups causing the simulation to crash after the second one. Fixed use of OSC Parameters as...
Read more >
CARLA ScenarioRunner - Read the Docs
Sign up for our newsletter to get our latest blog updates delivered to your inbox weekly. Email. Subscribe.
Read more >
1 Simulation Framework for Testing Autonomous Vehicles in a ...
purpose, a realistic virtual simulation environment was created using the CARLA. Simulator. Other edge case scenarios such as distracted pedestrians, ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found