Memory Leak

magic hate ball·Sep 26, 2016·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 NamiSep 26, 20161 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 ballSep 26, 20161 votes

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

magic hate ballSep 26, 20161 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.

Deep Terror NamiSep 26, 20161 votes

That's great, I recommend posting on the Help & Support board for assistance.

magic hate ballSep 26, 20161 votes

So once again you're insinuating that the problem is on my side. I have posited a theory as to the cause of my issue, and without a feasible alternative I'm left to think that I am right. I will not be convinced simply by you insisting otherwise. Give me a reason to think that it's on my side. From where I stand you're trying to handle me and I don't appreciate it, especially since from what you've said I believe I have a better handle on the technical aspects of the client than you do.

Deep Terror NamiSep 26, 20161 votes

I said nothing of the sort. I recommended you get advice from the Rioters in H&S. If the issue can be determined to be inherent to the client then they can pass it up to the proper people. If I claimed to know better I wouldn't be passing it off to them, I'd be arguing with you.

magic hate ballSep 26, 20161 votes

But this is where you report bugs, that is where you go to get support with their product. Coming here implies that there is a problem on their end. Going there implies that the problem is on my end. I work pretty closely with a QA team, and this separation of concerns is pretty clear.

magic hate ballSep 26, 20161 votes

Tbh before you replied I was pretty chill about the whole thing, but then you (inadvertently) riled me up. Didn't mean to blow up on you, but if you can't help it's better to not respond.

magic hate ballSep 26, 20161 votes

You know what it is, it's that if riot support came into the thread and you ended with "contact help and support" and I don't reply they might think that the issue is resolved, but it isn't, and in my mind it's on the dev team, not on help and support (for the reasons listed in my other post). It's an issue with the code, not something to be fixed by having me reinstall the client or update my JRE or w/e.

magic hate ballSep 26, 20161 votes

And I know it can be a million things, but the problem has persisted across multiple operating systems, across multiple motherboards, processors, hard drives, graphics cards, sticks of ram, you name it. It is a problem. It is persistent. It is not dependent on one case. It is dependent on a multitude of installations. A multitude of patches. I'm not going to be sated with "go talk to help and support" because I know that they think the problem is on my end and you know that too. That's why you're telling me to go there. Fix the client, or get the new one out there. I'm tired of limbo.