#3726 NORM Untriag: The journal leaks memory when switching between list and detailed view

[Zarro Boogs per Child]

#3726: The journal leaks memory when switching between list and detailed view
------------------------------+---------------------------------------------
 Reporter:  marco             |       Owner:  tomeu    
     Type:  defect            |      Status:  new      
 Priority:  normal            |   Milestone:  Untriaged
Component:  journal-activity  |     Version:           
 Keywords:                    |    Verified:  0        
------------------------------+---------------------------------------------
 There was a couple of problems in the sugar code but the main issue here
 is that pygobject 2.12 has a reference cycle between GObject and PyObject
 which seem to be causing all kind of weird memory issues. Even leaving
 aside the bugs I think depending on the cyclic gc to free GObjects is
 really bad, it already proved to be an issue for big chunks of memory like
 gtk.gdk.Pixbuf in the Memorize activity (yeah, you can work it around with
 gc.collect but...).

 I reported them upstream, but since the root of the problem is fixed in
 pygobject 2.14, for FRS we should probably consider to upgrade.

 Anyway, I refactored the code on master to not recreate the detailed view
 every time (which I wanted to do anyway). And I put in a workaround to not
 leak the canvas items. The changes are pretty simple but very invasive, so
 we will need to carefully consider if this should go in Trial-3.

 There seem to still be a much smaller leak (but it might just be the gc
 not kicking in). I'd rather spend time to track that down once we made a
 call about upgrading or not to 2.14. (The __del__ in DSMetadata is likely
 causing issues, btw)

-- 
Ticket URL: <https://dev.laptop.org/ticket/3726>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system