Bug#509803: Fails to properly free memory on exit

2010-04-18 Thread Stéphane Glondu
severity 509803 wishlist thanks Goswin Brederlow a écrit : > Please forward this upstream so ocaml can be made to call the > finalizers at exit. I won't forward this bug to upstream because I don't agree with what is asked. I don't think it's a bug, and I believe one shouldn't rely on finalizers

Processed: Re: Bug#509803: Fails to properly free memory on exit

2010-04-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 509803 wishlist Bug #509803 [ocaml] Fails to properly free memory on exit Severity set to 'wishlist' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (a

Bug#509803: Fails to properly free memory on exit

2009-01-08 Thread Florian Weimer
* Goswin Brederlow: > I assumed that when the program exits normaly that all memory will be > freed, specifically that *_finalize(value) is called for all custom > blocks in case they have to do some custom cleanup. Unfortunately that > is not the case. Having this functionality could be useful i

Bug#509803: Fails to properly free memory on exit

2008-12-31 Thread Richard Jones
On Fri, Dec 26, 2008 at 03:39:06PM +0100, Goswin Brederlow wrote: > I wrote some bindings for libaio using custom blocks for the C > structures I need to allocate for the internal state and buffer. I > also wrote *_finalize(value) functions for them so they get properly > cleaned up when no longer

Re: Bug#509803: Fails to properly free memory on exit

2008-12-30 Thread Romain Beauxis
Le Sunday 28 December 2008 14:09:18 Goswin von Brederlow, vous avez écrit : > > - need to change OCaml to make _finalizer mandatory at the end of the > >   process. > > Seems like a pretty trivial change. A simple "at_exit GC.full_major" > does the trick unless a global variable is used already. Ru

Bug#509803: Fails to properly free memory on exit

2008-12-30 Thread Stéphane Glondu
Stefano Zacchiroli a écrit : >>> Please forward this upstream so ocaml can be made to call the >>> finalizers at exit. >> Why don't you submit this bug to upstream yourself? > > This is not such a nice answer, don't you think? :) Sorry, I didn't mean to offend/criticize. But it seemed weird to me

Bug#509803: Fails to properly free memory on exit

2008-12-30 Thread Stefano Zacchiroli
On Sat, Dec 27, 2008 at 10:13:33AM +0100, Stéphane Glondu wrote: > Goswin Brederlow a écrit : >> Package: ocaml >> Version: 3.10.2-3 >> Severity: normal >> [...] >> Please forward this upstream so ocaml can be made to call the >> finalizers at exit. > > Why don't you submit this bug to upstream you

Re: Bug#509803: Fails to properly free memory on exit

2008-12-28 Thread Goswin von Brederlow
Sylvain Le Gall writes: > Hello, > > On 26-12-2008, Goswin Brederlow wrote: >> >> Without ocaml calling the finalizer at exit one has to manually track >> allocated custom blocks causing 16 bytes (prev/next pointer) overhead >> per block and implement ones own cleanup code by using atexit() in a

Re: Bug#509803: Fails to properly free memory on exit

2008-12-27 Thread Sylvain Le Gall
Hello, On 26-12-2008, Goswin Brederlow wrote: > > Without ocaml calling the finalizer at exit one has to manually track > allocated custom blocks causing 16 bytes (prev/next pointer) overhead > per block and implement ones own cleanup code by using atexit() in an > initializer, which is rather ug

Bug#509803: Fails to properly free memory on exit

2008-12-27 Thread Stéphane Glondu
Goswin Brederlow a écrit : Package: ocaml Version: 3.10.2-3 Severity: normal [...] Please forward this upstream so ocaml can be made to call the finalizers at exit. Why don't you submit this bug to upstream yourself? Cheers, -- Stéphane Glondu -- To UNSUBSCRIBE, email to debian-ocaml-ma

Bug#509803: Fails to properly free memory on exit

2008-12-26 Thread Goswin Brederlow
Package: ocaml Version: 3.10.2-3 Severity: normal Hi, I wrote some bindings for libaio using custom blocks for the C structures I need to allocate for the internal state and buffer. I also wrote *_finalize(value) functions for them so they get properly cleaned up when no longer in use. I assumed