Make GLib valgrind friendly
Submitted by David Zeuthen
Link to original bug (#627423)
Description
Right now, the GLib library stack gets in the way for finding memleaks. It would be useful if there was a function, say, g_mem_shutdown() that would free all memory "leaked" by GLib.