On Wed, 27 Feb 2008, Bill Skaggs wrote:
> It isn't tile *allocation* that matters here, it is tile *locking*,
> and locking only happens in one place, tile_lock() in
> app/base/tile.c. It should be pretty straightforward for
> you to throw some debugging code in there.
>
> As I wrote before, thoug
It isn't tile *allocation* that matters here, it is tile *locking*,
and locking only happens in one place, tile_lock() in
app/base/tile.c. It should be pretty straightforward for
you to throw some debugging code in there.
As I wrote before, though, tile locking happens *a lot*.
Many internal oper
On Wed, 2008-02-27 at 00:04 -0500, Brennan Sellner wrote:
> > Basically this means that your plug-ins creates drawables and doesn't
> > destroy them later nor does it attach them to any image.
For what it's worth I've been getting these warnings, using only
"core" plugins (gaussian blur, resize,
> Basically this means that your plug-ins creates drawables and doesn't
> destroy them later nor does it attach them to any image. Of course it's
> not correct that GIMP allows plug-ins to do such things. It should clean
> up after them and release all resources they allocated. But this is not
> an
Hi,
On Sat, 2008-02-23 at 22:09 -0500, Brennan Sellner wrote:
> I'm developing a reasonably complex plugin for GIMP 2.4 in C++ (using GIMP
> and libgimp 2.4.2 on Ubuntu 7.10), and am currently having trouble with a
> Heisenbug: after running my plugin with a particular set of parameters,
> when
Brennan Sellner wrote:
> I'm developing a reasonably complex plugin for GIMP 2.4 in C++ (using GIMP
> and libgimp 2.4.2 on Ubuntu 7.10), and am currently having trouble with a
> Heisenbug: after running my plugin with a particular set of parameters,
> when I exit GIMP, I often (~90% of the time
We probably would need to see the code (or have a way of replicating
the problem) to get anywhere. The warning means that tiles are
getting locked without afterward getting unlocked. There are about
100 operations in Gimp that call for tiles to be locked, and there's
just no way to have any idea
> when I exit GIMP, I often (~90% of the time) get the following error:
>
>Gimp-Base-WARNING **: tile ref count balance: 1858
We probably would need to see the code (or have a way of replicating
the problem) to get anywhere. The warning means that tiles are
getting locked without afterward g
Hi,
I'm developing a reasonably complex plugin for GIMP 2.4 in C++ (using GIMP
and libgimp 2.4.2 on Ubuntu 7.10), and am currently having trouble with a
Heisenbug: after running my plugin with a particular set of parameters,
when I exit GIMP, I often (~90% of the time) get the following error:
