https://bugs.winehq.org/show_bug.cgi?id=43388
Bug ID: 43388 Summary: valgrind shows a few definite leaks in dlls/winmm/tests/mci.c Product: Wine Version: 2.12 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs@winehq.org Reporter: austinenglish@gmail.com Distribution: Gentoo
==2739== 0 bytes in 1 blocks are definitely lost in loss record 6 of 1,022 ==2739== at 0x7BC51061: notify_alloc (heap.c:254) ==2739== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==2739== by 0x523E42B: IMalloc_fnAlloc (ifs.c:187) ==2739== by 0x523ECCB: IMalloc_Alloc (objidl.h:1405) ==2739== by 0x523ECCB: CoTaskMemAlloc (???:0) ==2739== by 0x1A4983D5: ??? ==2739== by 0x1A49D191: ??? ==2739== by 0x1A49D275: ??? ==2739== by 0x1A49D767: ??? ==2739== by 0x1A49DC76: ??? ==2739== by 0x19B3BF99: ??? ==2739== by 0x7BC913B3: ??? (signal_i386.c:2700) ==2739== by 0x7BC9143B: call_thread_func (signal_i386.c:2759) ==2739== by 0x7BC91391: ??? (signal_i386.c:2700) ==2739== by 0x7BC9B3EE: start_thread (thread.c:487) ==2739== by 0x4244249: start_thread (pthread_create.c:333) ==2739== by 0x433FD6D: clone (clone.S:114) ==2739==
==2739== 0 bytes in 1 blocks are definitely lost in loss record 7 of 1,022 ==2739== at 0x7BC51061: notify_alloc (heap.c:254) ==2739== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==2739== by 0x523E42B: IMalloc_fnAlloc (ifs.c:187) ==2739== by 0x523ECCB: IMalloc_Alloc (objidl.h:1405) ==2739== by 0x523ECCB: CoTaskMemAlloc (???:0) ==2739== by 0x1A4983D5: ??? ==2739== by 0x1A49D191: ??? ==2739== by 0x1A49D275: ??? ==2739== by 0x1A49D767: ??? ==2739== by 0x1A49DC8D: ??? ==2739== by 0x19B3BF99: ??? ==2739== by 0x7BC913B3: ??? (signal_i386.c:2700) ==2739== by 0x7BC9143B: call_thread_func (signal_i386.c:2759) ==2739== by 0x7BC91391: ??? (signal_i386.c:2700) ==2739== by 0x7BC9B3EE: start_thread (thread.c:487) ==2739== by 0x4244249: start_thread (pthread_create.c:333) ==2739== by 0x433FD6D: clone (clone.S:114) ==2739==
==2739== 0 bytes in 1 blocks are definitely lost in loss record 12 of 1,022 ==2739== at 0x7BC51061: notify_alloc (heap.c:254) ==2739== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==2739== by 0x523E42B: IMalloc_fnAlloc (ifs.c:187) ==2739== by 0x523ECCB: IMalloc_Alloc (objidl.h:1405) ==2739== by 0x523ECCB: CoTaskMemAlloc (???:0) ==2739== by 0x1A4983D5: ??? ==2739== by 0x1A49D191: ??? ==2739== by 0x1A49D275: ??? ==2739== by 0x1A49D767: ??? ==2739== by 0x1A49DC76: ??? ==2739== by 0x19C52F99: ??? ==2739== by 0x7BC913B3: ??? (signal_i386.c:2700) ==2739== by 0x7BC9143B: call_thread_func (signal_i386.c:2759) ==2739== by 0x7BC91391: ??? (signal_i386.c:2700) ==2739== by 0x7BC9B3EE: start_thread (thread.c:487) ==2739== by 0x4244249: start_thread (pthread_create.c:333) ==2739== by 0x433FD6D: clone (clone.S:114) ==2739==
==2739== 0 bytes in 2 blocks are definitely lost in loss record 13 of 1,022 ==2739== at 0x7BC51061: notify_alloc (heap.c:254) ==2739== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==2739== by 0x523E42B: IMalloc_fnAlloc (ifs.c:187) ==2739== by 0x523ECCB: IMalloc_Alloc (objidl.h:1405) ==2739== by 0x523ECCB: CoTaskMemAlloc (???:0) ==2739== by 0x1A4983D5: ??? ==2739== by 0x1A49D191: ??? ==2739== by 0x1A49D275: ??? ==2739== by 0x1A49D767: ??? ==2739== by 0x1A49DC8D: ??? ==2739== by 0x19C52F99: ??? ==2739== by 0x7BC913B3: ??? (signal_i386.c:2700) ==2739== by 0x7BC9143B: call_thread_func (signal_i386.c:2759) ==2739== by 0x7BC91391: ??? (signal_i386.c:2700) ==2739== by 0x7BC9B3EE: start_thread (thread.c:487) ==2739== by 0x4244249: start_thread (pthread_create.c:333) ==2739== by 0x433FD6D: clone (clone.S:114) ==2739==