Memory leak since the new patch

Risingson - Lost City

Hello,

For a few days now, I've been getting crashes on pwi. I checked the memory usage of pwi and it goes through the roof (above 3gb...).


http://oi42.tinypic.com/2eaqmjb.jpg



What is that?

I have a Medion ERAZER X7817

Windows 7 Home Premium 64-bit SP1

Inter Core i7-2670QM@2.20GHz, 8GB RAM Intel Graphics 3000/GeFroce GTX 670M



I need help over here. I scanned my computer with every antivirus known to man and nothing's up.

Sizzer - Raging Tide

The memory Leak issue has been fixed. Idk what's going on at your end but PWI seems better with the last content update. The devs made the game more stable for old machines so it's naturally game will give a good performance in newer P.C.

Try to run "Verify" back to 3 times. IF the problem still persist then contact Tech Support.

Azura - Lost City

Look for a program called minimem and configure it to clear pw's memory often.

SylenThunder - Twilight Temple

3GB is completely unnatural though. The client doesn't support exceeding the 2GB cap imposed on legacy 32-bit applications. On top of that, the latest update to the client makes it handle memory better and I haven't seen it exceed 1GB, even in extreme situations.

This is an indicator that something else is wrong on the OP's system, or with the client.

Chrisssss - Sanctuary

SylenThunder - Sanctuary wrote: »

3GB is completely unnatural though. The client doesn't support exceeding the 2GB cap imposed on legacy 32-bit applications. On top of that, the latest update to the client makes it handle memory better and I haven't seen it exceed 1GB, even in extreme situations.

This is an indicator that something else is wrong on the OP's system, or with the client.

Ah didn't know that, well glade to hear pwi acknowledges this issue. Had the same issue last yr but my problem was more of how I had my computer hooked to my tv although it was doing a memory leak. Ever since this update though I've been bugging more and crashing than I used to but it didn't seem like it was a memory leak. Does arch cause lag and crashes or could it?

Risingson - Lost City

It only seems to happen with PWI. It happened the other day and I reinstalled PWI, and still the same.

I'm running a verification right now, but as I said I scanned my computer with MBAM, ESET, AVG, SuperAntiSpyware and even a couple of rootkit scanners, and absolutely nothing.

I don't quite see what else could be wrong aside from the client.

Sizzer - Raging Tide

Holey Moley soo many anti-viruses. b:shocked

Risingson - Lost City

Yeah. I wanted to make sure there were no viruses whatsoever.

What else could be slowing down my laptop?

Sizzer - Raging Tide

Risingson - Lost City wrote: »

What else could be slowing down my laptop?

Your anti-viruses, also make sure your game files are added in your anti-viruses exception list or else running the game will be trouble for you. b:surrender

Risingson - Lost City

I think I may have fixed it. I updated my Intel Graphics 3000 drivers and my nVidia platform. It seems to run a lot better.

We'll see though, if it happens again I'll do what you just suggested.

Chrisssss - Sanctuary

Sorry for bringing this up but I'm at a loss. Alright thought I had the same issue too memory leak but considering you guys said pwi fixed it and I don't think it's memory leak.

My issue is my client crashes it seems like about every 1 hr or 2 or in extreme graphics it'll do white blocks on me or if I tele from a city to city or mori after a hr or 2 it'll do the white blocks on me again.

I have done the following:

Verified
check for driver updates
ran anti virus scans
lowered graphics

Still the issue is there, this started honestly after the major update. Before my memory in task manager was about 400K in arch now it seems like 800K to a 1G seems to be the cap. Reading this it sounds like 2G is the cap which should leave me with a lot of space.

Had this issue last yr but it ended up just having to get a DVI to HDMI cable to fix the problem.

Sizzer - Raging Tide

Please post a copy of your dxdiag.txt & Speccy report while you are crashing.

bluestuffzzz

Sizzer - Raging Tide wrote: »

Please post a copy of your dxdiag.txt & Speccy report while you are crashing.

For this specific problem, he doesn't need to post any information besides the mere fact that he crashes when he teleports, etc, etc. It's a memory leak that causes the client to reach extreme amounts of RAM usage. I understand that he stated it doesn't show up beyond 1GB of RAM being used, but it still crashes - this is most likely due to not watching the task manager at the time of the crash. Teleporting for example, forces the client to check the new area for players at the same time as loading the graphical scenery.

The only method around the crashing is to manually implement a quick patch/fix by visiting various websites offering to uncap the 2GB (1.8GB technically) of RAM limitation, and re-cap it to 4GB (this is for 32-bit executables). Unfortunately, Wanmei has decided that they will not be fixing this issue. It's a known issue since 2009, and PWE staff have often blamed the players, stating it is their machine. PWE has also stated that uncapping the elementclient.exe from 2GB to 4GB is technically bannable and can result in punishment (lol). It's bannable to post a link to the fix or a website even directing a user to a fix. Silly stuff.

Chrisssss - Sanctuary

bluestuffzzz wrote: »

For this specific problem, he doesn't need to post any information besides the mere fact that he crashes when he teleports, etc, etc. It's a memory leak that causes the client to reach extreme amounts of RAM usage. I understand that he stated it doesn't show up beyond 1GB of RAM being used, but it still crashes - this is most likely due to not watching the task manager at the time of the crash. Teleporting for example, forces the client to check the new area for players at the same time as loading the graphical scenery.

