New valgrind results for Oct 22, 2009

[Nikolay Sivov]

Dan Kegel wrote:
> MSDN says
> "When a DLL is unloaded from a process as a result of an unsuccessful
> load of the DLL, termination of the process, or a call to FreeLibrary,
> the system does not call the DLL's entry-point function with the
> DLL_THREAD_DETACH value for the individual threads of the process. The
> DLL is only sent a DLL_PROCESS_DETACH notification. DLLs can take this
> opportunity to clean up all resources for all threads known to the
> DLL."
>   
Forgot to say. This part of listview report looks like the same problem, 
but for winex11.drv

{
   <insert_a_suppression_name_here>
   Memcheck:Leak
   fun:notify_alloc
   fun:RtlAllocateHeap
   fun:x11drv_init_thread_data
   fun:thread_init_display
   fun:X11DRV_create_win_data
   fun:X11DRV_WindowPosChanging
   fun:set_window_pos
   fun:USER_SetWindowPos
   fun:SetWindowPos
   fun:show_window
   fun:ShowWindow
   fun:WIN_CreateWindowEx
   fun:CreateWindowExA
   fun:create_parent_window
   fun:func_listview
   fun:run_test
   fun:main
}