http://bugs.winehq.org/show_bug.cgi?id=21636
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID Summary|MJ12node.exe freezes after |MJ12node.exe freezes after |a while |a while (Linux kernel | |signal delivery bug, | |reported fixed 2.6.34-rc7+)
--- Comment #14 from Anastasius Focht focht@gmx.net 2010-08-18 11:41:44 --- Hello,
revisiting.
--- quote --- Using kernel 2.6.34-rc7 and latest Wine from git the node no longer freezes after a while, it just stops doing anything instead. Menus can be accessed, the window can be moved etc, but otherwise it's dead.
Maybe it has something to do with too many concurrent connections? I've set the node so that it can use 300 concurrent connections and 50mbit bandwidth when crawling. I should probably test it with lighter settings too..
One thing that I noticed from the node's own "console": it said an error about having too many open files or something like that. I've never seen it on Windows so it's most probably caused by Wine. --- quote ---
Well even if the original problem reported was not a dupe of bug 20380 it was a similar related kernel bug (signal delivery), which seems to be fixed in recent Linux kernel versions - based on your last comment.
Regarding the "too many open files" messages: it's outside the scope of wine if the app keeps that much files open. It could also be an app bug (file handle leak). You could try to temporarily raise that limit using:
--- snip --- $ su # ulimit -n 4096 # su <your_username> $ wine foo.exe --- snip ---
You can check the current limits:
--- snip --- $ ulimit -aH --- snip ---
Regards