Re: [sumo-user] TraCI quits on "Error: bad allocation"

[Jakob Erdmann <namdre.sumo@xxxxxxxxx>]

No. The next step would be to run sumo in a debugger and the connecting your traci script.

(see https://sumo.dlr.de/docs/TraCI/Interfacing_TraCI_from_Python.html#debugging_a_traci_session_on_linux)

If you can manage to put together a small scenario that crashes "reliably"  (i.e after running it a few time for no more than a few minutes) and send it to me, I would also take a look.

Am Di., 19. Mai 2020 um 15:39 Uhr schrieb marcelreppi <marcelreppi@xxxxxxxxx>:

No not really... only about 180MB.

When I try to change the arrival times or the amount of trips it affects the
error.
Sometimes it doesn't occur at all, sometimes earlier, sometimes later.

What also happens very often is that TraCI crashes only saying
"traci.exceptions.FatalTraCIError: connection closed by SUMO".
In the past sometimes I was able to fix it by making sure objects are being
unsubscribed from before removing them from the simulation but right now I
really don't understand what is happening.
Is there any way to get more detailed TraCI logs?

Thanks a lot!

Best regards
Marcel




--
Sent from: http://sumo-user-mailing-list.90755.n8.nabble.com/
_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user