Welcome to the Forum Archive!

Years of conversation fill a ton of digital pages, and we've kept all of it accessible to browse or copy over. Whether you're looking for reveal articles for older champions, or the first time that Rammus rolled into an "OK" thread, or anything in between, you can find it here. When you're finished, check out the boards to join in the latest League of Legends discussions.

GO TO BOARDS


Another instance of the client is running..

1
Comment below rating threshold, click here to show it.

Tupples

Senior Member

04-13-2013

every time I close the client with CMD+Q, which is kind of a reflex, I get this message 10x before I can open it. Pretty annoying. Right now I can't open it at all.


Comment below rating threshold, click here to show it.

RSisCOOL

Junior Member

04-13-2013

open up task manager and try quit any LoL related processes, maybe UserKernel or LoLClient LoL launcher basically anything LoL related then try reboot.


Comment below rating threshold, click here to show it.

Sentarinku

Junior Member

04-18-2013

Quote:
TaskForceWolf:
every time I close the client with CMD+Q, which is kind of a reflex, I get this message 10x before I can open it. Pretty annoying. Right now I can't open it at all.


Same issue, but I have narrowed it down slightly. Something is getting left in memory without being unrefenced. What, I don't know yet.

I use a tool called "Memory Clean" (free, AppStore), it fixes up dead references in your RAM to give you the most of your memory. If I use it after closing the LolClient, then I never have this problem.

This also leads me to think that the client checks it's memory footprint to see if it still running, and not running processes (ps ax|grep LoLClient; for example). I'd be interested to know, as I've compared processes when the client is running and when it is not.


1