Maybe the problem is not in the state file - it runs fine from loaded state if I omit the --begin parameter. Also, there seem to be different state file formats between 0.24 and 0.25 and the problem exists in both versions..
Thank you, Matej. On 8.1.2016 13:36, Matěj Kubička wrote: > Here goes the command that generated the sate file: > > sumo -c LuSTScenario.complete.mobility.sumo.cfg --save-state.times 30000 > -e 30010 > > Matej. > > > On 8.1.2016 12:44, Jakob Erdmann wrote: >> It looks as if the state file contains inconsistent data. >> The fastest work-around would be to avoid saving/loading states until >> the problem is fixed. >> If you can send me the command that was used to create the state file >> I can try to figure out what goes wrong. >> regards, >> Jakob >> >> 2016-01-07 23:22 GMT+01:00 Matěj Kubička >> <[email protected] >> <mailto:[email protected]>>: >> >> Update: the problem persists with 0.25.0. Also, if I omit the --begin >> parameter it won't die, but all the vehicles will teleport. M. >> >> On 7.1.2016 22:11, Matěj Kubička wrote: >> > Hello, >> > I have been trying to run sumo from saved state, but it dies first >> > simulationStep() after initialization. Its is killed on SIGABRT >> after >> > OS detects double free() or memory corruption. There is also >> plenty of >> > nonsense warning statements prior to that so we probably deal with a >> > dangling pointer messing with the memory. >> > >> > I am using sumo 0.24, built about 2 months back using sources from >> > SourceForge. I know there is a new version, but I didn't get to >> update >> > it yet. It was ran on Linux (3.13.0-74-generic kernel). >> > >> > The scenario and saved state is available for download from: >> > https://idata.lss.supelec.fr/index.php/s/mvHTQxVZ9sdwwCw >> > >> > You can run it using "sumo -c >> LuSTScenario.complete.mobility.sumo.cfg >> > --load-state state_30000.00.sbx -b 30000". I've verified that >> this is >> > with correct config file. >> > >> > For its output see enclosed stdout dump. I've ran valgrind's >> memcheck >> > on it so you can see where the problems originate from. First >> invalid >> > read is in MSLane::succLinkSec, folowed by warnings of type 'Vehicle >> > performs emergency stop [...] because there is no connection to the >> > next edge'. >> > >> > Thank you, >> > Matej. >> > >> > PS: Being a proper PhD student I am late to finish my >> experiments. So, >> > if there is a quick solution to this I would be happy to hear about >> > it.. :-) >> > >> > >> > >> > >> > >> >> ------------------------------------------------------------------------------ >> > >> > >> > _______________________________________________ >> > sumo-user mailing list >> > [email protected] >> <mailto:[email protected]> >> > https://lists.sourceforge.net/lists/listinfo/sumo-user >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> sumo-user mailing list >> [email protected] >> <mailto:[email protected]> >> https://lists.sourceforge.net/lists/listinfo/sumo-user >> >> > ------------------------------------------------------------------------------ > _______________________________________________ > sumo-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sumo-user ------------------------------------------------------------------------------ _______________________________________________ sumo-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sumo-user
