[Fluxus] Memory leak in build-extrusion?
evan.raskob [lists]
lists at lowfrequency.org
Fri Sep 24 04:16:38 PDT 2010
No valgrind on OS X :(
But now that you helped me make that pure:dyne usb boot stick I will give it a try...
Best
Evan
On 20 Sep 2010, at 21:59, Claude Heiland-Allen wrote:
> On 20/09/10 18:08, evan.raskob [lists] wrote:
>> Hi guys
>>
>> I have an exhibition running all day (12+ hrs) and it slows to a crawl towards the end of the day, but all I am doing really is creating an extrusion, destroying it, and re-creating it. Does this sound plausible? I'm not sure how to profile it...
>
> $ valgrind --vex-iropt-precise-memory-exns=yes --leak-check=full fluxus
>
> There's a lot of warnings about the garbage collector, which can be ignored, but at the end of the program run you'll get a flood of info about where unfreed memory was allocated.
>
>
> Claude
More information about the Fluxus
mailing list