win32: stop leaking GPrivate data
authorRyan Lortie <desrt@desrt.ca>
Tue, 4 Oct 2011 20:08:27 +0000 (16:08 -0400)
committerRyan Lortie <desrt@desrt.ca>
Tue, 4 Oct 2011 20:08:27 +0000 (16:08 -0400)
commitf1512917e6e46e30000bcca2ebf06ef9d15b751d
treec8cb804036f45d0c96b8a9cb27ee0dc68a9a86f6
parentdd09a95543dd9e2156a635e81892d2c583177f08
win32: stop leaking GPrivate data

Instead of running the GPrivate destructors from our thread proxy code,
run it from the DllMain handler for the DLL_THREAD_DETACH case.

This should ensure that thread-local data is free at the exit of all
threads -- not just the ones we created for ourselves.

https://bugzilla.gnome.org/show_bug.cgi?id=660745
glib/glib-init.c
glib/glib-init.h
glib/gthread-win32.c