[Bug 36581] New: valgrind shows a few leaks in winmm/tests/capture.c

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

Bug ID: 36581
           Summary: valgrind shows a few leaks in winmm/tests/capture.c
           Product: Wine
           Version: 1.7.19
          Hardware: x86
                OS: Linux
            Status: NEW
          Keywords: download, source, testcase
          Severity: normal
          Priority: P2
         Component: winmm&mci
          Assignee: [e-mail]
          Reporter: [e-mail]

austin@aw25 ~/wine-valgrind/dlls/winmm/tests $ make capture.ok
../../../tools/runtest -q -P wine -T ../../.. -M winmm.dll -p winmm_test.exe.so
capture && touch capture.ok
preloader: Warning: failed to reserve range 00110000-68000000
preloader: Warning: failed to reserve range 7f000000-82000000
==26292== 512 bytes in 1 blocks are definitely lost in loss record 665 of 832
==26292==    at 0x7BC4C6DF: notify_alloc (heap.c:255)
==26292==    by 0x7BC50F23: RtlAllocateHeap (heap.c:1716)
==26292==    by 0x5126CA4: list_window_children (win.c:318)
==26292==    by 0x512EE26: WIN_ListChildren (win.c:3267)
==26292==    by 0x512B3BC: WIN_SendDestroyMsg (win.c:1783)
==26292==    by 0x512B7F5: DestroyWindow (win.c:1876)
==26292==    by 0x4FDF40A: WINMM_DevicesThreadDone (waveform.c:2445)
==26292==    by 0x4FDF896: WINMM_DevicesThreadProc (waveform.c:2516)
==26292==    by 0x7BC870C7: ??? (signal_i386.c:2571)
==26292==    by 0x7BC87110: call_thread_func (signal_i386.c:2630)
==26292==    by 0x7BC870A5: ??? (signal_i386.c:2571)
==26292==    by 0x7BC8E4EC: start_thread (thread.c:428)
==26292==    by 0x421FF92: start_thread (pthread_create.c:309)
==26292==    by 0x43247ED: clone (clone.S:129)
==26292==

==26292== 5,940 bytes in 330 blocks are definitely lost in loss record 818 of
832
==26292==    at 0x7BC4C6DF: notify_alloc (heap.c:255)
==26292==    by 0x7BC50F23: RtlAllocateHeap (heap.c:1716)
==26292==    by 0x4FDACEF: WINMM_OpenDevice (waveform.c:1093)
==26292==    by 0x4FDBCAB: WID_Open (waveform.c:1361)
==26292==    by 0x4FDF30B: WINMM_DevicesMsgProc (waveform.c:2413)
==26292==    by 0x51394F5: ??? (winproc.c:173)
==26292==    by 0x513966A: call_window_proc (winproc.c:244)
==26292==    by 0x513B803: WINPROC_call_window (winproc.c:900)
==26292==    by 0x50F811C: call_window_proc (message.c:2223)
==26292==    by 0x50FA320: peek_message (message.c:2953)
==26292==    by 0x50FBDC6: PeekMessageW (message.c:3757)
==26292==    by 0x4FDF773: WINMM_DevicesThreadProc (waveform.c:2503)
==26292==    by 0x7BC870C7: ??? (signal_i386.c:2571)
==26292==    by 0x7BC87110: call_thread_func (signal_i386.c:2630)
==26292==    by 0x7BC870A5: ??? (signal_i386.c:2571)
==26292==    by 0x7BC8E4EC: start_thread (thread.c:428)
==26292==    by 0x421FF92: start_thread (pthread_create.c:309)
==26292==    by 0x43247ED: clone (clone.S:129)
==26292==

[Bug 36581] valgrind shows a few leaks in winmm/tests/capture.c

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

Austin English  changed:

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

[Bug 36581] valgrind shows a few leaks in winmm/tests/capture.c

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

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
       Distribution|---                         |Gentoo

[Bug 36581] valgrind shows a few leaks in winmm/tests/capture.c

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

--- Comment #1 from Austin English  ---
==2520== 512 bytes in 1 blocks are definitely lost in loss record 603 of 719
==2520==    at 0x7BC51061: notify_alloc (heap.c:254)
==2520==    by 0x7BC5554F: RtlAllocateHeap (heap.c:1716)
==2520==    by 0x4CD5934: list_window_children (win.c:319)
==2520==    by 0x4CDE503: WIN_ListChildren (win.c:3309)
==2520==    by 0x4CDAABF: DestroyWindow (win.c:1881)
==2520==    by 0x4B8E3DD: WINMM_DevicesThreadDone (waveform.c:2446)
==2520==    by 0x4B8E79F: WINMM_DevicesThreadProc (waveform.c:2517)
==2520==    by 0x7BC913B3: ??? (signal_i386.c:2700)
==2520==    by 0x7BC9143B: call_thread_func (signal_i386.c:2759)
==2520==    by 0x7BC91391: ??? (signal_i386.c:2700)
==2520==    by 0x7BC9B3EE: start_thread (thread.c:487)
==2520==    by 0x4244249: start_thread (pthread_create.c:333)
==2520==    by 0x433FD6D: clone (clone.S:114)