hi gem-devs
first of all, sorry for posting on this thread, without reading it ... but it might be related to the recent changes in this class
after updating to todays cvs, i'm not able to run my gem patch any more:
after this error message: terminate called after throwing an instance of 'std::bad_alloc' what(): St9bad_alloc Pd: signal 6
trying to find this with valgrind, i get the following trace:
**25539** new/new[] failed and should throw an exception, but Valgrind cannot throw exceptions and so is aborting instead. Sorry. ==25539== at 0x1B8FC782: VALGRIND_PRINTF_BACKTRACE (in /usr/lib/valgrind/vg_inject.so) ==25539== by 0x1B9046C8: operator new(unsigned) (in /usr/lib/valgrind/vgpreload_memcheck.so) ==25539== by 0x1C1F637B: std::vector<float, std::allocator<float> >::_M_insert_aux(__gnu_cxx::__normal_iterator<float*, std::vector<float, std::allocator<float> > >, float const&) (in /home/tim/pd/extra/Gem.pd_linux) ==25539== by 0x1C1F4801: TextBase::makeLineDist() (in /home/tim/pd/extra/Gem.pd_linux) ==25539== by 0x1C1F4898: TextBase::setJustification(TextBase::JustifyWidth, TextBase::JustifyHeight) (in /home/tim/pd/extra/Gem.pd_linux) ==25539== by 0x1C1F24E1: TextBase::justifyMessCallback(void*, _symbol*, int, _atom*) (in /home/tim/pd/extra/Gem.pd_linux) ==25539== by 0x809CBB1: pd_typedmess (in /usr/local/bin/pd) ==25539== by 0x809EFB4: outlet_anything (in /usr/local/bin/pd) ==25539== by 0x1B90CC54: init_bang (in /home/tim/pd/extra/init.pd_linux) ==25539== by 0x809CB64: pd_typedmess (in /usr/local/bin/pd) ==25539== by 0x809D39B: pd_vmess (in /usr/local/bin/pd) ==25539== by 0x807AFC4: canvas_loadbang (in /usr/local/bin/pd)
i somehow have the feeling, that there is a really bad memory leak in the "justify" method, that eats about all my memory in less than 15 seconds ...
no time to look into it now ... need to get proper commas first ...
cheers ... tim