[Rock-dev] std::bad_alloc: Memory Leak related to typelib/ruby

[Alexander Duda]

On Tue, 2011-02-01 at 14:53 +0100, Alexander Duda wrote:
> problem is the function reader.read (reader.read_new). The garbage
> collector is somehow not deleting the sample and the result will be
> "std::bad_alloc"

I implemented a workaround for Vizkit (ruby). GC is called every 2 secs
to delete objects from typelib which do not trigger the gc.

But the hole allocation eats up a lot of cpu power therefore we are
going hopefully for the solution Sylvain suggested at some point
(Typelib should reuse the memory of old samples).

Alex




-- 
Dipl.-Ing. Alexander Duda 
Unterwasserrobotik

DFKI Bremen
Robotics Innovation Center
Robert-Hooke-Straße 5
28359 Bremen, Germany

Phone: +49 (0)421 178-456620
Fax:   +49 (0)421 178-454150
E-Mail: alexander.duda at dfki.de

Weitere Informationen: http://www.dfki.de/robotik
-----------------------------------------------------------------------
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
(Vorsitzender) Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
Amtsgericht Kaiserslautern, HRB 2313
Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
USt-Id.Nr.:    DE 148646973
Steuernummer:  19/673/0060/3