Memory Leak

magic hate ball·9/26/2016, 12:04:26 AM·1 votes·545 views

I am fairly certain that ~10 patches ago a memory leak was introduced into the client that causes it to crash in champ select. If you want I'll give you reasons as to why I feel that it is a memory leak and not something else, but I feel that that is ancillary to this discussion. I am pretty sure I reported this in one way or another when it first started happening, but I'm re-reporting it because my timer for dodging just became 10 minutes instead of 5. I have not once intentionally dodged a game in the past year. Every single time it is the client crashing. Now I know that you can't just give a free pass to people dodging games (and discerning between intentional and unintentional 'crashes' is difficult), but surely you can find some way to fix your client so that its instability doesn't cause 10m cooldowns on top of 6+m queue times.

10 Comments

Deep Terror Nami9/26/2016, 12:07:42 AM1 votes

Memory leaks can happen in any program due to errors in updating, not just something inherent to the version. Try repairing your client.

magic hate ball9/26/2016, 12:13:33 AM1 votes

I have reinstalled the client (and my operating system) multiple times since that patch and it has not changed the issue.

magic hate ball9/26/2016, 12:23:47 AM1 votes

I don't want to go off on you but memory leaks refer to a very particular problem, and for an update to cause it, it would have to introduce an unintended change in code. Either way there is a problem in the code (a bug) that needs to be fixed. An allocation of memory that is not de-allocated. Probably in a process that is repeated without a need for human interaction with the client based on what I have seen. Now that's a very broad problem, but it is affecting me and I would like to not have to wait 10m because I waited 5m so many times that it decided that I've been dodging too much.