May 2026 - Wine-Bugs - list.winehq.org

[Bug 36172] New: xcopy tests fail under valgrind
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=36172 Bug ID: 36172 Summary: xcopy tests fail under valgrind Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com xcopy.c:59: Test failed: xcopy /D:d-m-y test returned rc=258 xcopy.c:64: Test failed: xcopy /D:m-d-y test failed rc=258 xcopy.c:65: Test failed: xcopy did not create xcopytest\xcopy1 xcopy.c:70: Test failed: xcopy /D:m-d-y test failed rc=258 xcopy.c:71: Test failed: xcopy did not create xcopytest\xcopy1 -- 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.

3 6

[Bug 34090] New: Worship Keeper program window empty...
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

http://bugs.winehq.org/show_bug.cgi?id=34090 Bug #: 34090 Summary: Worship Keeper program window empty... Product: Wine Version: 1.6-rc5 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dsreyes1014(a)gmail.com Classification: Unclassified I'm trying to install a new program called Worship Keeper. The setup file is attached below. When the setup is done and I tick Finish it comes up with a dialog box with an error. I'm running on Linux Mint 15 Cinnamon x86_64 with wine-1.6-rc5. Requirements for the program is at least directx9 and netframework-2.0 Any help would be appreciated. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 9

[Bug 59472] New: FreeArc hangs on startup in new wow64 mode
by WineHQ Bugzilla Aug. 28, 2026

Aug. 28, 2026

http://bugs.winehq.org/show_bug.cgi?id=59472 Bug ID: 59472 Summary: FreeArc hangs on startup in new wow64 mode Product: Wine Version: 11.3 Hardware: x86-64 URL: https://archive.org/details/FreeArc-0.666-win32bin-Sou rces OS: Linux Status: NEW Keywords: download, testcase, wow64 Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: arethusa26(a)gmail.com Distribution: --- Created attachment 80459 --> http://bugs.winehq.org/attachment.cgi?id=80459 Largest memory block loop test case executable When running the FreeArc archiver tool on the command line to add a file to an archive with a new wow64 build of Wine, the tool hangs indefinitely with only a banner output string: $ wine freearc/bin/Arc.exe a test.arc empty_file 0124:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION FreeArc 0.666 With a old wow64 build of Wine, the tool runs and completes successfully: $ wine freearc/bin/Arc.exe a test.arc empty_file 0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION FreeArc 0.666 0024:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x80010000, unix_prot 0 0024:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 80000000 0024:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x78010000, unix_prot 0 0024:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 78000000 ... creating archive: test.arc Compressing 1 file, 1,024 bytes. Processed 0% 0024:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x80010000, unix_prot 0 0024:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 80000000 0024:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x78010000, unix_prot 0 0024:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 78000000 ... Compressed 1 file, 1,024 => 44 bytes. Ratio 4.2% Compression time: cpu 0.62 secs, real 0.31 secs. Speed 3 kB/s All OK To reproduce the issue with FreeArc, download "FreeArc-portable-0.666-win32.zip" from the URL link and extract the contents of the ZIP file to a directory named "freearc". The Arc.exe binary can be run with the provided command line. When FreeArc is run with new wow64 Wine, there appears to be a thread that is stuck repeatedly calling VirtualAlloc with 0 size: 0124:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000000 2000 00000004 0124:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff (nil) 00000000 8000 0124:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000000 2000 00000004 0124:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff (nil) 00000000 8000 The code involved in the hang appears to be the LargestMemoryBlock::LargestMemoryBlock() constructor in Environment.cpp from the FreeArc sources. It's a (buggy) loop that attempts a binary search for the largest size it can successfully pass to VirtualAlloc. I have extracted the logic to create a standalone test case, which is built with: i686-w64-mingw32-gcc -O2 -Wall -Wl,--large-address-aware -o largest_memory_block.exe largest_memory_block.c On Windows 10, the largest_memory_block.exe test case shows the following output: a = 0 b = ffffffff Freeing pointer 00000000 with VirtualFree Allocating 7fffffff bytes with VirtualAlloc VirtualAlloc returned 00000000 VirtualAlloc failed, updating b to 7fffffff a = 0 b = 7fffffff Freeing pointer 00000000 with VirtualFree Allocating 3fffffff bytes with VirtualAlloc VirtualAlloc returned 01970000 VirtualAlloc succeeded, updating a to 3fffffff ... a = 7f98ffff b = 7f990001 Freeing pointer 00000000 with VirtualFree Allocating 7f990000 bytes with VirtualAlloc VirtualAlloc returned 7fff0000 VirtualAlloc succeeded, updating a to 7f990000 On new wow64 Wine, the test case shows the following output: a = 0 b = ffffffff Freeing pointer 00000000 with VirtualFree Allocating 7fffffff bytes with VirtualAlloc VirtualAlloc returned 7fff0000 VirtualAlloc succeeded, updating a to 7fffffff a = 7fffffff b = ffffffff Freeing pointer 7fff0000 with VirtualFree Allocating 3fffffff bytes with VirtualAlloc VirtualAlloc returned 00900000 VirtualAlloc succeeded, updating a to 3fffffff ... a = 1 b = ffffffff Freeing pointer 003f0000 with VirtualFree Allocating 0 bytes with VirtualAlloc VirtualAlloc returned 00000000 VirtualAlloc failed, updating b to 0 a = 1 b = 0 Freeing pointer 00000000 with VirtualFree Allocating 0 bytes with VirtualAlloc VirtualAlloc returned 00000000 VirtualAlloc failed, updating b to 0 ... The midpoint computation "c = (a + b) / 2" in the loop overflows when the initial allocation succeeds on Wine and leads to incorrect execution, whereas the initial allocation doesn't appear to succeed on Windows. -- 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.

