March 2025 - Wine-bugs - list.winehq.org

[Bug 54352] New: Performance tanks when looking at occluded part of the level
by WineHQ Bugzilla 25 Nov '25

25 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=54352 Bug ID: 54352 Summary: Performance tanks when looking at occluded part of the level Product: Wine Version: 8.0-rc4 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: mirh(a)protonmail.ch https://github.com/doitsujin/dxvk/issues/1845 This is basically the equivalent of the missed optimization I had already reported to dxvk (except wined3d had like half the framerate to begin with). With the native nvidia d3d9 driver, you barely can spot a difference in the Mass Effect comm room between looking at the emptiest wall in human history, or the closed door behind that gives access to the rest of the ship. With wined3d, I go from like 220fps to ~70. Btw there's an apitrace in the thread above, if it can help. -- 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 2

[Bug 56470] New: Wined3d has windows always sitting in background
by WineHQ Bugzilla 25 Nov '25

25 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=56470 Bug ID: 56470 Summary: Wined3d has windows always sitting in background Product: Wine Version: 9.5 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: mirh(a)protonmail.ch So.. as I always do every few month, I try to see if wined3d finally holds a candle for helping with games in Windows. This time I was surprised by a constant 30FPS lock, despite the fact both my game of choice settings and the external tools profiles for its executable didn't have one (indeed if I removed wine's dlls, native d3d9 could easily get almost 10 times as much framerate) Long story short, after some time banging my head I figured this was happening because "Background Application Max Frame Rate" was enabled in the nvidia control panel. Problem being of course that a foreground fullscreen window definitively isn't supposed to be affected by that. This does not happen with normal opengl games (even after I renamed their exe, just to be extra safe about whitelisting and whatnot) so it seems something on your side of things. -- 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 4

[Bug 44021] New: LiveMaker engine fails to find font despite overrides set up
by wine-bugs＠winehq.org 25 Nov '25

25 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=44021 Bug ID: 44021 Summary: LiveMaker engine fails to find font despite overrides set up Product: Wine Version: 2.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- Going by https://github.com/xupefei/Locale-Emulator/issues/80, doesn't access the font in question (MS Gothic) directly, yet despite its overrides being set up correctly (HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\FontSubstitutes: both English and Japanese names), the engine crashes unless that font is actually present in drive_c/windows/Fonts. It might be that this can't be done as font matching/replacing takes place at much later stage, yet would be nice if someone could verify one way or the other. Perhaps those names should simply hardcoded to be returned in Japanese locale, regardless of the fonts being actually present ? Cause before Windows 10 (which has a different Japanese font), they couldn't not be there after a proper Japanese Windows install. -- 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 53819] New: some versions of Unity engine need GetWindowTheme implemented to properly display crash dialog
by WineHQ Bugzilla 25 Nov '25

25 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=53819 Bug ID: 53819 Summary: some versions of Unity engine need GetWindowTheme implemented to properly display crash dialog Product: Wine Version: 7.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: uxtheme Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- So, I've stumbled upon a Unity engine game that crashes every now and then due to what seems to be virtual mapping space exhaustion. Not sure about the crash itself - it's more likely to be graphics related that winegstreamer, but that's just a guess. Anyway, once the crash happens, console is flooded by: 03b0:err:module:DelayLoadFailureHook failed to delay load uxtheme.dll.GetWindowTheme wine: Call from 7B0123C6 to unimplemented function uxtheme.dll.GetWindowTheme, aborting 03b0:err:seh:KiUserCallbackDispatcher ignoring exception and the Unity crash dialog doesn't display properly. -- 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 4

[Bug 56447] New: PlayOnline Viewer: The "splash screen" is blank/grey without its image.
by WineHQ Bugzilla 23 Nov '25

23 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=56447 Bug ID: 56447 Summary: PlayOnline Viewer: The "splash screen" is blank/grey without its image. Product: Wine Version: 9.4 Hardware: x86-64 URL: https://web.archive.org/web/20210810150839/http://www. playonline.com/ff11eu/download/media/install_win.html OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chiitoo(a)gentoo.org Distribution: Gentoo This is a very old one, but as far as I can tell, not reported until now (aside from some side-mentions). PlayOnline Viewer, which is used to launch Final Fantasy XI Online, has a blank/grey window for its "splash screen". It has been working in Wine Staging for some time. Not sure if related, but comparing the logging between runs, each of these show up twice with Vanilla but only once with Staging: err:d3d:wined3d_fence_wait glClientWaitSync returned 0x911b. err:d3d:wined3d_context_gl_wait_command_fence Failed to wait for command fence with id 0x1, ret 0x4. err:d3d:wined3d_fence_wait glClientWaitSync returned 0x911b. err:d3d:wined3d_context_gl_wait_command_fence Failed to wait for command fence with id 0x2, ret 0x4. -- 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 3

