[Bug 52234] New: wine double free or corruption
https://bugs.winehq.org/show_bug.cgi?id=52234 Bug ID: 52234 Summary: wine double free or corruption Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: axet(a)me.com Distribution: --- Wine 6.21 double free or corruption when network enabled (wifi) and starts normally when wifi is disabled. Only x64 prefixes are affected, x32 prefixes starts normally. Looks like malicious code but I have no prove or suspicions actions beside wine freeze at start with network enabled. First discovered using lutris-6.21-6 https://github.com/lutris/wine/issues/128 Simple inspection with 'strace' WINEDEBUG wireshard give me no results. Only wine 6.21 affected. It is worth digging? I'm using this command to start / create prefix: WINEPREFIX=$PWD/123 ~/.local/share/lutris/runners/wine/winehq-6.21-x86_64/bin/wineboot -- 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.
https://bugs.winehq.org/show_bug.cgi?id=52234 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de --- Comment #1 from Fabian Maurer <dark.shadow4(a)web.de> --- Since newer versions work, it could either be fixed, or just be random and not appear out of chance... You could try using valgrind to figure out what causes this, this should allow you to track down where it happens. It doesn't crash for me. Although I have to ask - does it happen with the official winehq packages? Not sure what lutris does on top of them. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=52234 --- Comment #2 from Alexey Kuznetsov <axet(a)me.com> --- I'm reporting here, since winehq (official binaries) act like I described above. Lutris version, was the first place I report the bug because it has same symptoms as official release (it was discovered later, since I suspect lutris at first). I'm using Debian 12 bookworm. Vagrant does not detect anything: WINEPREFIX=$PWD/123 valgrind ~/.local/share/lutris/runners/wine/winehq-6.21-x86_64/bin/wineboot ==312627== Memcheck, a memory error detector ==312627== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==312627== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info ==312627== Command: /home/axet/.local/share/lutris/runners/wine/winehq-6.21-x86_64/bin/wineboot ==312627== wine: created the configuration directory '/media/axet/Games/Path of Exile/123' 002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 0048:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 0050:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) double free or corruption (out) Command does not return I had to Ctrl+C and killall... -- 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.
https://bugs.winehq.org/show_bug.cgi?id=52234 --- Comment #3 from Fabian Maurer <dark.shadow4(a)web.de> --- I think for valgrind you have to use something like this: WINELOADERNOEXEC=1 valgrind wine wineboot -- 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.
https://bugs.winehq.org/show_bug.cgi?id=52234 --- Comment #4 from Alexey Kuznetsov <axet(a)me.com> --- Try run it twice. First run works! Booth winehq and lutris. And next run dosen't, even if you reboot the machine or delete the wine folder it will not recover and keep crashing with memory error. Looks like and act like a virus (sine first run works), but I have no prove (no idea how to detect it). Beside it wont run x64 prefixes. I also have checked original wine directory and 'diff -r' (binary compare) it is unchanged. So, no body changed the wine directory. My conclusion was it could be bug in wine. And only wine-6.21 affected. All before and later up to 7.0-rc1 works. I guess vlgrind could help, but I never used it before. And your suggestion fails with a lot of errors. Booth failed with errors: WINEPREFIX=$PWD/123 WINELOADERNOEXEC=1 valgrind ~/.local/share/lutris/runners/wine/winehq-6.21-x86_64/bin/wine wineboot or WINEPREFIX=$PWD/123 WINELOADERNOEXEC=1 valgrind ~/.local/share/lutris/runners/wine/winehq-6.21-x86_64/bin/wineboot -- 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.
https://bugs.winehq.org/show_bug.cgi?id=52234 --- Comment #5 from Fabian Maurer <dark.shadow4(a)web.de> --- As I said, it works just fine for me. For valgrind, I get over 1000 errors as well. Probably won't help track it down then. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=52234 --- Comment #6 from Alexey Kuznetsov <axet(a)me.com> --- I found what is causing it. Very strange. Having those files in ~/.cache/AMD/VkCache directory causing wine to crash with double corrupt message: A21E3B76F983AB25CAD2A47E19EFB13B_1.parc A21E3B76F983AB25CAD2A47E19EFB13B_4.parc A21E3B76F983AB25CAD2A47E19EFB13B_7.parc A21E3B76F983AB25CAD2A47E19EFB13B.parc A21E3B76F983AB25CAD2A47E19EFB13B_2.parc A21E3B76F983AB25CAD2A47E19EFB13B_5.parc A21E3B76F983AB25CAD2A47E19EFB13B_8.parc A21E3B76F983AB25CAD2A47E19EFB13B_3.parc A21E3B76F983AB25CAD2A47E19EFB13B_6.parc A21E3B76F983AB25CAD2A47E19EFB13B_9.parc I'm using AMD video card with (amdvlk:amd64 2021.Q4.2) installed from official repository. This vlk cache is lutris-6.21-6 dependent (or official winehq-6.21). files: * https://disk.yandex.ru/d/ZmIVKwyNbuTDiQ AMD video driver: * https://github.com/GPUOpen-Drivers/AMDVLK -- 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.
https://bugs.winehq.org/show_bug.cgi?id=52234 --- Comment #7 from Alexey Kuznetsov <axet(a)me.com> --- Reinstalling AMDVLK causing this "wired" cache appear again in smaller size (10M) and causing corruption again https://disk.yandex.ru/d/vXEmUl5DAVjGFg -- 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.
https://bugs.winehq.org/show_bug.cgi?id=52234 --- Comment #8 from Fabian Maurer <dark.shadow4(a)web.de> --- So, does it work with mesa? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=52234 --- Comment #9 from Alexey Kuznetsov <axet(a)me.com> --- Sure it works. radv not using this wired .cache/AMD folder at all. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=52234 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED --- Comment #10 from Austin English <austinenglish(a)gmail.com> --- (In reply to Alexey Kuznetsov from comment #9)
Sure it works. radv not using this wired .cache/AMD folder at all.
Sounds like an AMD bug then.. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=52234 songxy <sxy_sdy(a)163.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sxy_sdy(a)163.com -- 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.
participants (1)
-
WineHQ Bugzilla