[Bug 36595] New: valgrind shows several memory leaks in windowscodecs/tests/metadata.c

[wine-bugs at winehq.org]

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

            Bug ID: 36595
           Summary: valgrind shows several memory leaks in
                    windowscodecs/tests/metadata.c
           Product: Wine
           Version: 1.7.19
          Hardware: x86
                OS: Linux
            Status: NEW
          Keywords: download, source, testcase
          Severity: normal
          Priority: P2
         Component: windowscodecs
          Assignee: wine-bugs at winehq.org
          Reporter: austinenglish at gmail.com

==24667== 8 bytes in 1 blocks are definitely lost in loss record 38 of 560
==24667==    at 0x7BC4C6DF: notify_alloc (heap.c:255)
==24667==    by 0x7BC50F23: RtlAllocateHeap (heap.c:1716)
==24667==    by 0x4E4AEE9: ComponentFactory_CreateInstance (imgfactory.c:1044)
==24667==    by 0x4E3A55B: ClassFactoryImpl_CreateInstance (clsfactory.c:138)
==24667==    by 0x5124F06: CoCreateInstance (unknwn.h:226)
==24667==    by 0x4CBE594: test_create_reader (metadata.c:837)
==24667==    by 0x4CC3DA5: func_metadata (metadata.c:1786)
==24667==    by 0x4CD57DA: run_test (test.h:584)
==24667==    by 0x4CD5BC9: main (test.h:654)
==24667== 

==24667== 16 bytes in 1 blocks are definitely lost in loss record 106 of 560
==24667==    at 0x7BC4C6DF: notify_alloc (heap.c:255)
==24667==    by 0x7BC50F23: RtlAllocateHeap (heap.c:1716)
==24667==    by 0x4E76AC9: ungif_alloc (ungif.c:61)
==24667==    by 0x4E76BD9: MakeMapObject (ungif.c:155)
==24667==    by 0x4E7734D: DGifGetImageDesc (ungif.c:413)
==24667==    by 0x4E77F9F: DGifSlurp (ungif.c:891)
==24667==    by 0x4E442E2: GifDecoder_Initialize (gifformat.c:1131)
==24667==    by 0x4CC00CF: test_metadata_gif (wincodec.h:3511)
==24667==    by 0x4CC3DAF: func_metadata (metadata.c:1788)
==24667==    by 0x4CD57DA: run_test (test.h:584)
==24667==    by 0x4CD5BC9: main (test.h:654)
==24667== 

==24667== 32 bytes in 1 blocks are definitely lost in loss record 204 of 560
==24667==    at 0x7BC4C6DF: notify_alloc (heap.c:255)
==24667==    by 0x7BC50F23: RtlAllocateHeap (heap.c:1716)
==24667==    by 0x514316C: CreateStreamOnHGlobal (hglobalstream.c:591)
==24667==    by 0x4CB9DC8: create_stream (metadata.c:195)
==24667==    by 0x4CBE5E9: test_create_reader (metadata.c:841)
==24667==    by 0x4CC3DA5: func_metadata (metadata.c:1786)
==24667==    by 0x4CD57DA: run_test (test.h:584)
==24667==    by 0x4CD5BC9: main (test.h:654)
==24667== 

==24667== 34 bytes in 1 blocks are definitely lost in loss record 207 of 560
==24667==    at 0x7BC4C6DF: notify_alloc (heap.c:255)
==24667==    by 0x7BC50F23: RtlAllocateHeap (heap.c:1716)
==24667==    by 0x7B8457FF: HeapAlloc (heap.c:271)
==24667==    by 0x7B845B34: GlobalAlloc (heap.c:388)
==24667==    by 0x4CB9D2E: create_stream (metadata.c:187)
==24667==    by 0x4CBE5E9: test_create_reader (metadata.c:841)
==24667==    by 0x4CC3DA5: func_metadata (metadata.c:1786)
==24667==    by 0x4CD57DA: run_test (test.h:584)
==24667==    by 0x4CD5BC9: main (test.h:654)
==24667== 

and one possible leak:
==24667== 8 bytes in 1 blocks are possibly lost in loss record 37 of 560
==24667==    at 0x7BC4C6DF: notify_alloc (heap.c:255)
==24667==    by 0x7BC50F23: RtlAllocateHeap (heap.c:1716)
==24667==    by 0x7B8457FF: HeapAlloc (heap.c:271)
==24667==    by 0x7B845AD4: GlobalAlloc (heap.c:376)
==24667==    by 0x4CB9D2E: create_stream (metadata.c:187)
==24667==    by 0x4CBE5E9: test_create_reader (metadata.c:841)
==24667==    by 0x4CC3DA5: func_metadata (metadata.c:1786)
==24667==    by 0x4CD57DA: run_test (test.h:584)
==24667==    by 0x4CD5BC9: main (test.h:654)
==24667==

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.