https://bugs.winehq.org/show_bug.cgi?id=45939 --- Comment #2 from showard314(a)gmail.com --- I got to attach winedbg to the running process and wait for the program to hit the file descriptor limit and crash. However, winedbg only gave the following info upon crash: 00f8:err:winedbg:dbg_handle_debug_event Unknown thread 00f8:err:winedbg:dbg_handle_debug_event Unknown thread 00f8:err:winedbg:dbg_handle_debug_event Unknown thread 00f8:err:winedbg:dbg_handle_debug_event Unknown thread 00f8:err:winedbg:dbg_handle_debug_event Unknown thread 00f8:err:winedbg:dbg_handle_debug_event Unknown thread 00f8:err:winedbg:dbg_handle_debug_event Unknown thread I found a bug with similar symptoms: https://bugs.winehq.org/show_bug.cgi?id=23999 like this bug, software crashes after some time after spawning lots of processes because of DRM checks. I think what we might be seeing here is there are anti-cheating checks running in the windows binary that is periodically generating anonymous memory map files to look for hack/cheating code. For some reason these map file descriptors are remaining open long after the file was deleted. Eventually the ulimit is hit and everything locks up/freezes/corrupts because game resources cannot be opened. -- 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.