[sumo-user] Leaked object

[Valber S. <va...@go...>]

Hello, all!

   Has anybody run into this problem with SUMO? Here's what happens:

caesar@caesar-laptop:~/sumo-0.12.0/examples/sumo/busses$ sumo -c
test.sumo.cfg
Loading configuration... done.
MSDetectorControl: clearing myMsgLoops
MSNet: clearing myMsgEmitter
MSNet: clearing msgEmitVec
Leaked object at 0x913d680 (size 56, MSVehicleType.cpp:146)
Leaked object at 0x9180de8 (size 12, 0x806c50e)
Leaked object at 0x91815a0 (size 8, 0x806c50e)
Leaked object at 0x91f4a78 (size 72, MSNet.cpp:567)
Leaked object at 0x91f96a0 (size 12, 0x806c50e)
...

    This is uname -a output:
    Linux caesar-laptop 2.6.31-22-generic #60-Ubuntu SMP Thu May 27 00:22:23
UTC 2010 i686 GNU/Linux
    I'm running Ubuntu 9.10 (Karmic Koala) on an Acer 5720ZG laptop.

    Also, when I try to run the example sumo-0.12.0/examples/sumo/busses
with sumo-gui, right after pressing "play", I get a:
    fast_mutex::lock(): already locked
    Aborted

    My GCC version: gcc (Ubuntu 4.4.1-4ubuntu9) 4.4.1
    I'm using the GLIBCXX_FORCE_NEW(= 1) environment variable, after being
showed this warning (which appears in the end of the Leaked Object output):

*** WARNING:  GCC 3 or later is detected, please make sure the
    environment variable GLIBCPP_FORCE_NEW (GCC 3.2 and 3.3) or
    GLIBCXX_FORCE_NEW (GCC 3.4 and later) is defined.  Check the
    README file for details.

    Since I setted GLIBCXX_FORCE_NEW(= 1) I don't get this message any more,
still the "leaked object" error goes on.

    Thank you so much for any help!
    Valber