The only method around the crashing is to manually implement a quick patch/fix by visiting various websites offering to uncap the 2GB (1.8GB technically) of RAM limitation, and re-cap it to 4GB (this is for 32-bit executables). Unfortunately, Wanmei has decided that they will not be fixing this issue. It's a known issue since 2009, and PWE staff have often blamed the players, stating it is their machine. PWE has also stated that uncapping the elementclient.exe from 2GB to 4GB is technically bannable and can result in punishment (lol). It's bannable to post a link to the fix or a website even directing a user to a fix. Silly stuff.

AH thank you one other question, last year I'd had purchased a new PC but just used a HDMI cord because after a month memory leak occurred than I purchased the DVI to HDMI cord which seemed to have fixed the problem but after awhile that port seemed to have failed (I have two ports) than used the other and worked just fine until now. So assuming with the new graphics of this content it just over does it on my video card? Considering that do you think this has harmed video card?

Sizzer - Raging Tide

The cap isn't 2 GB it is 1.5 GB(me thinks) then the client is bound to crash. That is actually within normal operating parameters. Some parts of the game have to render an INSANE number of characters, buildings, visual effects and more.
PWI likes to use the CPU quite a lot. You can try updating your mainboard and CPU drivers, and see if that helps any with the memory management issues.

At your own risk, you may have to disable your antivirus, firewall, and other security software temporarily while you download, install, update, login to, and play the game. Sometimes the security software will block it or throttle it, no matter what you try or even if you try to add exceptions for the game files in your security software.

SylenThunder - Twilight Temple

bluestuffzzz wrote: »

For this specific problem, he doesn't need to post any information besides the mere fact that he crashes when he teleports, etc, etc. It's a memory leak that causes the client to reach extreme amounts of RAM usage. I understand that he stated it doesn't show up beyond 1GB of RAM being used, but it still crashes - this is most likely due to not watching the task manager at the time of the crash. Teleporting for example, forces the client to check the new area for players at the same time as loading the graphical scenery.

The only method around the crashing is to manually implement a quick patch/fix by visiting various websites offering to uncap the 2GB (1.8GB technically) of RAM limitation, and re-cap it to 4GB (this is for 32-bit executables). Unfortunately, Wanmei has decided that they will not be fixing this issue. It's a known issue since 2009, and PWE staff have often blamed the players, stating it is their machine. PWE has also stated that uncapping the elementclient.exe from 2GB to 4GB is technically bannable and can result in punishment (lol). It's bannable to post a link to the fix or a website even directing a user to a fix. Silly stuff.

Actually, if it's just crashing during the teleports and nothing else, simply reducing the draw distance a notch or two will fix that.

As for the rest, yes, kinda need the Speccy report, and/or a dxdiag output. I can then analyze the system, give tips to free up the CPU, offer advise on software that is or isn't needed, and identify conflicts that are causing the client to crash. Can't do that without detailed information.

I'll cover the details on the RAM later...

Chrisssss - Sanctuary wrote: »

AH thank you one other question, last year I'd had purchased a new PC but just used a HDMI cord because after a month memory leak occurred than I purchased the DVI to HDMI cord which seemed to have fixed the problem but after awhile that port seemed to have failed (I have two ports) than used the other and worked just fine until now. So assuming with the new graphics of this content it just over does it on my video card? Considering that do you think this has harmed video card?

The client barely uses your GPU, it's more likely a CPU bottleneck is causing you the troubles. With a Speccy profile I can help narrow down the cause for that.

Sizzer - Raging Tide wrote: »

The cap isn't 2 GB it is 1.5 GB(me thinks) then the client is bound to crash. That is actually within normal operating parameters. Some parts of the game have to render an INSANE number of characters, buildings, visual effects and more.
PWI likes to use the CPU quite a lot. You can try updating your mainboard and CPU drivers, and see if that helps any with the memory management issues.

At your own risk, you may have to disable your antivirus, firewall, and other security software temporarily while you download, install, update, login to, and play the game. Sometimes the security software will block it or throttle it, no matter what you try or even if you try to add exceptions for the game files in your security software.

Technically, the cap is 2GB, but it's actually rendered just over 1.8GB blue was correct in that using the 4GB patch to allow the client to exceed the boundary is against ToS. Minimem is nice for systems that don't have the RAM to spare, but it can also have a negative side effect in some cases if you're using high details.

The latest update/expansion/whatever you want to call it, has improved performance on lower-end systems by basically doing the same thing Minimem does. It's forcing garbage collection on the memory usage of the client to keep it below 1GB. On most systems this isn't a problem. If you're using an extremely high resolution with full-on details, it can cause a problem sometimes.
I am currently working on troubleshooting this issue and will have more details on a solution later. Currently, the fix is to reduce your settings in some way. Lower resolution for the client, turn off things like shadows, reduce the draw distance or effects are all valid temp fixes.
On the other hand, this problem can also be caused by other programs using the CPU, which causes client's processes to be delayed slightly, it doesn't get the textures it needs loaded when it thinks they need to be loaded and subsequently crashes. This can be cause by security software, scheduled updates, bloatware from your PC maker, or even something as simple as a video codec.

In any case, if you would like for someone to help you troubleshoot the issue, we will need, at an absolute minimum, we will need a copy of the output from a dxdiag.txt file, and a link to a published Speccy report taken while you are having the issues.
(Remember to use the [code] tags for the dxdiag info and to remove any trademark characters so it doesn't get cut off.) (CODE tag is the # symbol in the editor.)

Chrisssss - Sanctuary

http://pwi-forum.perfectworld.com/showthread.php?t=1384801

That was from last years post. The specs should be under the specs tab