1 8

[Bug 46836] New: Battle.Net UI freezes when downloading big games after a period of time
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=46836 Bug ID: 46836 Summary: Battle.Net UI freezes when downloading big games after a period of time Product: Wine Version: 4.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com Distribution: --- Best way to reproduce it: 1. Install Battle.Net and arial font using winetricks 2. Log in and start installation of some big game, for example, WoW (has a free trial) After some time (for me it was 10-15 minutes) the UI becomes frozen (nothing moves) and completely unresponsive. However, it seems to still continue working and downloading things, and restarting it helps to resolve it. When this happens, I don't seem anything standout-ish pop in the terminal log. Attached a log with during recording of which the bug occured. -- 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.

3 6

[Bug 46243] New: wine doesn't work with valgrind' s --progress-interval option
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=46243 Bug ID: 46243 Summary: wine doesn't work with valgrind's --progress-interval option Product: Wine Version: 3.21 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, valgrind Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- valgrind-3.14.0 added an option to print its progress. Adding --progress-interval=1 will print some statistics about its progress every second. This works with, for example, yes or bzip2: austin(a)laptop:~$ /opt/oldvalgrind/valgrind-3.14.0/bin/valgrind --progress-interval=1 yes > /dev/null ==11932== Memcheck, a memory error detector ==11932== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==11932== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info ==11932== Command: yes ==11932== --11932-- PROGRESS: U 1s, W 1s, 100.0% CPU, EvC 0.50M, TIn 1.9k, TOut 0.0k, #thr 1 --11932-- PROGRESS: U 2s, W 2s, 100.0% CPU, EvC 1.20M, TIn 1.9k, TOut 0.0k, #thr 1 --11932-- PROGRESS: U 3s, W 3s, 100.0% CPU, EvC 1.80M, TIn 1.9k, TOut 0.0k, #thr 1 --11932-- PROGRESS: U 4s, W 4s, 100.0% CPU, EvC 2.50M, TIn 1.9k, TOut 0.0k, #thr 1 but when I try that with Wine, nothing: austin(a)laptop:~/wine-git$ /opt/oldvalgrind/valgrind-3.14.0/bin/valgrind --progress-interval=1 ./wine winemine ==12309== Memcheck, a memory error detector ==12309== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==12309== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info ==12309== Command: ./wine winemine ==12309== ==12314== ==12314== HEAP SUMMARY: This would be incredibly helpful to have working, for knowing when valgrind is busy versus when it's stuck in a loop. -- 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.

2 2

