Track down memory leak
@tvb
Submitted by Tristan Van Berkom Link to original bug (#641131)
Description
To reproduce:
- Create a project with just one GtkWindow
- Start 'top' in a terminal
- Load the project, inspect Glade's resident memory usage
- Close the project
- Load the project again and inspect Glade's resident memory usage
Every time the project is reopened Glade's memory grows, about 2MB for ever 3 times the project is reloaded (it used to be 2MB per load, fixing GtkToolPalette GtkContainerClass->forall() implementation to consider looping over a child list that may be modified fixed part of the memory leak).