Can anybody get in FM like they used to?

The only way i can actually visit stores in FM now is through channel hopping inside rooms.

The moment i step outside, there are so many people all spamming their messages that Maple implodes and i have to close it through task manager


Does it mess up for anyone else? Or maybe i just have bad connection idk..

Lolweakcomputer.

This should go in tech section, along with specs of your computer.

This happens on my PC.. but on my laptop its fine.

Nexon made a boo-boo when handling graphic memory. The client is allocating memory for each image that appears on your screen (in other words, caching the images), but it's not releasing all of the memory when it's done using them. This creates a runaway effect that eventually leads to a crash. Of course, if you have a more powerful computer, you'll see less crashes because you have more memory to allocate.

You'll notice if you sit in the FM with your Task Manager open, the memory that the client uses will continue to go up until you change maps or change channels. And even then, it doesn't go back to normal levels so crashing is imminent.

it's not releasing all of the memory when it's done using them

That's like the first thing you get in the habit of NOT doing when you start learning to program...

My computer more or less freezes if I try to go in FM entrance in chan 1. So yeah, channel hop.
Been that way since a few weeks before BB, probably since that patch that was supposed to fix combatibily problems.

I suspect this is fairly common, since I see a lot of characters materializing in FMs rather that coming in through the portal.

Nexon made a boo-boo when handling graphic memory. The client is allocating memory for each image that appears on your screen (in other words, caching the images), but it's not releasing all of the memory when it's done using them. This creates a runaway effect that eventually leads to a crash. Of course, if you have a more powerful computer, you'll see less crashes because you have more memory to allocate.

You'll notice if you sit in the FM with your Task Manager open, the memory that the client uses will continue to go up until you change maps or change channels. And even then, it doesn't go back to normal levels so crashing is imminent.

Yeah, I'm also going to note this is probably similar to the problem that caused the win7 crashes at bosses though I'm not sure if that was limited to 64-bit machines or what.

Nexon made a boo-boo when handling graphic memory. The client is allocating memory for each image that appears on your screen (in other words, caching the images), but it's not releasing all of the memory when it's done using them. This creates a runaway effect that eventually leads to a crash. Of course, if you have a more powerful computer, you'll see less crashes because you have more memory to allocate.

You'll notice if you sit in the FM with your Task Manager open, the memory that the client uses will continue to go up until you change maps or change channels. And even then, it doesn't go back to normal levels so crashing is imminent.

How annoying :/ Guess i wont be going to FM anytime soon unless they fix it.

I have 1GB of video RAM and it still causes a major lag spike on my system as well.

my ATI 5870 HD asks "what problem, good sir?"

sounds like you don't have enough processing power, RAM, or graphics card power to take all of that. I'm doing fine on my e6400 @ 3.0 with a 6870.

sounds like you don't have enough processing power, RAM, or graphics card power to take all of that. I'm doing fine on my e6400 @ 3.0 with a 6870.

Im not sure about Processing Power or my Graphics Card, but i picked this laptop because it had 3GB of RAM.

There's definitely something up with the client.

 Spoiler

I've never seen it use up that much memory before.

Nexon made a boo-boo when handling graphic memory. The client is allocating memory for each image that appears on your screen (in other words, caching the images), but it's not releasing all of the memory when it's done using them. This creates a runaway effect that eventually leads to a crash. Of course, if you have a more powerful computer, you'll see less crashes because you have more memory to allocate.

You'll notice if you sit in the FM with your Task Manager open, the memory that the client uses will continue to go up until you change maps or change channels. And even then, it doesn't go back to normal levels so crashing is imminent.

So that's why even on KMS, which should have a "compatible" client with Windows Vista/7 (since their website says Windows XP and later in the game requirements page of the website), after standing for a long time in the Free Market Entrance, the client ALWAYS crashed!

Same goes for standing in Free Market rooms for a long time with an opened store on Windows 7. While I can strangely do it on Windows XP, it always crashes after a while on Windows 7 64 bit.

Could it be that the client has problems with the memory on Windows 7 more than on Windows XP? :f6:

Try looking into a neat little program called FreeRAM. I rarely have to use it, and when it does activate, it is usually able to free up a good 20-35% of my memory when I need it. You shouldn't have it set to auto-free your RAM though, as it tends to dip down performance while it does. It clears the image cache for me. The main issue is that if it frees too much (usually when I leave Maplestory inactive for a while), it will have to reload the graphics as you encounter them which causes instant "lag spikes" as it loads the images again. This is common when attacking for the first time in a few hours. Otherwise, it's very handy and I've never crashed once because of the memory building up too much.

NOTE: Experiences may vary depending on PC specs. Again, you should disable any auto-free effects as areas with a lot of images (bosses) will build up and trigger it causing instantaneous framerate drops. Side-effects may include: death and a loss of EXP.

Nexon made a boo-boo when handling graphic memory. The client is allocating memory for each image that appears on your screen (in other words, caching the images), but it's not releasing all of the memory when it's done using them. This creates a runaway effect that eventually leads to a crash. Of course, if you have a more powerful computer, you'll see less crashes because you have more memory to allocate.

You'll notice if you sit in the FM with your Task Manager open, the memory that the client uses will continue to go up until you change maps or change channels. And even then, it doesn't go back to normal levels so crashing is imminent.

What did they do, hire a bunch of High Schoolers in Beginner's Programming for this game? As Takebacker said, that's like the first thing you learn NOT to do in programming. *sigh*...Nexon...

I've noticed channel 1 FM being alot laggier since big bang. Not to complain though because I do not play anymore

There's definitely something up with the client.

 Spoiler

I've never seen it use up that much memory before.

That's way too much, even for the various 3D games I've played, the max I get was only 500mb. I'm on x64 bit computer btw, that's even more memory than x32.

There's definitely something up with the client.

 Spoiler

I've never seen it use up that much memory before.

wtp? even when i play starcraft2 for like 4-5 hours, starcraft wont use that much of memory :f6:

But i noticed something, if i stay on a map with too many people (leafre ch1, henesys ch1, fme) or on a map with people killing monster for too long, my client tend to start glitching, windows (buddy, guild, alliance, inv, etc) will become invisible, all chat ballons wont appear, sometimes lowering the quality fix it, sometimes the client just crash.

There's definitely something up with the client.

 Spoiler

I've never seen it use up that much memory before.

It only goes up that high when you go to bosses that you can summon. However when it does it usually means I'm going to crash soon (because the pixels start bugging out on me) or when I attempt to click npc and exit its going to crash when trying to get out.