[Bug 30415] New: wineserver leaks memory when running Crysis Wars dedicated server
http://bugs.winehq.org/show_bug.cgi?id=30415 Bug #: 30415 Summary: wineserver leaks memory when running Crysis Wars dedicated server Product: Wine Version: 1.4 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: liquitsnake(a)gmx.net Classification: Unclassified The Crysis Wars dedicated server, especially with the MWLL mod and many players, leaks a lot of memory. 5 to 10 MB/minute are not unusual. This happens on Windows too, can't be fixed and is not subject of this bug report. On Wine however, the wineserver process leaks memory alongside the Crysis Wars process! In fact, wineserver leaks even faster, more than doubling the memory load on my machine at a given time. Wineserver's leak is the subject of this bug report. Wineserver will not release its memory when Crysis quits. In fact, the only way to do that is to quit wineserver, either by killing it, or by closing all Wine applications and waiting for wineserver to quit on its own. I'll be happy to provide any info needed to help debug this. I don't know where to even start though. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=30415 Dan Kegel <dank(a)kegel.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dank(a)kegel.com --- Comment #1 from Dan Kegel <dank(a)kegel.com> 2012-04-11 18:21:20 CDT --- You could try running wineserver -f under valgrind --leak-check=yes , see http://valgrind.org/docs/manual/quick-start.html and http://www.winehq.org/docs/wineserver -- 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.
http://bugs.winehq.org/show_bug.cgi?id=30415 --- Comment #2 from haarp <liquitsnake(a)gmx.net> 2012-04-12 10:25:40 CDT --- Created attachment 39768 --> http://bugs.winehq.org/attachment.cgi?id=39768 First run with valgrind This is my first time using valgrind, so bear with me. It looks like this log doesn't yield anything useful. I started wineserver through valgrind as per comment 1, then Crysis and let it run for a while. Then I played on the server until valgrind/wineserver's memory consumption increased by around 30MB. Then I shut them down. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=30415 haarp <liquitsnake(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #39768|0 |1 is obsolete| | --- Comment #3 from haarp <liquitsnake(a)gmx.net> 2012-04-13 14:08:27 CDT --- Created attachment 39788 --> http://bugs.winehq.org/attachment.cgi?id=39788 second run with --show-reachable=yes I did a second run and enabled --show-reachable. I let it leak around 500MB this time. As far as I can tell, valgrind didn't catch any of that. Not sure what to do about that, but I'm open for suggestions. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=30415 --- Comment #4 from Austin English <austinenglish(a)gmail.com> --- This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.18 or newer) wine? -- 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=30415 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED --- Comment #5 from Austin English <austinenglish(a)gmail.com> --- (In reply to Austin English from comment #4)
This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.18 or newer) wine?
Abandoned. -- 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=30415 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #6 from Austin English <austinenglish(a)gmail.com> --- Closing. -- 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=30415 --- Comment #7 from haarp <main.haarp(a)gmail.com> --- Just a small follow-up on this a few years later. I tested Wine 1.8.3 on Debian, and this bug appears to be fixed. Sorry that I never got to test this with a newer version until now. Cheers! -- 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)
-
wine-bugs＠winehq.org