On 2012-08-06 13:53, Michael Meeks wrote:
Anyhow - the suggestion is, assuming we can find/cleanup this sort of
badness [ incidentally a GObject takes a reference on itself during it's
destruction to avoid double destruction ], is it a good idea to have an
abort/assert whatever is fashio
So,
I was wondering reading:
https://bugs.freedesktop.org/show_bug.cgi?id=53154#c5
"...either memory corruption or a ref-counted UNO object
forcefully being deleted before its ref-count is zero"
It seemed to me that we could catch the latter case and avoi
