Re-produceable per-process Memory-leak in POL.EXE

[Alhanelem]

Let me preface this by noting, none of the content of this post is a suggestion the issue shouldn't be addressed. It absolutely should. I'm just discussing why I don't think this is going to be a priority. Because discussing things is what I do. Devil's advocate maybe, but I actually find this stuff interesting.

1.) The program POL.EXE is a 32-bit application capable of addressing (2-4GB of memory only). It is simply incapable of utilizing more RAM than this. All memory requests for POL.exe occur within this 2-4GB of virtual address space.

Firstly, you only used half of the possible 4GB, so I wouldn't say its close to a big deal yet.
Secondly, This is easily fixable- By the end user by simply running a patcher to make the EXE Large Address Aware, which can also fix a different crash caused by changing areas rapidly via home point warp; and by SE by simply setting the flag that patching the EXE does.

2.) As time goes on, a process requests more memory on the heap (RAM)

You established that the game only leaks memory when you perform a specific action- And that action is only realistically going to be performed a maximum of 16 times or so by someone who is actually going through the trouble of doing daily stuff on every single character, which isn't something everybody does. I think you overestimate the number of people who actually max out their accounts like this- In fact I think more people have multiple accounts with one character on them than have one account with the maximum characters.

3.) To be specific, the memory leak occurs for ANY amount of logout and logins. Every time you logout and login you are losing memory. It doesn't matter if it's 1 character, 16 characters or any number in between.

Same as point above, I don't think ordinary players usually log in and out enough times to make this a big problem.

The fact that you discovered it means it could happen, but I don't think it's much cause for worry. And someone with enough knowledge can actually fix it themselves whether or not SE bothers to.

(Note, the patcher I refer to can be used on any such 32-bit application to allow it to address more memory; I'm not going to link it for obvious reasons, but this has become a problem with a number of older applications, so thats why it exists). Technically, just allowing the game to use more memory doesn't truly fix the problem, but it makes it immensely less likely to have any impact.