[Bug 39257] New: user32/tests/dde.c crashes under valgrind
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=39257 Bug ID: 39257 Summary: user32/tests/dde.c crashes under valgrind Product: Wine Version: 1.7.51 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Fedora Created attachment 52324 --> https://bugs.winehq.org/attachment.cgi?id=52324 backtrace Backtrace: =>0 0x0483c341 wine_dbgstr_wn+0x76(str="????????????????H", n=0xffffffff) [/home/austin/wine-valgrind/dlls/user32/tests/../../../include/wine/test.h:486] in user32_test (0x04acf528) 1 0x047718bc wine_dbgstr_w+0x1f(s="????????????????H") [/home/austin/wine-valgrind/dlls/user32/tests/../../../include/wine/test.h:69] in user32_test (0x04acf548) 2 0x0477e757 server_end_to_end_callback+0x718(uType=<couldn't compute location>, uFmt=<couldn't compute location>, hconv=<couldn't compute location>, hsz1=<couldn't compute location>, hsz2=<couldn't compute location>, hdata=<couldn't compute location>, dwData1=<couldn't compute location>, dwData2=<couldn't compute location>) [/home/austin/wine-valgrind/dlls/user32/tests/dde.c:2464] in user32_test (0x04acf788) 3 0x04b0b4b2 WDML_InvokeCallback+0xa2(pInstance=0x46616c8, uType=0x4050, uFmt=0, hConv=0x46638b0, hsz1=0xc002, hsz2=(nil), hdata=0x4663cf2, dwData1=0, dwData2=0) [/home/austin/wine-valgrind/dlls/user32/dde_misc.c:1231] in user32 (0x04acf7e8) 4 0x04b0f980 WDML_ServerHandleExecute+0x134(pConv=0x46638b0, pXAct=0x4663cb0) [/home/austin/wine-valgrind/dlls/user32/dde_server.c:834] in user32 (0x04acf848) 5 0x04b0fe35 WDML_ServerHandle+0xdd(pConv=0x46638b0, pXAct=0x4663cb0) [/home/austin/wine-valgrind/dlls/user32/dde_server.c:1002] in user32 (0x04acf888) 6 0x04b10303 WDML_ServerConvProc+0x3f0(hwndServer=<couldn't compute location>, iMsg=<couldn't compute location>, wParam=<couldn't compute location>, lParam=<couldn't compute location>) [/home/austin/wine-valgrind/dlls/user32/dde_server.c:1112] in user32 (0x04acf908) 7 0x04b8870a WINPROC_wrapper+0x19() in user32 (0x04acf948) 8 0x04b8883d call_window_proc+0xb1(hwnd=0xb2011a, msg=0x3e8, wp=0xaf011e, lp=0x4663c4a, result=0x4acfac8, arg=0x4b0ff12) [/home/austin/wine-valgrind/dlls/user32/winproc.c:245] in user32 (0x04acf988) 9 0x04b8a67b WINPROC_call_window+0x1c2(hwnd=0xb2011a, msg=0x3e8, wParam=0xaf011e, lParam=0x4663c4a, result=0x4acfac8, unicode=0, mapping=WMCHAR_MAP_DISPATCHMESSAGE) [/home/austin/wine-valgrind/dlls/user32/winproc.c:910] in user32 (0x04acf9d8) 10 0x04b51dc0 DispatchMessageA+0x1a7(msg=<couldn't compute location>) [/home/austin/wine-valgrind/dlls/user32/message.c:3952] in user32 (0x04acfaf8) 11 0x0477f5ca test_end_to_end_server+0x18c(hproc=0x5c, hthread=0x60, type_a=0x1) [/home/austin/wine-valgrind/dlls/user32/tests/dde.c:2674] in user32_test (0x04acfb58) 12 0x0477f95f func_dde+0x2ba() [/home/austin/wine-valgrind/dlls/user32/tests/dde.c:2740] in user32_test (0x04acfcf8) 13 0x0483c82d run_test+0x9f(name="dde") [/home/austin/wine-valgrind/dlls/user32/tests/../../../include/wine/test.h:584] in user32_test (0x04acfd38) 14 0x0483cc75 main+0x222(argc=<couldn't compute location>, argv=<couldn't compute location>) [/home/austin/wine-valgrind/dlls/user32/tests/../../../include/wine/test.h:666] in user32_test (0x04acfde8) -- 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.

3 4

[Bug 46689] New: kernel32/tests/locale.c shows an invalid write
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=46689 Bug ID: 46689 Summary: kernel32/tests/locale.c shows an invalid write Product: Wine Version: 4.2 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- ../../../tools/runtest -q -P wine -T ../../.. -M kernel32.dll -p kernel32_test.exe.so locale && touch locale.ok preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 ==21972== Invalid write of size 2 ==21972== at 0x7B4818FB: wine_decompose (decompose.c:2218) ==21972== by 0x7B48197A: wine_decompose (decompose.c:2234) ==21972== by 0x7B480447: wine_decompose_string (normalize.c:100) ==21972== by 0x7B451617: NormalizeString (locale.c:5403) ==21972== by 0x4AF1149: test_NormalizeString (locale.c:5770) ==21972== by 0x4B07EBC: func_locale (locale.c:6021) ==21972== by 0x4B7172E: run_test (test.h:617) ==21972== by 0x4B7216C: main (test.h:701) ==21972== Address 0x494107c is 0 bytes after a recently re-allocated block of size 4 alloc'd ==21972== at 0x7BC48A83: notify_alloc (heap.c:260) ==21972== by 0x7BC4BFA7: RtlAllocateHeap (heap.c:1726) ==21972== by 0x7B4433F8: HeapAlloc (heap.c:271) ==21972== by 0x7B44AB49: heap_realloc (heap.h:40) ==21972== by 0x7B4515F7: NormalizeString (locale.c:5396) ==21972== by 0x4AF1149: test_NormalizeString (locale.c:5770) ==21972== by 0x4B07EBC: func_locale (locale.c:6021) ==21972== by 0x4B7172E: run_test (test.h:617) ==21972== by 0x4B7216C: main (test.h:701) ==21972== -- 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.

