On Thu, 04 Aug 2011 16:52:20 +0200
Oto Havle havle...@gmail.com wrote:
I've found a thread from caml-list archives which suggests that calling
caml_{register/remove}_global_root from custom block finalizers might not be
safe:
Stéphane Glondu wrote:
I can see that cairo_surface_t finalizer is always called when expected.
ml_cairo_image_surface_create_for_data does register a global root, but
caml_{register/remove}_global_root calls are always paired.
The bug scenario in fact involves two custom blocks -
tags 524908 - moreinfo
tags 524908 + confirmed
found 524908 1:1.2.0-2
thanks
Le 02/08/2011 21:52, Oto Havle a écrit :
[...] Note that I have 32-bit system.
I didn't take this into account, and I can indeed reproduce the bug in
an up-to-date i386 sid chroot, with version 1:1.2.0-2.
Cheers,
--
tags 524908 + help upstream
thanks
Le 03/08/2011 08:22, Stéphane Glondu a écrit :
[...] Note that I have 32-bit system.
I didn't take this into account, and I can indeed reproduce the bug in
an up-to-date i386 sid chroot, with version 1:1.2.0-2.
By looking a bit deeper, I can observe that
tags 524908 + moreinfo
thanks
On Mon, 20 Apr 2009 20:46:03 +0200, Oto Havle wrote:
OCaml programs which create Cairo surfaces via Cairo_bigarray leak memory.
Following test program reproduces the bug. The program allocates many
100Mb arrays, but explicit garbage collector invocation should
Package: libcairo-ocaml-dev
Version: 20070908-1+b2
Severity: normal
OCaml programs which create Cairo surfaces via Cairo_bigarray leak memory.
Following test program reproduces the bug. The program allocates many 100Mb arrays, but
explicit garbage collector invocation should keep the total
6 matches
Mail list logo
