[PvP.Net] Consistent repro steps for crashing the client.

Mârty·3/1/2015, 2:28:13 AM·2 votes·872 views
  1. Log into PvP.net.

  2. Have a moderately high (at least 50) number of online friends.

  3. Minimize the client/afk/play a game.

  4. Scroll through your friends list at a moderate pace while hovering over your friends. Eventually, it'll crash your client.

I've managed to crash my client this way multiple times, repairing my client did not fix the issue. I can make a video if required.

3 Comments

Zxkuqyb3/1/2015, 4:50:40 AM2 votes

I explained this MULTIPLE times but EVERYONE ignores EVERYTHING I say--UNTIL it happens to them. IT'S A MEMORY LEAK The memory leak is because of that new "server side update" (it was in the 5.4 patch but wasn't activated right away) from two nights ago The server side update allows you to see your friend list champion data and server time data in real time (even for offline players). and it EATS up memory constantly. Once the client reaches maximum 32 bit allocation size (2.1 GB commit size, usually this is about 1.6 GB of physical memory), it crashes, because a 32 bit program can not use more than 2,147,483,647 bytes of memory. If League were a 64 bit program, this memory leak would just keep growing and even eat up the memory on 64 GB power computers.

There is NO solution to this. I don't know if it happens in windows 8.1 or windows 10, but it happens on windows 7/x64. I tried using a process viewer and it's impossible to tell which "module" that lolclient.exe is using, that is causing the leak. This isn't the first time an adobe air client has had leaks like this, though.

I guess Riot simply doesn't test these things.

Zxkuqyb3/1/2015, 6:58:49 PM1 votes

You can work around the bug SLIGHTLY, by turning off "show offline friends" You still get the memory leak but it progresses MUCH slower than before (but using mouse over friends accelerates the memory leak by a factor of 100).