September 2018 - Wine-Bugs - list.winehq.org

[Bug 38452] New: valgrind shows an uninitialized variable in urlmon/tests/url.c
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=38452 Bug ID: 38452 Summary: valgrind shows an uninitialized variable in urlmon/tests/url.c Product: Wine Version: 1.7.41 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: urlmon Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Debian ==16118== Conditional jump or move depends on uninitialised value(s) ==16118== at 0x98944C9: ??? ==16118== by 0x59BB456: create_nscontainer (nsembed.c:2115) ==16118== by 0x59389E8: HTMLDocument_Create (htmldoc.c:4857) ==16118== by 0x59A727D: ClassFactory_CreateInstance (main.c:271) ==16118== by 0x49F746C: IClassFactory_CreateInstance (unknwn.h:226) ==16118== by 0x49F746C: CoCreateInstance (???:0) ==16118== by 0x4929C7C: create_mime_object (binding.c:260) ==16118== by 0x4929FAB: create_object (binding.c:310) ==16118== by 0x492C716: report_data (binding.c:1079) ==16118== by 0x492C9F3: InternetProtocolSink_ReportData (binding.c:1128) ==16118== by 0x4931581: IInternetProtocolSink_ReportData (urlmon.h:3113) ==16118== by 0x4931581: ProtocolSinkHandler_ReportData (???:0) ==16118== by 0x4931FF0: IInternetProtocolSink_ReportData (urlmon.h:3113) ==16118== by 0x4931FF0: report_data_proc (???:0) ==16118== by 0x492E367: process_tasks (bindprot.c:57) ==16118== by 0x492E3B8: notif_wnd_proc (bindprot.c:68) ==16118== by 0x4C424C9: ??? (winproc.c:174) ==16118== by 0x4C425FC: call_window_proc (winproc.c:245) ==16118== by 0x4C44370: WINPROC_call_window (winproc.c:901) ==16118== by 0x4C0CB60: DispatchMessageW (message.c:4027) ==16118== by 0x492DD97: start_binding (binding.c:1554) ==16118== by 0x492DF63: bind_to_object (binding.c:1598) ==16118== by 0x494AA69: URLMoniker_BindToObject (umon.c:260) ==16118== Uninitialised value was created by a stack allocation ==16118== at 0x9894439: ??? ==16118== -- 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 43313] New: valgrind shows several uninitialized writes in dlls/ dinput/tests/device.c
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=43313 Bug ID: 43313 Summary: valgrind shows several uninitialized writes in dlls/dinput/tests/device.c Product: Wine Version: 2.12 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com CC: 00cpxxx(a)gmail.com Distribution: Gentoo ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A6DAE: JoystickWImpl_Acquire (joystick_linuxinput.c:718) ==21119== by 0x52A6F15: JoystickAImpl_Acquire (joystick_linuxinput.c:736) ==21119== by 0x48783BA: test_object_info (device.c:118) ==21119== by 0x4878BBB: enum_devices (device.c:194) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f68c is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6B64: JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A700D: JoystickWImpl_Unacquire (joystick_linuxinput.c:762) ==21119== by 0x52A70F0: JoystickAImpl_Unacquire (joystick_linuxinput.c:774) ==21119== by 0x4878441: test_object_info (device.c:121) ==21119== by 0x4878BBB: enum_devices (device.c:194) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f68c is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6F36: JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A6DAE: JoystickWImpl_Acquire (joystick_linuxinput.c:718) ==21119== by 0x52A6F15: JoystickAImpl_Acquire (joystick_linuxinput.c:736) ==21119== by 0x48785AF: test_object_info (device.c:131) ==21119== by 0x4878BBB: enum_devices (device.c:194) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f68c is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6B64: JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A700D: JoystickWImpl_Unacquire (joystick_linuxinput.c:762) ==21119== by 0x52A70F0: JoystickAImpl_Unacquire (joystick_linuxinput.c:774) ==21119== by 0x4878683: test_object_info (device.c:136) ==21119== by 0x4878BBB: enum_devices (device.c:194) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f68c is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6F36: JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A6DAE: JoystickWImpl_Acquire (joystick_linuxinput.c:718) ==21119== by 0x52A6F15: JoystickAImpl_Acquire (joystick_linuxinput.c:736) ==21119== by 0x48788F9: test_object_info (device.c:161) ==21119== by 0x4878BBB: enum_devices (device.c:194) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f68c is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6B64: JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A700D: JoystickWImpl_Unacquire (joystick_linuxinput.c:762) ==21119== by 0x52A70F0: JoystickAImpl_Unacquire (joystick_linuxinput.c:774) ==21119== by 0x48789BD: test_object_info (device.c:166) ==21119== by 0x4878BBB: enum_devices (device.c:194) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f68c is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6F36: JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A6DAE: JoystickWImpl_Acquire (joystick_linuxinput.c:718) ==21119== by 0x48783BA: test_object_info (device.c:118) ==21119== by 0x4878C4C: enum_devices (device.c:200) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f6cc is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6B64: JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A700D: JoystickWImpl_Unacquire (joystick_linuxinput.c:762) ==21119== by 0x4878441: test_object_info (device.c:121) ==21119== by 0x4878C4C: enum_devices (device.c:200) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f6cc is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6F36: JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A6DAE: JoystickWImpl_Acquire (joystick_linuxinput.c:718) ==21119== by 0x48785AF: test_object_info (device.c:131) ==21119== by 0x4878C4C: enum_devices (device.c:200) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f6cc is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6B64: JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A700D: JoystickWImpl_Unacquire (joystick_linuxinput.c:762) ==21119== by 0x4878683: test_object_info (device.c:136) ==21119== by 0x4878C4C: enum_devices (device.c:200) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f6cc is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6F36: JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== wine-2.12. Note: I had a Sony DS4 plugged in via USB when the tests were run, which may be related -- 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 37157] New: mshtml/events test hangs under valgrind
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=37157 Bug ID: 37157 Summary: mshtml/events test hangs under valgrind Product: Wine Version: 1.7.24 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Created attachment 49389 --> https://bugs.winehq.org/attachment.cgi?id=49389 valgrind output I've only noticed this on my debian desktop, but it's repeatable every time. austin(a)debian-home:~/wine-valgrind-known$ valgrind --version valgrind-3.9.0 austin(a)debian-home:~/wine-valgrind-known$ ps aux | grep event austin 18489 0.0 0.0 2244 540 pts/3 S+ 07:56 0:00 /bin/sh -c ../../../tools/runtest -q -P wine -T ../../.. -M mshtml.dll -p mshtml_test.exe.so events && touch events.ok austin(a)debian-home:~/wine-valgrind-known$ uname -a Linux debian-home 3.14-2-686-pae #1 SMP Debian 3.14.13-2 (2014-07-24) i686 GNU/Linux -- 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 36315] New: valgrind shows several leaks in qedit/tests/mediadet.c
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=36315 Bug ID: 36315 Summary: valgrind shows several leaks in qedit/tests/mediadet.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Created attachment 48402 --> https://bugs.winehq.org/attachment.cgi?id=48402 valgrind log ==31827== 28 bytes in 1 blocks are possibly lost in loss record 239 of 877 ==31827== at 0x7BC4C735: notify_alloc (heap.c:255) ==31827== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==31827== by 0x4B5B262: heap_alloc_zero (typelib.c:1662) ==31827== by 0x4B5DEA1: MSFT_ReadAllRefs (typelib.c:2902) ==31827== by 0x4B6014C: ITypeLib2_Constructor_MSFT (typelib.c:3716) ==31827== by 0x4B5F3B8: TLB_ReadTypeLib (typelib.c:3460) ==31827== by 0x4B576DC: LoadTypeLibEx (typelib.c:478) ==31827== by 0x4B57618: LoadTypeLib (typelib.c:454) ==31827== by 0x4B5786A: LoadRegTypeLib (typelib.c:537) ==31827== by 0x6073AD3: ??? ==31827== by 0x607A475: ??? ==31827== by 0x600A806: ??? ==31827== by 0x600AAC0: ??? ==31827== by 0x50A3E26: CoCreateInstance (unknwn.h:226) ==31827== by 0x5FADE44: SampleGrabber_create (samplegrabber.c:1304) ==31827== by 0x5FA741F: DSCF_CreateInstance (main.c:110) ==31827== by 0x50A3E26: CoCreateInstance (unknwn.h:226) ==31827== by 0x4956F1F: test_samplegrabber (mediadet.c:388) ==31827== by 0x4957979: func_mediadet (mediadet.c:475) ==31827== by 0x495877C: run_test (test.h:584) ==31827== ==31827== 32 bytes in 1 blocks are possibly lost in loss record 293 of 877 ==31827== at 0x7BC4C735: notify_alloc (heap.c:255) ==31827== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==31827== by 0x7BC39AE9: RtlInitializeCriticalSectionEx (critsection.c:326) ==31827== by 0x7B876B51: InitializeCriticalSectionEx (sync.c:356) ==31827== by 0x7B876AD0: InitializeCriticalSection (sync.c:313) ==31827== by 0x6074935: ??? ==31827== by 0x6011AC3: ??? ==31827== by 0x5FE5C00: ??? ==31827== by 0x600AAC0: ??? ==31827== by 0x50A3E26: CoCreateInstance (unknwn.h:226) ==31827== by 0x5FA8D03: GetSplitter (mediadet.c:435) ==31827== by 0x5FA9282: MediaDet_put_Filename (mediadet.c:513) ==31827== by 0x4955998: test_mediadet (qedit.h:598) ==31827== by 0x4957974: func_mediadet (mediadet.c:474) ==31827== by 0x495877C: run_test (test.h:584) ==31827== by 0x4958B6A: main (test.h:654) ==31827== ==4134== 66 bytes in 1 blocks are definitely lost in loss record 456 of 929 ==4134== at 0x7BC4C735: notify_alloc (heap.c:255) ==4134== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==4134== by 0x52C2635: IMalloc_fnAlloc (ifs.c:186) ==4134== by 0x52C2F50: CoTaskMemAlloc (objidl.h:1236) ==4134== by 0x6345811: ??? ==4134== by 0x634F193: ??? ==4134== by 0x630023B: MediaDet_put_Filename (strmif.h:6469) ==4134== by 0x4A79998: test_mediadet (qedit.h:598) ==4134== by 0x4A7B974: func_mediadet (mediadet.c:474) ==4134== by 0x4A7C77C: run_test (test.h:584) ==4134== by 0x4A7CB6A: main (test.h:654) ==4134== etc. -- 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 36561] New: valgrind shows a definite leak in msrle/tests/msrle.c
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=36561 Bug ID: 36561 Summary: valgrind shows a definite leak in msrle/tests/msrle.c Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==29940== 256 bytes in 1 blocks are definitely lost in loss record 399 of 539 ==29940== at 0x7BC4C6DF: notify_alloc (heap.c:255) ==29940== by 0x7BC50F23: RtlAllocateHeap (heap.c:1716) ==29940== by 0x7B8457FF: HeapAlloc (heap.c:271) ==29940== by 0x7B845A26: GlobalAlloc (heap.c:364) ==29940== by 0x7B846E63: LocalAlloc (heap.c:967) ==29940== by 0x65FE88C: ??? ==29940== by 0x65FEB12: ??? ==29940== by 0x6600326: ??? ==29940== by 0x4E168F6: DRIVER_SendMessage (driver.c:136) ==29940== by 0x4E16A41: SendDriverMessage (driver.c:156) ==29940== by 0x4DEE914: MSVIDEO_SendMessage (msvideo_main.c:173) ==29940== by 0x4DF13FD: ICSendMessage (msvideo_main.c:1096) ==29940== by 0x4DF0492: ICCompress (msvideo_main.c:741) ==29940== by 0x4CA23BE: test_encode (msrle.c:92) ==29940== by 0x4CA24A6: func_msrle (msrle.c:104) ==29940== by 0x4CA3299: run_test (test.h:584) ==29940== by 0x4CA3687: main (test.h:654) ==29940== -- 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 36116] New: msi/action possible leak in test_create_remove_shortcut
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=36116 Bug ID: 36116 Summary: msi/action possible leak in test_create_remove_shortcut Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: minor Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==20424== 48 bytes in 1 blocks are possibly lost in loss record 485 of 1,049 ==20424== at 0x7BC4C735: notify_alloc (heap.c:255) ==20424== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==20424== by 0x5069418: msi_alloc (msipriv.h:1188) ==20424== by 0x506AE0C: get_table (table.c:601) ==20424== by 0x506F48C: TABLE_CreateView (table.c:2161) ==20424== by 0x5075B7D: WHERE_CreateView (where.c:1242) ==20424== by 0x50797E1: sql_parse (sql.y:494) ==20424== by 0x507A959: MSI_ParseSQL (sql.y:1002) ==20424== by 0x5044749: MSI_DatabaseOpenViewW (msiquery.c:132) ==20424== by 0x4FEC6FC: load_all_files (action.c:1300) ==20424== by 0x4FED0F6: ACTION_CostInitialize (action.c:1544) ==20424== by 0x4FFDEFD: ACTION_HandleStandardAction (action.c:7619) ==20424== by 0x4FFE0F1: ACTION_PerformAction (action.c:7648) ==20424== by 0x4FEA821: ITERATE_Actions (action.c:507) ==20424== by 0x50448B6: MSI_IterateRecords (msiquery.c:188) ==20424== by 0x4FEABBF: ACTION_ProcessExecSequence (action.c:590) ==20424== by 0x4FFE945: MSI_InstallPackage (action.c:7840) ==20424== by 0x50386E7: MsiInstallProductW (msi.c:251) ==20424== by 0x50385D8: MsiInstallProductA (msi.c:226) ==20424== by 0x4C3C622: test_create_remove_shortcut (action.c:5746) ==20424== -- 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 8

