https://bugs.winehq.org/show_bug.cgi?id=48225
Bug ID: 48225 Summary: StoneHearth, Radiant Entertainment, available from Steam. Too many open files error Product: Wine Version: 4.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: wine@zootal.com Distribution: ---
Game installs and plays, but after 5-10 minutes of game play, this appears in console:
wine: Unhandled exception 0xe0000008 in thread 1fb at address 00007FB8C7E93023 (thread 01fb), starting debugger... 01fb:err:winediag:FILE_CreateFile Too many open files, ulimit -n probably needs to be increased
And the game stops responding. If anyone wants to see logs I would be happy to provide whatever you want.
https://bugs.winehq.org/show_bug.cgi?id=48225
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #1 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
Please check FAQ entry 10.3.2: https://wiki.winehq.org/FAQ#Too_many_open_files.2C_ulimit_-n_probably_needs_...
What is the output of the command "ulimit -n"?
Regards.
https://bugs.winehq.org/show_bug.cgi?id=48225
--- Comment #2 from Matthew Reed wine@zootal.com --- The default for the version of Slackware I use is 1024. I've been using linux for 15 years or so, and I've never need to change this. Everything I do, including running a 7D2D server, four half-life servers, and four minecraft servers on my game server box, works just fine with this limit.
For the purposes of testing this game, I have increased it all the way up to 65535, and the only difference it makes is that it runs a bit longer before it crashes. Something (the game, a wine lib?) continuously opens files and does not release the handle, and eventually the max is reached, and it crashes.
https://bugs.winehq.org/show_bug.cgi?id=48225
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- (In reply to Matthew Reed from comment #2)
The default for the version of Slackware I use is 1024. I've been using linux for 15 years or so, and I've never need to change this. Everything I do, including running a 7D2D server, four half-life servers, and four minecraft servers on my game server box, works just fine with this limit.
For the purposes of testing this game, I have increased it all the way up to 65535, and the only difference it makes is that it runs a bit longer before it crashes. Something (the game, a wine lib?) continuously opens files and does not release the handle, and eventually the max is reached, and it crashes.
It could be the game, in which case there's not really anything we can do. Windows doesn't have a concept of NOFILE. I've seen programs that leak hundreds of thousands of kernel handles that work fine on Windows.
It could also be Wine. A trace with WINEDEBUG=+file,+ntdll,+server,+pid might help say for sure.
https://bugs.winehq.org/show_bug.cgi?id=48225
--- Comment #4 from Matthew Reed wine@zootal.com --- I know previous versions of windows had file limits, but I stopped using Windows before Windows 8 came out so honestly don't know how the current version of windows handles file handles. Not surprised if they made it unlimited - though all that does is compensate for sloppy programming. I will get you the requested logs, I'll try to get that tonight.
https://bugs.winehq.org/show_bug.cgi?id=48225
--- Comment #5 from Zebediah Figura z.figura12@gmail.com --- (In reply to Matthew Reed from comment #4)
I know previous versions of windows had file limits, but I stopped using Windows before Windows 8 came out so honestly don't know how the current version of windows handles file handles. Not surprised if they made it unlimited - though all that does is compensate for sloppy programming. I will get you the requested logs, I'll try to get that tonight.
To be fair to Windows, they also can kind of afford not to have file limits, because they page out kernel memory. (And they have plenty of reasons not to tell the programmer they're doing it wrong...)
https://bugs.winehq.org/show_bug.cgi?id=48225
--- Comment #6 from Matthew Reed wine@zootal.com --- I have fond memories of increasing file handles in config.sys....that was a long time ago. I'm betting the program itself is eating file handles, and the devs are not aware or just don't care. Anyhow I'll get your logs tonight and see if they show anything of interest. I'll also play with an even higher file limit and see if it maxes out or just keeps increasing.
https://bugs.winehq.org/show_bug.cgi?id=48225
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #7 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-6.4?
https://bugs.winehq.org/show_bug.cgi?id=48225
--- Comment #8 from Matthew Reed wine@zootal.com --- I ran it for a while, and after about 8 minutes or so it stopped responding like it did when it previously threw the file handle error. This was in the console:
wine: Unhandled exception 0xe0000008 in thread 5f8 at address 000000007B037855 (thread 05f8), starting debugger...
Nothing about file handles, but exact same symptoms. I'll play with it a bit and see if I can get more info, but I'm guessing it is still doing the same thing in wine 6.4
https://bugs.winehq.org/show_bug.cgi?id=48225
--- Comment #9 from Matthew Reed wine@zootal.com --- FWIW, I played with this a bit and found other apps that work fine with older versions of wine won't work under wine 6.4. TBH I've had nothing but trouble with wine 6.x. It's possible this problem was fixed but something else is broken. I think I'm going to wait for wine 6.x to mature a bit and then try this again.