[Bug 36360] New: valgrind shows several leaks in dxdiagn/tests/provider.c

https://bugs.winehq.org/show_bug.cgi?id=36360

Bug ID: 36360
           Summary: valgrind shows several leaks in
                    dxdiagn/tests/provider.c
           Product: Wine
           Version: 1.7.18
          Hardware: x86
                OS: Linux
            Status: NEW
          Keywords: download, source, testcase
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]

==14755== 756 bytes in 21 blocks are definitely lost in loss record 1,054 of
1,203
==14755==    at 0x7BC50A9B: RtlAllocateHeap (heap.c:255)
==14755==    by 0x53C9493: IMalloc_fnAlloc (ifs.c:186)
==14755==    by 0x53C99D4: CoTaskMemAlloc (objidl.h:1236)
==14755==    by 0xAD2EA72: ???
==14755==    by 0xAD2EEB4: ???
==14755==    by 0x649E5C6: ???
==14755==    by 0x649C924: ???
==14755==    by 0x4A788CB: func_provider (provider.c:124)
==14755==    by 0x4A798E0: run_test (test.h:584)
==14755==    by 0x4A79CCF: main (test.h:654)
==14755==

==14755== 28 bytes in 1 blocks are possibly lost in loss record 322 of 1,203
==14755==    at 0x7BC50A9B: RtlAllocateHeap (heap.c:255)
==14755==    by 0x53A8BB8: apartment_getclassobject (compobj.c:526)
==14755==    by 0x53ABFC6: get_inproc_class_object (compobj.c:2894)
==14755==    by 0x53AED2F: CoGetClassObject (compobj.c:3032)
==14755==    by 0x53AF4B7: CoCreateInstance (compobj.c:3197)
==14755==    by 0x649FCEF: ???
==14755==    by 0x649C924: ???
==14755==    by 0x4A78720: func_provider (provider.c:83)
==14755==    by 0x4A798E0: run_test (test.h:584)
==14755==    by 0x4A79CCF: main (test.h:654)
==14755== 
{

[Bug 36360] valgrind shows several leaks in dxdiagn/tests/provider.c

https://bugs.winehq.org/show_bug.cgi?id=36360

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |valgrind

[Bug 36360] valgrind shows several leaks in dxdiagn/tests/provider.c

https://bugs.winehq.org/show_bug.cgi?id=36360

--- Comment #1 from Sven  ---
The first leak is due to IAMFilterData_ParseFilterData being called in
dxdiagn/provider.c, which internally calls FM2_ReadFilterData, which in turn
needs a method such as FM2_DeleteRegFilter to clean up.

According to MSDN, IAMFilterData::ParseFilterData is deprecated and
IFilterMapper2::EnumMatchingFilters should be used instead. This method
internally also calls FM2_ReadFilterData, but uses FM2_DeleteRegFilter to clean
up.

But there may be better ways to do this.

[Bug 36360] valgrind shows several leaks in dxdiagn/tests/provider.c

https://bugs.winehq.org/show_bug.cgi?id=36360

pattietreutel  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]