[Bug 36678] New: shell32/tests/shlexec.c: several tests fail under valgrind
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=36678 Bug ID: 36678 Summary: shell32/tests/shlexec.c: several tests fail under valgrind Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com shlexec.c:139: Test failed: ShellExecute(verb="", file=""C:\users\austin\Temp\wtb94b.tmp\drawback_file.noassoc foo.shlexec"") WaitForSingleObject returned 258 shlexec.c:139: Test failed: ShellExecute(verb="", file="C:\users\austin\Temp\wtb94b.tmp\drawback_nonexist.noassoc foo.shlexec") WaitForSingleObject returned 258 shlexec.c:139: Test failed: ShellExecute(verb="", file="C:\users\austin\Temp\wtb94b.tmp\test file.shlexec") WaitForSingleObject returned 258 shlexec.c:139: Test failed: ShellExecute(file="C:\users\austin\Temp\wtb94b.tmp\test file.shlexec") WaitForSingleObject returned 258 shlexec.c:1565: Test failed: argvA3 expected 'Open', but key not found or empty shlexec.c:1573: Test failed: argvA4 expected 'C:\users\austin\Temp\wtb94b.tmp\test file.shlexec', but key not found or empty -- 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 36674] New: mmdevapi/tests/capture.c fails under valgrind
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=36674 Bug ID: 36674 Summary: mmdevapi/tests/capture.c fails under valgrind Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: mmdevapi Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ../../../tools/runtest -q -P wine -T ../../.. -M mmdevapi.dll -p mmdevapi_test.exe.so capture && touch capture.ok preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 capture.c:141: Test failed: GetNextPacketSize 480 vs. GCP 728 capture.c:308: Test failed: GCP 968 vs. BufferSize 23941 capture.c:348: Test failed: Valid IAudioCaptureClient_GetBuffer returns 08890001 capture.c:355: Test failed: restarted GCP 8 capture.c:409: Test failed: Valid IAudioCaptureClient_GetBuffer returns 08890001 -- 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 36326] New: valgrind shows a leak in rpcrt4/tests/rpc_protoseq.c
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=36326 Bug ID: 36326 Summary: valgrind shows a leak in rpcrt4/tests/rpc_protoseq.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: rpc Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==13435== 68 bytes in 1 blocks are possibly lost in loss record 143 of 282 ==13435== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255) ==13435== by 0x5BB4B33: rpcrt4_protseq_sock_alloc (rpc_transport.c:1554) ==13435== by 0x5BAFAE5: RPCRT4_get_or_create_serverprotseq (rpc_server.c:927) ==13435== by 0x5BB1D62: RpcServerUseProtseqA (rpc_server.c:1041) ==13435== by 0x4D7A5B0: func_rpc_protseq (rpc_protseq.c:71) ==13435== by 0x4D9AC78: run_test (test.h:584) ==13435== by 0x4D9B067: main (test.h:654) ==13435== ==13580== 64 bytes in 1 blocks are possibly lost in loss record 140 of 282 ==13580== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255) ==13580== by 0x5B94EC7: rpcrt4_protseq_np_alloc (rpc_transport.c:642) ==13580== by 0x5B8FAE5: RPCRT4_get_or_create_serverprotseq (rpc_server.c:927) ==13580== by 0x5B919A1: RpcServerUseProtseqEpExA (rpc_server.c:997) ==13580== by 0x5B91B08: RpcServerUseProtseqEpA (rpc_server.c:892) ==13580== by 0x4D5A4F6: func_rpc_protseq (rpc_protseq.c:58) ==13580== by 0x4D7AC78: run_test (test.h:584) ==13580== by 0x4D7B067: main (test.h:654) ==13580== -- 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 32754] New: rFactor 2 dedicated server crash - Unhandled exception
by wine-bugs＠winehq.org Aug. 28, 2026

