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

[Bug 53711] Final Fantasy XI crashes randomly at multiple points

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53711 --- Comment #22 from pandora.xero(a)gmail.com --- (In reply to Zeb Figura from comment #21) > Hmm, the log from comment 17 doesn't quite match what you reported wrt the > virtual memory size increasing by 20 MB each time. There are a couple > increases but not enough for me to be sure of where they're coming from. > > I think it's pretty clear that we're running out of memory, especially given > the maps file from comment 20 at the time of the crash, but I'm still not > confident of why. The amount of mapped GPU memory is 418 MiB, which is not > so high as to be a smoking gun, but the rest of it is anonymous. > > Here's what I can tell from analyzing the +virtual log and map files from > comment 20: > > * the low "reserved" area of 0 - 0x20000000 is not much fuller at crash time > than it is at open time; > > * also, NtAllocateVirtualMemory only ever returns memory inside that > reserved area (with I think one exception, but that memory is freed); > > * amount of mapped GPU memory (/dev/renderD128) is higher at crash time than > open time, but not really so high as to be a smoking gun (418 MiB vs 342 > MiB); > > * amount of anonymous mapped memory in the non-reserved area (0x20000000 - > 0x7f000000) is way higher at 'crash' time than 'open' time. > > So I think that whatever memory is being leaked, is not being allocated by > the Wine side. This doesn't necessarily mean that it's not Wine's fault it's > being leaked (and I would probably assume it is Wine's fault), but it is > useful information nonetheless. > > I think this means we can rule out d3d memory; sysmem should go through > NtAllocateVirtualMemory, and GPU memory *should* be DMA mapped. Unless > radeonsi is ever going to give us anonymous mapped memory? > > I'll have to think about how to narrow it down further, though. Well, whenever you have an idea, it seems all I need to make the game crash is about 5 or 6 hours managing inventory between all my characters. -- 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.

Sept. 30, 2022

[Bug 53711] Final Fantasy XI crashes randomly at multiple points

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53711 --- Comment #21 from Zeb Figura <z.figura12(a)gmail.com> --- Hmm, the log from comment 17 doesn't quite match what you reported wrt the virtual memory size increasing by 20 MB each time. There are a couple increases but not enough for me to be sure of where they're coming from. I think it's pretty clear that we're running out of memory, especially given the maps file from comment 20 at the time of the crash, but I'm still not confident of why. The amount of mapped GPU memory is 418 MiB, which is not so high as to be a smoking gun, but the rest of it is anonymous. Here's what I can tell from analyzing the +virtual log and map files from comment 20: * the low "reserved" area of 0 - 0x20000000 is not much fuller at crash time than it is at open time; * also, NtAllocateVirtualMemory only ever returns memory inside that reserved area (with I think one exception, but that memory is freed); * amount of mapped GPU memory (/dev/renderD128) is higher at crash time than open time, but not really so high as to be a smoking gun (418 MiB vs 342 MiB); * amount of anonymous mapped memory in the non-reserved area (0x20000000 - 0x7f000000) is way higher at 'crash' time than 'open' time. So I think that whatever memory is being leaked, is not being allocated by the Wine side. This doesn't necessarily mean that it's not Wine's fault it's being leaked (and I would probably assume it is Wine's fault), but it is useful information nonetheless. I think this means we can rule out d3d memory; sysmem should go through NtAllocateVirtualMemory, and GPU memory *should* be DMA mapped. Unless radeonsi is ever going to give us anonymous mapped memory? I'll have to think about how to narrow it down further, though. -- 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.

Sept. 30, 2022

[Bug 53744] WM_SETTEXT between ANSI programs treating LPARAM as Unicode causing name corruption

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53744 dark(a)darkok.xyz changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |testcase -- 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.

Sept. 30, 2022

[Bug 53744] WM_SETTEXT between ANSI programs treating LPARAM as Unicode causing name corruption

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53744 --- Comment #2 from dark(a)darkok.xyz --- Created attachment 73189 --> https://bugs.winehq.org/attachment.cgi?id=73189 Receives WM_SETTEXT -- 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.

Sept. 30, 2022

[Bug 53744] WM_SETTEXT between ANSI programs treating LPARAM as Unicode causing name corruption

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53744 --- Comment #1 from dark(a)darkok.xyz --- Created attachment 73188 --> https://bugs.winehq.org/attachment.cgi?id=73188 Sends WM_SETTEXT -- 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.

Sept. 30, 2022

[Bug 53744] WM_SETTEXT between ANSI programs treating LPARAM as Unicode causing name corruption

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53744 dark(a)darkok.xyz changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |d42888f07c6e3e491c99bb5c8b6 | |2b568264e990c Keywords| |regression -- 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.

Sept. 30, 2022

[Bug 53744] New: WM_SETTEXT between ANSI programs treating LPARAM as Unicode causing name corruption

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53744 Bug ID: 53744 Summary: WM_SETTEXT between ANSI programs treating LPARAM as Unicode causing name corruption Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: dark(a)darkok.xyz Distribution: --- When sending a WM_SETTEXT to and from a program expecting ANSI strings, it seems to be interpreting the string as Unicode, causing the window title to become corrupted. Sending a wide string over then makes it work on Wine, but not Windows. The issue was introduced in Wine 7.6, and still exists in the latest versions. -- 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.

Sept. 30, 2022

[Bug 53711] Final Fantasy XI crashes randomly at multiple points

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53711 pandora.xero(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #73186|0 |1 is obsolete| | --- Comment #20 from pandora.xero(a)gmail.com --- Created attachment 73187 --> https://bugs.winehq.org/attachment.cgi?id=73187 20220930 - maps, log, backtrace (Correction to originally-uploaded file issued because incorrect file extension was causing the file type to be misidentified. No idea how I failed to catch this sooner.) This .tar.xz contains: winelog.log - full log file +pid,+virtual,+timestamp backtrace.txt - backtrace from crash mapopen.map - memory map from just after my first character login mapcrash.map - memory map from time of crash maplaunch.stamp - contains timestamp for when wine was launched, as well as the WINEDEBUG channels. mapopen.stamp - contains timestamp for the first memory map mapcrash.stamp - contains timestamp for the memory map at time of crash The log file is too large to post uncompressed - around 55MB. I'm not sure it'll be of much use, either, except for correlation purposes. -- 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.

Sept. 30, 2022

[Bug 53711] Final Fantasy XI crashes randomly at multiple points

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53711 --- Comment #19 from pandora.xero(a)gmail.com --- Created attachment 73186 --> https://bugs.winehq.org/attachment.cgi?id=73186 more log and map dumps This .tar.xz contains: winelog.log - full log file +pid,+virtual,+timestamp backtrace.txt - backtrace from crash mapopen.map - memory map from just after my first character login mapcrash.map - memory map from time of crash maplaunch.stamp - contains timestamp for when wine was launched, as well as the WINEDEBUG channels. mapopen.stamp - contains timestamp for the first memory map mapcrash.stamp - contains timestamp for the memory map at time of crash The log file is too large to post uncompressed - around 55MB. I'm not sure it'll be of much use, either, except for correlation purposes. -- 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.

Sept. 30, 2022

[Bug 53718] WoW Beta/PTR get "Your 3D accelorator card is not supported"

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53718 --- Comment #24 from nerzhul <loic.blot(a)unix-experience.fr> --- i'll try to test various wine packages bisecting version fixing it this weekend -- 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.

Sept. 30, 2022