[Bug 48197] New: Autonauts in steam under wine has a memory leak.
https://bugs.winehq.org/show_bug.cgi?id=48197 Bug ID: 48197 Summary: Autonauts in steam under wine has a memory leak. Product: Wine Version: 4.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: eeknaak(a)gmail.com Distribution: --- Created attachment 65834 --> https://bugs.winehq.org/attachment.cgi?id=65834 Hard_info report Running Autonauts.exe under wine 4.20 has a constant memory leak. Running it native on windows doesn't have a leak. https://github.com/EricKnaak/computerfacts/blob/master/pc%20specs OS: Ubuntu 18.04 wine: 4.20 steam for linux: Built: Nov 20 2019, at 01:49:33 Autonauts.exe won't run in valgrind due to lack of support of IRET/IRETD — Interrupt Return. I learned about Valgrind and how to compile again. I don't see anything I can do to gather any more info on this problem. -- 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=48197 eeknaak(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu -- 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=48197 eeknaak(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu -- 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=48197 eeknaak(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu -- 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=48197 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |leslie_alistair(a)hotmail.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.
https://bugs.winehq.org/show_bug.cgi?id=48197 --- Comment #1 from eeknaak(a)gmail.com --- https://bugs.kde.org/show_bug.cgi?id=414659 Is the bug report on trying to nail down the memory leak. They said I can't use valgrind on a IRET/IRETD using program. also maybe they said I can???? Either way I can't build the latest version of valgrind to run Autonauts. keeps complaining of missing 32bit libraries or that I can't build 32bit on a 64 bit computer. -- 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=48197 --- Comment #2 from eeknaak(a)gmail.com --- Created attachment 65843 --> https://bugs.winehq.org/attachment.cgi?id=65843 Save file that exacerbates memory leak. Autonauts icho version game save -- 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=48197 --- Comment #3 from eeknaak(a)gmail.com --- Game download Link: https://denki.itch.io/autonauts Since this is a wine issue download one of the windows versions. issue is found in the 64 bit version. To replicate the memory issue. Version of wine used in this replicate is 4.20. 1. Download Autonauts 2. Extract Autonauts 3. Download "Save file that exacerbates memory leak." (https://bugs.winehq.org/attachment.cgi?id=65843) and put it into .../Autonauts_Version_21.2_Windows x64/Autosaves/Autosaves 4. run Autonauts.exe (in folder Autonauts_Version_21.2_Windows x64) using wine 5. wait 15 minutes and memory leak should have taken up more memory. -- 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=48197 eeknaak(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eeknaak(a)gmail.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.
https://bugs.winehq.org/show_bug.cgi?id=48197 --- Comment #4 from eeknaak(a)gmail.com --- 5. Hit "esc" key. click load. click memoryleak.txt. then click open. click yes. *5. wait 15 minutes and memory leak should have taken up more memory. -- 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=48197 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish(a)gmail.com Keywords| |download URL| |https://denki.itch.io/auton | |auts --- Comment #5 from Austin English <austinenglish(a)gmail.com> --- (In reply to eeknaak from comment #1)
https://bugs.kde.org/show_bug.cgi?id=414659 Is the bug report on trying to nail down the memory leak. They said I can't use valgrind on a IRET/IRETD using program. also maybe they said I can???? Either way I can't build the latest version of valgrind to run Autonauts. keeps complaining of missing 32bit libraries or that I can't build 32bit on a 64 bit computer.
The patch isn't in a release yet, so yes, you'll need to build from source. For valgrind to work on 32-bit binaries, much like Wine, you'll need 32-bit libraries available. It's outside of the scope of wine bugzilla, but something like `sudo apt-get build-dep valgrind` may help. You might also find the suppression lists at https://github.com/austin987/wine-valgrind-scripts useful, to avoid looking for known issues. Does the 32-bit version also have a leak? If so, that's probably easier to debug. -- 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=48197 --- Comment #6 from eeknaak(a)gmail.com --- I'll look into seeing if I can find the leak in wine using the 32bit exe. I'll attempt valgrind again with build-dep. and see if that works. -- 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=48197 --- Comment #7 from eeknaak(a)gmail.com --- eric(a)eric-MS-7752:~/Downloads/valgrind-3.15.0$ sudo apt build-dep valgrind Reading package lists... Done E: Unable to find a source package for valgrind No source package for valgrind. Using valgrind on the 32 bit autonauts (valgrind --trace-children=yes --vex-iropt-register-updates=allregs-at-mem-access wine ~/Downloads/Autonauts_Version_21.2_Windows\ x86/Autonauts.exe ) resulted in error: ==3879== 0009:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 0009:err:winediag:nodrv_CreateWindow The explorer process failed to start. ==3879== ==3879== HEAP SUMMARY: ==3879== in use at exit: 205,114 bytes in 5,504 blocks ==3879== total heap usage: 95,339 allocs, 89,835 frees, 146,776,918 bytes allocated . I am really bad with any thing graphical. Usually when I need to do a reinstall of ubuntu it is because I can't get anything to display on the screen. I tried throwing DISPLAY=:0 in different parts of that command, and before calling that command and no change to the outcome. I'll try again tomorrow morning. -- 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=48197 --- Comment #8 from eeknaak(a)gmail.com --- maybe an issue was I didn't enable source code repos, under ubuntu. -- 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=48197 --- Comment #9 from eeknaak(a)gmail.com --- Starting to look like I will be unable to attempt to use updated valgrind, due to compiling code being to complex for me to learn. I have given all info I have on this bug and some way of tracing the memory leak is needed. -- 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=48197 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #10 from joaopa <jeremielapuree(a)yahoo.fr> --- Does the bug still occur with wine-6.20? -- 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=48197 --- Comment #11 from eeknaak(a)gmail.com --- I tested 6.20 64bit wine with: OS: Ubuntu 18.04 64bit playonlinux: 4.3.4 using system wine version 6.20 used playonlinux only as a graphical way to run wine. Followed steps on comment 3. There was no noticeable memory leak from looking on system monitor. I think I would consider this resolved. -- 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=48197 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #12 from Austin English <austinenglish(a)gmail.com> --- (In reply to eeknaak from comment #11)
I tested 6.20 64bit wine with: OS: Ubuntu 18.04 64bit playonlinux: 4.3.4 using system wine version 6.20
used playonlinux only as a graphical way to run wine.
Followed steps on comment 3. There was no noticeable memory leak from looking on system monitor.
I think I would consider this resolved.
Reported fixed. -- 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=48197 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #13 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 7.20. -- 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