Reported this on April 11 but didn't get any response, so I'm just trying again :-)
Valgrind complains about drmHashTable staying around. It's ironic because in my application drmClose creates the hash table and creates an entry for no other purpose than to delete the entry. So my first patch is libdrm_drmclose.patch which stops doing any of that if there wasn't a hash table already. libdrm_drmclose2.patch extends that and deletes drmHashTable when its empty. I have a DSO that links against libdrm and I don't want dlopen/dlclose cycles to leak memory. Cheers, Waldo -- Intel Corporation - Hillsboro, Oregon Ultra Mobility Group - Platform Software Architecture Tel: +1 503 264 6237 - Mobile: +1 503 703-7327
libdrm_drmclose.patch
Description: libdrm_drmclose.patch
libdrm_drmclose2.patch
Description: libdrm_drmclose2.patch
------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
-- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
