.
It's a game issue. Been going on since CH 5 release.
I get it on my machine when client.exe surpasses using about 1.25 gig of ram. ie pretty much anytime I port somewhere and am just standing around.
I have 8 gig and am no where near using it all.
BTW, reinstalling with the new client download resolved the wather issues but did nothing for the memory issues nor the new crashing issues.
.
.
This issue is not total resources being used, it is a given instance of ROM exceeding 1.3 gig in ram.
Some data for you:
PC runs at 27% of 8gig being used before ROM opened.
Situation 1:
Instance 1 - 1.21 gig used by client toon in Dalanis Snoop.
Ported around till I got error message, client.exe at 1.33gig. Ram usage 41%.
Situation 2:
4 instances of ROM running. PC at 80% RAM used.
Instance 1 - 1.14 gig used by client toon in FLAC (new zone)
Instance 2 - 1.13 gig used by client toon in Varanas East
Instance 3 - 1.05 gig used by client toon in Varanas East
Instance 4 - 1.00 gig used by client toon in Varanas East
No memory error till I port around and get the 1st instance to exceed 1.3 gig.
Once I click "Ok" I haven't been able to get the message to come up again until the client has been closed and reopened.
Clearly it's not an overall resource issue.
.
There is an add-on, MemoryWarningMuffler, from curse that can make it so the message pops up in a subtle slate gray in gen chat tab instead of a pop-up. ipeacefrog is correct, the message only comes up when Runes exceeds 1 gig+ use of RAM. It doesn't matter HOW much RAM you have, what version of Windows you're running, or any of that. So just know it is NOT your computer, it's Runes of Magic. They added this message with the patch, probably not realizing quite how often their game reaches such levels. lol
Thanks a lot guys lol, I was thinking that it couldn't be my computer because there is no way, I have never come even close to using 7gigs of ram at any one time.
ipeacefrog thanks for the reasurch and such, I ran a few experiments, and my pc has the same results.
The message itself is not so bothersome as the fact that I
KNOW a
CRASH is close to follow