<vijaymarupudi>daviid: If that's the case, then that would be it! I had no idea autofree was implemented for opaque structs, I thought it was only for gobjects <vijaymarupudi>I guess it makes sense, pointers can have finalizers added to them, a kinda built in autofree <daviid>vijaymarupudi: there stillisa problem,because (a) it's unclear tousers when they should fre or not [that is, when mem is glib/gobject or g-golfallocated], and [b], as things are, those scheme allocated struct are being gc'ed too early ... as clone1 reported a few weeks ago, haven't find the time to 'properly work' on this yet ... <vijaymarupudi>daviid: I think autofree everything would be the ideal goal, then there would be no confusion. I had no idea they were being gc'ed too early, if finalizers are running too early, wouldn't that be a guile bug? <daviid>vijaymarupudi: no, nothing to do with guile - it is a g-golf issue, just as clone reported, iters (or any scheme allocated/gobject filled mem is currently suspected to be gc'ed too early ... <vijaymarupudi>daviid: Got it. I'm excited for g-golf, it feels like the bugs are happening less and less often :) <daviid>vijaymarupudi: tx - getting there ... ***nckx_ is now known as nckx
***roptat_ is now known as roptat
***chris is now known as Guest5969