Book Closing in HEAD kills objects in a "bad" order, corrupts memory.

Linas Vepstas linas at
Wed May 26 09:36:50 EDT 2004

On Wed, May 26, 2004 at 09:26:16AM -0400, Derek Atkins was heard to remark:
> Linas, thanks for the affirmation.  I'll add some code to handle this
> case, in which case we don't really need to worry about the order
> anymore (at least for book_end().
> We may still need to worry about it for book_begin(), but I'm not sure
> how to handle that in the current QOF Object code.  The order seems
> somewhat dependent on the order-of-registration of the object modules,
> no?

Hey' didn't you write that code? I think its pulling from a hash table,
which is why its random order.  I don't remember how things work during
startup.  It should be easier during startup, where one can clearly
spec a dependency graph (this depends on that being intited, so go init
that now).

pub  1024D/01045933 2001-02-01 Linas Vepstas (Labas!) <linas at>
PGP Key fingerprint = 8305 2521 6000 0B5E 8984  3F54 64A9 9A82 0104 5933

More information about the gnucash-devel mailing list