Launcher STILL has problems

[{ZW}C-LOKE]

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!

[Megagoth1702]

Workaround - put priority on LOW. Helps the game get more CPU.

[maximi4444]

Thats cute but I cant set it LOW....it says:

Operation was not finished. Access was denied. (freely trasnlated from Slovak)


So I cant....there should be a patch or smth...and I found out that after patch this happened only when I restarted mumble because of crash...It just crashed and I couldnt hear anyone..so I closed it and restarted it..and this shit started to happen.

It is connected to it somehow...gotta just find out how.

Please fix THIS first...the CPU..anything else can wait..thanks

Cheers,
sn4ke4444

[Spiller]

Operation was not finished. Access was denied. (freely trasnlated from Slovak)

To fix That Go to :
Start --->Type : tskmgr(in Search at the bottom of the Start menu in Win7)
Right Click on tskmgr and Run as Admin then you should be able to Access Set Affinity and Set Priority in the Right Click Menu.

[{ZW}C-LOKE]

To fix That Go to :
Start --->Type : tskmgr(in Search at the bottom of the Start menu in Win7)
Right Click on tskmgr and Run as Admin then you should be able to Access Set Affinity and Set Priority in the Right Click Menu.

That's great and everything, and I agree. Yes, setting the affinity (and priority) of a process such as this will achieve the desired results, but doing this is more of a treatment to the symptoms, not a cure for the disease. The underlying problem in launcher.exe is still there even after subduing it with this "duct tape" type fix.

This is also not to mention that affinity is inherited by child processes, which means, starting launcher.exe with priority (and or affinity) spawns PR.exe and Mumble.exe with the same (at least) affinity settings. Not sure about priority, but there are for sure times when PR.exe (or bf2.exe) utilize pipelining across multiple threads, at which point an affinity setting inherited to PR.exe that dictates only utilizing one thread instead of all available (at the few select moments in runtime where it so chooses to) is not beneficial in the least.

You can't close out Launcher.exe without it closing PR.exe and Mumble.exe because those two processes become children processes of the parent process that launched them, Launcher.exe.

It's very frustrating to see this symptom remedy rumor floating around the forum, especially having a better understanding of how processing occurs, especially on multi-core, hyperthreading, and Core i3,i5,i7 MC + HT processors, and knowing that the underlying disease is still there.

[AncientMan]

PRLauncher handles the communication between PRBF2 and PRMumble. Without PRLauncher running, everything would break. So no, you can't do something like quit PRLauncher and launch PRMumble manually, your game would be completely screwed, and I'm sure you don't want that .

[{ZW}C-LOKE]

Yeah, and you can see that parent/child relationship between launcher and PR.exe/Mumble.exe with Process Explorer; the best task manager replacement known to man.

Process Explorer

If only there was a way to detach PR.exe after launch...