2 2

[Bug 46349] New: wininet/tests/http.c shows uninitialized memory use
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=46349 Bug ID: 46349 Summary: wininet/tests/http.c shows uninitialized memory use Product: Wine Version: 4.0-rc3 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: wininet Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Gentoo ==23151== Thread 5: ==23151== Syscall param sendmsg(msg.msg_iov[0]) points to uninitialised byte(s) ==23151== at 0x425091F: sendmsg (sendmsg.c:30) ==23151== by 0x60591C4: WS2_send (socket.c:2628) ==23151== by 0x60594BB: WS2_sendto (socket.c:5606) ==23151== by 0x605FBC5: WS_send (socket.c:5521) ==23151== by 0x4A93CF4: server_thread (http.c:2443) ==23151== by 0x7BC77F0F: ??? (in /home/austin/wine-valgrind/dlls/ntdll/ntdll.dll.so) ==23151== by 0x7BC7B2D5: call_thread_func (signal_i386.c:2654) ==23151== by 0x7BC77F01: ??? (in /home/austin/wine-valgrind/dlls/ntdll/ntdll.dll.so) ==23151== Address 0x4a2d031 is 4,193 bytes inside a recently re-allocated block of size 8,000 alloc'd ==23151== at 0x7BC483AD: notify_alloc (heap.c:260) ==23151== by 0x7BC4BD6D: RtlReAllocateHeap (heap.c:1893) ==23151== by 0x4A931F3: server_thread (http.c:2156) ==23151== by 0x7BC77F0F: ??? (in /home/austin/wine-valgrind/dlls/ntdll/ntdll.dll.so) ==23151== by 0x7BC7B2D5: call_thread_func (signal_i386.c:2654) ==23151== by 0x7BC77F01: ??? (in /home/austin/wine-valgrind/dlls/ntdll/ntdll.dll.so) ==23151== Uninitialised value was created by a client request ==23151== at 0x7BC4831C: mark_block_uninitialized (heap.c:214) ==23151== by 0x7BC4A643: initialize_block (heap.c:245) ==23151== by 0x7BC4BDEE: RtlReAllocateHeap (heap.c:1915) ==23151== by 0x4A931F3: server_thread (http.c:2156) ==23151== by 0x7BC77F0F: ??? (in /home/austin/wine-valgrind/dlls/ntdll/ntdll.dll.so) ==23151== by 0x7BC7B2D5: call_thread_func (signal_i386.c:2654) ==23151== by 0x7BC77F01: ??? (in /home/austin/wine-valgrind/dlls/ntdll/ntdll.dll.so) ==23151== -- 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.

2 2

[Bug 38846] New: valgrind shows a possible leaks in winmm/tests/wave.c
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=38846 Bug ID: 38846 Summary: valgrind shows a possible leaks in winmm/tests/wave.c Product: Wine Version: 1.7.46 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- ==31082== 12 bytes in 1 blocks are possibly lost in loss record 77 of 761 ==31082== at 0x7BC4AAA3: notify_alloc (heap.c:254) ==31082== by 0x7BC4ED46: RtlAllocateHeap (heap.c:1715) ==31082== by 0x6126E65: MMDevEnum_RegisterEndpointNotificationCallback (devenum.c:1253) ==31082== by 0x4C57B7B: IMMDeviceEnumerator_RegisterEndpointNotificationCallback (mmdeviceapi.h:757) ==31082== by 0x4C57B7B: WINMM_InitMMDevices (???:0) ==31082== by 0x4C5CC9C: WINMM_DevicesThreadProc (waveform.c:2465) ==31082== by 0x7BC81E27: ??? (signal_i386.c:2682) ==31082== by 0x7BC81E6E: call_thread_func (signal_i386.c:2741) ==31082== by 0x7BC81E05: ??? (signal_i386.c:2682) ==31082== by 0x7BC88FE8: start_thread (thread.c:443) ==31082== by 0x4F88F37F: start_thread (in /usr/lib/libpthread-2.21.so) ==31082== by 0x4F7ABD4D: clone (in /usr/lib/libc-2.21.so) ==31082== -- 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.

2 3

[Bug 36581] New: valgrind shows a few leaks in winmm/tests/capture.c
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

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: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com austin(a)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== -- 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.

2 5