Aug. 28, 2026

http://bugs.winehq.org/show_bug.cgi?id=32754 Bug #: 32754 Summary: rFactor 2 dedicated server crash - Unhandled exception Product: Wine Version: 1.5.22 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: marcus.blumhagen(a)web.de Classification: Unclassified Created attachment 43231 --> http://bugs.winehq.org/attachment.cgi?id=43231 console output, when not requesting crash details Overview "Core/rFactor2 Dedicated.exe", run from the root dirctory of the application, crashes. Steps to reproduce (There is no purchase required for running the dedicated server, so by following below steps anybody can try and reproduce the above behaviour.) 1. Download "rFactor2 full installer" (currently Build 134) from http://rfactor.net/web/rf2/rf2dl/. Also download at least one .rfmod file from the category "Content (cars, tracks, etc)". I´d recommend "2012 FIA Formula Two", since it has no updates yet, no dependencies on other content and is comparably small, thus making its installation the least troublesome. 2.a Install rFactor2, take a note of where you choose the "Data and Settings Destination Folder" to be, or make it the same as the "Core Destination Folder". 2.b Put your .rfmod file(s) into the "Packages" directory inside the "Data and Settings Destination Folder". 2.c Change directory to the "Core Destination Folder", run "Core/ModMgr.exe" and Install the Mod(s) 3. Still in the "Core Destination Folder", run "Core/rFactor2\ Dedicated.exe". Leave the default settings by clicking the bottom right button in the first 3 windows that appear. Then assign a "Race Name" (top left) on the last dialog (the one that has "Load Track" written on the bottom right button). Then click "Load Track"... Actual Result The server starts loading but crashes in the process after a short time and the following message is output on the terminal: "wine: Unhandled exception 0xc0000417 in thread 29 at address 0x5369bc (thread 0029), starting debugger..." Also, the crash window of wine titled "Program Error" comes up, but when I click "Show Details", the window of "rFactor2 Dedicated.exe" is closed immediately and the window "Program Error Details" pops up but won´t show any details, it stays at: "Loading detailed information, please wait..." Whereas, when after the crash I choose to close the "Program Error" window there is more information on the terminal, see the attachment. Expected Result A running rFactor 2 dedicated server. Build date & Platform Build date: 2013-01-19 gcc --version: gcc (Debian 4.7.2-5) 4.7.2 wine --version: wine-1.5.22 Build and run environment is a chroot containing Debian Sid i386, host is Debian 6.0.6 (Squeeze). Build dependencies were installed by "apt-get build-dep wine" Additional information The program was run semi-successfully already, but I cannot reproduce it anymore. But even then it crashed more than 75% of the time with the symptoms described above. When it successfully launched, the server sometimes could not connect to the matchmaker. Not knowing, which component ist at fault, I tried a run with WINEDEBUG=trace+all, but after half an hour and seeing the log grow to more than 2.2 GB, I gave up. -- 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 14