[Bug 46568] New: 64-bit msxml6.dll from Microsoft Core XML Services 6.0 redist package fails to load (Wine doesn't respect 44-bit user-mode VA limitation from Windows < 8.1)
by wine-bugs＠winehq.org 22 Nov '25

22 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=46568 Bug ID: 46568 Summary: 64-bit msxml6.dll from Microsoft Core XML Services 6.0 redist package fails to load (Wine doesn't respect 44-bit user-mode VA limitation from Windows < 8.1) Product: Wine Version: 4.0 Hardware: x86-64 URL: https://download.microsoft.com/download/2/e/0/2e01308a -e17f-4bf9-bf48-161356cf9c81/msxml6_x64.msi OS: Linux Status: NEW Keywords: download, win64 Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, reported by Louis in https://bugs.winehq.org/show_bug.cgi?id=46107#c2 --- quote --- I tried winetricks msxml3 and msxml6, but somehow it didn`t work out in 64-bit wineprefix; i get errors that msxml is not registered etc, Does anyone know a workaround to use native msxml on 64-bit prefix? --- quote --- Relevant part of trace log: --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files/Altium/AD18 $ WINEDEBUG=+seh,+relay,+loaddll,+virtual wine64 ./X2.EXE >>log.txt 2>&1 ... 002a:Call KERNEL32.LoadLibraryExW(0053f2b0 L"C:\\windows\\system32\\msxml6.dll",00000000,00000008) ret=7fbe435d7558 ... 002a:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\msxml6.dll" at 0x7ff79e00000: native 002a:Call PE DLL (proc=0x7ff79e0101c,module=0x7ff79e00000 L"msxml6.dll",reason=PROCESS_ATTACH,res=(nil)) ... 002a:Call KERNEL32.HeapCreate(00000001,00000000,00000000) ret=7ff79e18411 002a:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00110000 2000 00000004 002a:trace:virtual:map_view got mem with anon mmap 0x7fbe39819000-0x7fbe39929000 002a:trace:virtual:VIRTUAL_DumpView View: 0x7fbe39820000 - 0x7fbe3992ffff (valloc) 002a:trace:virtual:VIRTUAL_DumpView 0x7fbe39820000 - 0x7fbe3992ffff --rw- 002a:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff 0x7fbe39820000 00010000 1000 00000004 002a:trace:virtual:mprotect_exec forcing exec permission on 0x7fbe39820000-0x7fbe3982ffff 002a:trace:virtual:VIRTUAL_DumpView View: 0x7fbe39820000 - 0x7fbe3992ffff (valloc) 002a:trace:virtual:VIRTUAL_DumpView 0x7fbe39820000 - 0x7fbe3982ffff c-rw- 002a:trace:virtual:VIRTUAL_DumpView 0x7fbe39830000 - 0x7fbe3992ffff --rw- 002a:Ret KERNEL32.HeapCreate() retval=7fbe39820000 ret=7ff79e18411 ... 002a:Call ntdll.RtlAllocateHeap(7fbe39820000,00000000,00000060) ret=7ff79e03c10 002a:Ret ntdll.RtlAllocateHeap() retval=7fbe39822730 ret=7ff79e03c10 002a:Call msvcrt.memset(7fbe39822740,00000000,00000042) ret=7ff79e03a5a 002a:Ret msvcrt.memset() retval=7fbe39822740 ret=7ff79e03a5a 002a:trace:seh:NtRaiseException code=c0000005 flags=0 addr=0x7ff79e03efe ip=7ff79e03efe tid=002a 002a:trace:seh:NtRaiseException info[0]=0000000000000000 002a:trace:seh:NtRaiseException info[1]=ffffffffffffffff 002a:trace:seh:NtRaiseException rax=000000000011b2d0 rbx=6c61567274736270 rcx=0000000000000008 rdx=0000000000000000 002a:trace:seh:NtRaiseException rsi=0000000000007fbe rdi=0000000000000730 rbp=00000ff7c73044e8 rsp=000000000053ea70 002a:trace:seh:NtRaiseException r8=00007fbe39822740 r9=0000000000000000 r10=0000000000000000 r11=0000000000000000 002a:trace:seh:NtRaiseException r12=00007fbe39822740 r13=000007ff79f8dc80 r14=00007fbe436c6160 r15=000000000053f708 ... 002a:exception c0000005 in PE entry point (proc=0x7ff79e0101c,module=0x7ff79e00000,reason=PROCESS_ATTACH,res=(nil)) 002a:Ret PE DLL (proc=0x7ff79e0101c,module=0x7ff79e00000 L"msxml6.dll",reason=PROCESS_ATTACH,res=(nil)) retval=0 002a:Call PE DLL (proc=0x7ff79e0101c,module=0x7ff79e00000 L"msxml6.dll",reason=PROCESS_DETACH,res=(nil)) 002a:Ret PE DLL (proc=0x7ff79e0101c,module=0x7ff79e00000 L"msxml6.dll",reason=PROCESS_DETACH,res=(nil)) retval=1 002a:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\msxml6.dll" : native 002a:Ret KERNEL32.LoadLibraryExW() retval=00000000 ret=7fbe435d7558 002a:err:ole:COMPOBJ_DllList_Add couldn't load in-process dll L"C:\\windows\\system32\\msxml6.dll" --- snip --- It seems that certain older 64-bit components such as Microsoft XML libs make assumptions about the 64-bit user-mode virtual address space layout. This is different from the usual broken apps a la "I failed at porting my 32-bit app to 64-bit" (pointer truncation). In this case, pointers from certain allocations are broken into multiple parts and used as indices into multi-level lookup tables. Pitfall: there is a 44-bit user-mode VA limitation (8TB) for 64-bit Windows which was lifted starting with Windows 8.1+. Wine doesn't respect the 44-bit pre-Windows 8.1 virtual address space limits, allowing process heaps to be placed in 0000'7Fxx'0000'0000 range (128 TB) which causes out-of-bounds access to lookup tables when indices overflow (derived from pointer bits). The exception occurs in entry point, causing 'msxml6.dll' to be unloaded. One workaround is to move Wine's top-down allocations/heaps into 8 TB VA range (Wine preloader) and impose same user-mode address space bits limits as with all 64-bit Windows versions < 8.1 to stay "compatible". I've tested it and it works for native here. Not sure if it's worth to change though. I don't know if a separate 64-bit MSXML6 re-distributable package exists that has been fixed wrt Windows 8.1+ address space limits. MSXML6 is part of Windows OS for newer versions and automatically kept up-to-date. $ sha1sum msxml6_x64.msi 1eb84eeae7729ea5db7fe79779f4e216114261ba msxml6_x64.msi $ du -sh msxml6_x64.msi 2.6M msxml6_x64.msi $ wine --version wine-4.0-276-g84459ba94b Regards -- 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 17

[Bug 15039] New: MSVC 6: Menu popdowns too narrow for arrows
by wine-bugs＠winehq.org 22 Nov '25

22 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=15039 Summary: MSVC 6: Menu popdowns too narrow for arrows Product: Wine Version: 1.1.1 Platform: PC-x86-64 OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: claus.fischer(a)clausfischer.com CC: claus.fischer(a)clausfischer.com Microsoft Visual C++ 6 is working to a large extent. When opening a menu of the developer studio, the menu items with arrows (that open submenus) are not displayed correctly. The triangular arrows on the right end will stick out of the menu popdown area. I'm not sure if they just stick out to the end of the "shadow" (3d effect) around the popdown, or sometimes more. They should be fully contained in the popdown area. -- 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 23

[Bug 40574] New: bbtalk.exe wont start
by wine-bugs＠winehq.org 22 Nov '25

22 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=40574 Bug ID: 40574 Summary: bbtalk.exe wont start Product: Wine Version: 1.9.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: eore26(a)gmail.com Distribution: --- Created attachment 54413 --> https://bugs.winehq.org/attachment.cgi?id=54413 Program error detail Unhandled Exception -- 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

[Bug 43985] New: I could not run my g ame 梦幻西游
by wine-bugs＠winehq.org 22 Nov '25

22 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=43985 Bug ID: 43985 Summary: I could not run my game 梦幻西游 Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: yizhongwang(a)yahoo.com CC: michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- I could not run my game -- 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 54979] New: Futexes which protect memory allocation congest, causing 100x performance degradation
by WineHQ Bugzilla 21 Nov '25

21 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=54979 Bug ID: 54979 Summary: Futexes which protect memory allocation congest, causing 100x performance degradation Product: Wine Version: 8.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: nagle(a)animats.com Distribution: --- Created attachment 74518 --> https://bugs.winehq.org/attachment.cgi?id=74518 Debugger output with multiple threads stuck in spinlocks. SUMMARY Under the wrong circumstances, a program doing many memory allocations from multiple threads can experience more than 100x performance degradation. I'm seeing this in my own Rust program, which has 16 sometimes-compute-bound threads on a 12 CPU machine. This works fine on Microsoft Windows and when compiled for Linux. Under Wine, it can be over 100x slower. Multiple threads are banging on a spinlock at _InterlockedCompareExchange [Z:\usr\src\packages\BUILD\include\winnt.h:6630] in ntdll spin_lock [Z:\usr\src\packages\BUILD\dlls\ntdll\sync.c:937] in ntdll This is the spin lock around the queue for pausing threads. DISCUSSION This looks like futex congestion. That's a known kind of problem, but doesn't seem to have been seen in Wine before. It may be that some programs just run really slow under Wine, and nobody knows why. The code in NTDLL is clearly intended to handle the fast case without doing an OS-level lock. Under light load, that's O(1). But under heavy load, with multiple threads pounding on spinlocks, each spinlock waits longer, and there are multiple threads, so it becomes O(N^2). Which means huge slowdowns. See discussion at https://forum.winehq.org/viewtopic.php?t=37688 which has snippets of the code that's causing the problem. I can copy all that info over here if necessary. Let me know. -- 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 19