Launcher STILL has problems
Posted: 2013-08-03 15:15
The launcher still maxxes out cpu usage. Even after patch, this occurs anywhere from 10-15 mins to a couple hours of playing. No fail every time, it's something I can basically count on. It's noticeably linked to mumble stopping. As soon as everyone's mumble goes bonkers, that's when Loader.exe goes apeshit. The patch that was applied did solve the problem partially, but I'm telling you that it's still not fixed. This is not an isolated event, I've had several people confirm this.
And I love the idea of having the launcher handle loading PR + Mumble, don't get me wrong. But having Launcher.exe launch both these two and still keep them as a child process without detaching them essentially means that when Loader.exe goes apeshit, the only way to remedy the problem is to close out the entire game, because you can't just kill Launcher.exe without affecting both of the important child processes; PR.exe and Mumble.exe. You should have Launcher.exe at LEAST detach PR.exe back into it's own parent process, so when this happens, we can at least just close out Launcher.exe and restart mumble while not having to leave the game.
How do I know these are child processes? In fact, how do I know all these wonderful things that the default Task Manager doesn't tell you? I use a task manager called Process Explorer. It's a tool built by Microsoft for system admins. It's quite informative, and it is what should be the default task manager of Windows for anyone serious about informational awareness of their system. You can grab it from Process Explorer
Also, don't know if this info helps or not, but even during regular play, both my physical memory and system commit (physical memory and pagefile disk space set aside by the system for processes in memory that the system guarantees those processes is available for their operations) are maxxed out, 100%. I have four gigs ram and my pagefile is set to the same. These memory leaks (or overhead, if that was intended) are not linked to the mumble crash/Loader.exe issue, from what I'm able to tell.
But I tell you what, this is driving me so nutts I'm getting ready to attach a debugger to loader.exe and debug the goddamn thing myself!
And I love the idea of having the launcher handle loading PR + Mumble, don't get me wrong. But having Launcher.exe launch both these two and still keep them as a child process without detaching them essentially means that when Loader.exe goes apeshit, the only way to remedy the problem is to close out the entire game, because you can't just kill Launcher.exe without affecting both of the important child processes; PR.exe and Mumble.exe. You should have Launcher.exe at LEAST detach PR.exe back into it's own parent process, so when this happens, we can at least just close out Launcher.exe and restart mumble while not having to leave the game.
How do I know these are child processes? In fact, how do I know all these wonderful things that the default Task Manager doesn't tell you? I use a task manager called Process Explorer. It's a tool built by Microsoft for system admins. It's quite informative, and it is what should be the default task manager of Windows for anyone serious about informational awareness of their system. You can grab it from Process Explorer
Also, don't know if this info helps or not, but even during regular play, both my physical memory and system commit (physical memory and pagefile disk space set aside by the system for processes in memory that the system guarantees those processes is available for their operations) are maxxed out, 100%. I have four gigs ram and my pagefile is set to the same. These memory leaks (or overhead, if that was intended) are not linked to the mumble crash/Loader.exe issue, from what I'm able to tell.
But I tell you what, this is driving me so nutts I'm getting ready to attach a debugger to loader.exe and debug the goddamn thing myself!
