please, PLEASE fix the memory leak

[Mowster]

<p>Although I know that the response will be "Upgrade your computer its not the game"....</p><p>Fact...I had no issues playing until the freeport revamp. Xpac=sudden major memory crashes.</p><p>Fact...I uninstalled and reinstalled the game.</p><p>Fact...after said reinstall memory issue was gone. No issue loading even into large gh even on balanced settings.</p><p>Fact...physical memory usage after reinstall once again showed around 60%</p><p>Fact...thursday they did an update.</p><p>Fact...after the update, again with the crashing and running out of memory.</p><p>Fact...now my memory usage is, once again, hitting 100% then crashing.</p><p>Fact...I am NOT the only player experiencing this problem and it has gotten worse since the Xpac.</p><p>Fact...I could double my memory to 8 gigs and I am sure that I would still crash from low memory.</p><p>Fact...this is the ONLY game that I cannot play now much of the time because of crashes, yet it is the only game that I pay to play<---gee am i the only one who thinks there is something seriously wrong with that picture.</p><p>Fact...this game has a known issue with memory leakage.</p><p>Fact...I pay $15 for 30 days of this game, yet cannot play all 30 days because of game issues and crashes.</p><p>Conclusion...it's not my computer, it's the game.</p><p>Suggestion...hey Sony, instead of charging us $15 for 30 days regardless of our ability to play, how about only racking up the charge for the days we actually can log in and play. If I have paid for 30 days(a month)but only have logged on for say 15 of those, don't charge account again until 30 days of actual play time has been logged. Because I bet the impact of players not logging on and getting charged because they are unable to actually log in and play the game would encourage the devs to fix the problem post haste.</p><p>Fact...memory leaks, game crashes, lagging, and station launcher snafus would hasitly become a thing of the past.</p>

[Elomort]

<p>Try closing the new launcher.</p>

[Wurm]

<p><cite>Elomort wrote:</cite></p><blockquote><p>Try closing the new launcher.</p></blockquote><p>And how is that going to help an in game problem?</p>

[The_Cheeseman]

<p>I have the same problem. It really only seems to affect me in the T3 Commonlands guild hall. If I try to zone-in there my client will crash, sometimes popping-up 3-6 critical out-of-memory errors at the same time. I can only avoid this fate by reducing my graphics settings to "ASCII Mode", meaning every single option at absolute minimum. I never had any trouble at all before AoD launch, but now I feel like an exile from my guild hall, and it's really aggravating me. This needs to be fixed ASAP.</p>

[Wurm]

<p><cite>The_Cheeseman wrote:</cite></p><blockquote><p>I have the same problem. It really only seems to affect me in the T3 Commonlands guild hall. If I try to zone-in there my client will crash, sometimes popping-up 3-6 critical out-of-memory errors at the same time. I can only avoid this fate by reducing my graphics settings to "ASCII Mode", meaning every single option at absolute minimum. I never had any trouble at all before AoD launch, but now I feel like an exile from my guild hall, and it's really aggravating me. This needs to be fixed ASAP.</p></blockquote><p>A friend of mine had the same problem and I talked him into how to make his page-file bigger and it fixed the crashing. It still takes him 5 mins to zone into the guildhall... but he ends up inside.</p><p>It seems that the game is ignoring how much ram you have and putting a bunch of stuff into the pagefile when loading houses or guildhalls.</p>

[Mayerling]

<p>24gigs ram... Intel I7-950... Windows 7 pro... Velociraptor and SSD drive... AMD 6850 1Gig GDDR5 Vmem... MemLeak... not my computer.</p>

[Avirodar]

<p><cite>Mayerling wrote:</cite></p><blockquote><p>24gigs ram... Intel I7-950... Windows 7 pro... Velociraptor and SSD drive... AMD 6850 1Gig GDDR5 Vmem... MemLeak... not my computer.</p></blockquote><p>I am in a very similar boat to you, system wise.I can run around on Freeport with 2 characters, using the extreme quality graphics settings. While I do not crash, observing my systems memory usage makes it clear why client crashes (due to memory) have been a problem for some users since AoD was launched.SOE used to have the memory leak on somewhat of a leash. Not anymore.</p>

[Gaealiege]

<p>Yeah, there is definitely a memory leak in game.  ESPECIALLY observed in Freeport.  I'm running with 12 Gig of RAM and my client will crash letting me know I don't have enough memory to allocate....yeah right.  I run the top PC games in existence in their highest settings well over 60 FPS and never, after hours of gameplay, have I seen a memory issue. (Skyrim, Crysis 2, etc.)</p><p>The last time SOE had a memory leak they told the players for months "nuh uh!"</p><p>Then after a few months they said "Well ...yeah you were right" and fixed it.  I expect them to do the same thing again here.  You'll see reps responding with the usual soft-headed, imbecilic replies like "Have you updated your drivers?"</p>

[The_Cheeseman]

<p><cite>Wurm wrote:</cite></p><blockquote><p>A friend of mine had the same problem and I talked him into how to make his page-file bigger and it fixed the crashing. It still takes him 5 mins to zone into the guildhall... but he ends up inside.</p><p>It seems that the game is ignoring how much ram you have and putting a bunch of stuff into the pagefile when loading houses or guildhalls.</p></blockquote><p>I assure you, I know all about virtual memory allocation and this is not the problem. I have even set the 3GB switch recommended in the support forums, and while it did help loading times in general, it did not stop this issue. This is not a PC problem, it's a game client problem.</p>

[Wurm]

<p><cite>The_Cheeseman wrote:</cite></p><blockquote><p><cite>Wurm wrote:</cite></p><blockquote><p>A friend of mine had the same problem and I talked him into how to make his page-file bigger and it fixed the crashing. It still takes him 5 mins to zone into the guildhall... but he ends up inside.</p><p>It seems that the game is ignoring how much ram you have and putting a bunch of stuff into the pagefile when loading houses or guildhalls.</p></blockquote><p>I assure you, I know all about virtual memory allocation and this is not the problem. I have even set the 3GB switch recommended in the support forums, and while it did help loading times in general, it did not stop this issue. This is not a PC problem, it's a game client problem.</p></blockquote><p>I agree that its the game. I was just letting you know that my friend making his page file larger worked for him.</p>

[Jrral]

<p><cite>The_Cheeseman wrote:</cite></p><blockquote><p>This is not a PC problem, it's a game client problem.</p></blockquote><p>It is. The basic problem is the game client's a 32-bit program. That means it's got 2 gigabytes of memory for it's data, period, because of the the way Windows allocates virtual address space for 32-bit programs. It's not so much that it's running out of memory, it's that memory's getting fragmented by allocations and deallocations to the point where there's not a big enough single chunk of free memory to fill the request and Windows can't expand the address space to make any more available. The only fix is to convert the game client to a 64-bit program, and depending on how it was coded that may not be feasible (a lot of code assumes that ints and/or longs are the same size as pointers, and Windows elected to make ints and longs 32-bit types even on 64-bit versions so there's no simple way of converting that kind of code over).</p>

[MindiMaxi2]

<p><cite>Jrral@Unrest wrote:</cite></p><blockquote><p><cite>The_Cheeseman wrote:</cite></p><blockquote><p>This is not a PC problem, it's a game client problem.</p></blockquote><p>It is. The basic problem is the game client's a 32-bit program. That means it's got 2 gigabytes of memory for it's data, period, because of the the way Windows allocates virtual address space for 32-bit programs. It's not so much that it's running out of memory, it's that memory's getting fragmented by allocations and deallocations to the point where there's not a big enough single chunk of free memory to fill the request and Windows can't expand the address space to make any more available. The only fix is to convert the game client to a 64-bit program, and depending on how it was coded that may not be feasible (a lot of code assumes that ints and/or longs are the same size as pointers, and Windows elected to make ints and longs 32-bit types even on 64-bit versions so there's no simple way of converting that kind of code over).</p></blockquote><p>Does this mean that when they recently increased the size of the assets (mentioned several times in the tech/support forums where they justify/explain the rash of recent out of memory errors) the chances of running into an out of memory error has greatly increased because of:</p><p> "...memory getting fragmented by allocations and deallocations to the point where there's not a big enough <strong><em>single</em></strong> chunk of free memory to fill the request...."</p><p>So, larger assets, less wiggle room...?</p><p>Or so large, no room for error?</p>

[Felshades]

<p><cite>Wurm wrote:</cite></p><blockquote><p><cite>Elomort wrote:</cite></p><blockquote><p>Try closing the new launcher.</p></blockquote><p>And how is that going to help an in game problem?</p></blockquote><p>I have 4 gigs of ram and do not get the out of memory issue.</p><p>It slows down after a while, and I'm not monitoring my memory usage.. but I have yet to crash because I ran out of memory. And I'm often running two clients. I close the launcher.</p><p>The launcher is a resource hog.</p>

[Felshades]

<p><cite>Mayerling wrote:</cite></p><blockquote><p>24gigs ram... Intel I7-950... Windows 7 pro... Velociraptor and SSD drive... AMD 6850 1Gig GDDR5 Vmem... MemLeak... not my computer.</p></blockquote><p>How big's the pagefile?</p><p>Also, Im not entirely sure even windows 7 can handle 24 gigs of ram off the top of my head. I'd have to look it up.</p><p>And if you got 24 gigs of ram I'm hoping you're still using the standard size pagefile(double your ram).</p><p>I have an 8 gig page file and no issues...</p>

[Felshades]

<p><cite>MindiMaxi2 wrote:</cite></p><blockquote><p><cite>Jrral@Unrest wrote:</cite></p><blockquote><p><cite>The_Cheeseman wrote:</cite></p><blockquote><p>This is not a PC problem, it's a game client problem.</p></blockquote><p>It is. The basic problem is the game client's a 32-bit program. That means it's got 2 gigabytes of memory for it's data, period, because of the the way Windows allocates virtual address space for 32-bit programs. It's not so much that it's running out of memory, it's that memory's getting fragmented by allocations and deallocations to the point where there's not a big enough single chunk of free memory to fill the request and Windows can't expand the address space to make any more available. The only fix is to convert the game client to a 64-bit program, and depending on how it was coded that may not be feasible (a lot of code assumes that ints and/or longs are the same size as pointers, and Windows elected to make ints and longs 32-bit types even on 64-bit versions so there's no simple way of converting that kind of code over).</p></blockquote><p>Does this mean that when they recently increased the size of the assets (mentioned several times in the tech/support forums where they justify/explain the rash of recent out of memory errors) the chances of running into an out of memory error has greatly increased because of:</p><p> "...memory getting fragmented by allocations and deallocations to the point where there's not a big enough <strong><em>single</em></strong> chunk of free memory to fill the request...."</p><p>So, larger assets, less wiggle room...?</p><p>Or so large, no room for error?</p></blockquote><p>I want to say larger, less wiggle room.</p><p>Ideally you'd want windows to defragment the pagefile now and again as it's being used, as the page file is whats being used when theres not enough space in your ram to fit the item in, but pagefile is only defragmented when you tell it to be, much like hard drive space.</p><p>Defragmenting ram occurs when you reboot.</p>

[Elomort]

<p><cite>Wurm wrote:</cite></p><blockquote><p><cite>Elomort wrote:</cite></p><blockquote><p>Try closing the new launcher.</p></blockquote><p>And how is that going to help an in game problem?</p></blockquote><p>The launcher uses a ton of the 32 bit memory space needed by the game. If you close it then that memory is free and available for the game to use. The game then won't crash quite as much, if at all.</p><p>Works for me, ymmv... however... it won't hurt trying will it?</p>

[Jrral]

<p><cite>Felshades wrote:</cite></p><blockquote><p>Ideally you'd want windows to defragment the pagefile now and again as it's being used, as the page file is whats being used when theres not enough space in your ram to fit the item in, but pagefile is only defragmented when you tell it to be, much like hard drive space.</p></blockquote><p>Having the pagefile fragmented degrades performance, but it doesn't have any effect on memory allocation. If I have 2 contiguous pages of memory, they can be mapped to 2 non-consecutive blocks of the pagefile without any problem.</p><p>The only way I know to defrag the pagefile is to turn it off, reboot, remove the old pagefile, defrag the disk, then turn on the pagefile again setting it's size to a specific size so Windows allocates it as a single contiguous chunk of disk space.</p>

[Axyrem]

<p><cite>Jrral@Unrest wrote:</cite></p><blockquote><p><cite>Felshades wrote:</cite></p><blockquote><p>Ideally you'd want windows to defragment the pagefile now and again as it's being used, as the page file is whats being used when theres not enough space in your ram to fit the item in, but pagefile is only defragmented when you tell it to be, much like hard drive space.</p></blockquote><p>Having the pagefile fragmented degrades performance, but it doesn't have any effect on memory allocation. If I have 2 contiguous pages of memory, they can be mapped to 2 non-consecutive blocks of the pagefile without any problem.</p><p>The only way I know to defrag the pagefile is to turn it off, reboot, remove the old pagefile, defrag the disk, then turn on the pagefile again setting it's size to a specific size so Windows allocates it as a single contiguous chunk of disk space.</p></blockquote><p>i am running EQ2 from SSD with 8GB ..... this game is infected by many many memory leaks.</p><p>Kunzar Jungle is unplayble</p><p>Moors of Ykesha is unplayble</p><p>it sucks period...</p>

[Lthena]

<p><strong>Just because the game cannot allocate any more RAM, does NOT mean there is a memory leak. </strong>As others have said, EQ2 is 32 bit, and therefore if it tries to allocate more than 2 GB of RAM, you'll automatically get that error even if you have more memory available.</p><p>I run the game on pretty 'low' settings and I'm around 1.4 GB of RAM for EQ2. I'm assuming if you have the game set to the highest settings it will indeed near 2 GB and automatically cause the error as it loads more assets.</p><p>I'm also greatly surprised many people complained about getting the error and reported how much total memory they have, <strong>but did not bother to report how much RAM the game was using when it crashed</strong>, especially with complaining about a memory leak.</p><p>Also I'm not saying there isn't a memory leak, but rather the out of memory error can be reported when a 32bit program NORMALLY requests too much memory.</p>

[The_Cheeseman]

<p>It may be true that it's not a memory leak, but since it just started happening after the AoD launch, it certainly seems to be related to some change to the game client and how it allocated memory. If the client is "working as intended" but is now unstable on a 32-bit OS due to requiring too much memory, they either need to update the game's minimum specifications, or change it back to the way it was.</p><p>I have been running the game without incident on High Performance for years. Ever since AoD launch, logging into the guild hall will crash my client unless I lower those settings. And when I say lower, I don't just mean Extreme Performance, I mean a custom configuration wherein I have manually set every single option to minimum. That is the only way I can load the T3 commonlands guild hall without the client blowing-up in my face. I have to believe this is a bug, because if it's an intended change, my time playing EQ2 may be reaching its end.</p>

[Lthena]

<p><cite>The_Cheeseman wrote:</cite></p><blockquote><p>It may be true that it's not a memory leak, but since it just started happening after the AoD launch, it certainly seems to be related to some change to the game client and how it allocated memory. If the client is "working as intended" but is now unstable on a 32-bit OS due to requiring too much memory, they either need to update the game's minimum specifications, or change it back to the way it was.</p><p>I have been running the game without incident on High Performance for years. Ever since AoD launch, logging into the guild hall will crash my client unless I lower those settings. And when I say lower, I don't just mean Extreme Performance, I mean a custom configuration wherein I have manually set every single option to minimum. That is the only way I can load the T3 commonlands guild hall without the client blowing-up in my face. I have to believe this is a bug, because if it's an intended change, my time playing EQ2 may be reaching its end.</p></blockquote><p>I'm not saying the problem is on your end, but do all your guildmates suffer the same problem, when zoning into the guild hall?</p>

[Avirodar]

<p><cite>Lthena wrote:</cite></p><blockquote><p><strong>Just because the game cannot allocate any more RAM, does NOT mean there is a memory leak. </strong>As others have said, EQ2 is 32 bit, and therefore if it tries to allocate more than 2 GB of RAM, you'll automatically get that error even if you have more memory available.</p><p>I run the game on pretty 'low' settings and I'm around 1.4 GB of RAM for EQ2. I'm assuming if you have the game set to the highest settings it will indeed near 2 GB and automatically cause the error as it loads more assets.</p><p>I'm also greatly surprised many people complained about getting the error and reported how much total memory they have, <strong>but did not bother to report how much RAM the game was using when it crashed</strong>, especially with complaining about a memory leak.</p><p>Also I'm not saying there isn't a memory leak, but rather the out of memory error can be reported when a 32bit program NORMALLY requests too much memory.</p></blockquote><p>Hi.I have had my EQ2 client up to 2.8GB of memory used.  Default EQ2 install. Default OS install. No modified system settings.With such, you may want to validate your facts before you talk about what will and will not happen automatically.</p>

[Sandyfoot]

<p>One thing I did discover while trying to troubleshoot my eq2 deadlock errors is that Creative Lab's THX True Studio software can take up a huge amount of Modified memory space, sometimes well over 50% of the total memory in the Windows 7 resource monitor's Memory tab, Physical Memory > graph bar.</p><p>My computer has 8gigs of RAM and a discrete  ATI graphics card with 1 gb of ram. I turned off THX True Studio (the software has an off/on switch) and things improved somewhat. I then used msconfig to do a selective startup without the THX software along with a couple of other things Creative decided to add... and performance greatly improved (with the exception that the quality of the sound degraded without THX).</p><p>The THX software is supposed to "help" the RealTek onboard audio to sound better and bigger. But after doing some research on what could cause huge amounts of Modified memory to be used in Windows 7 x64, leaks seem to be the culprit. I am beginning to believe that the Miles Sound in EQ2 along with THX True Studio was contributing to my problem.</p><p>But for me, disabling THX True Studio has greatly improved performance but has not totaly solved the deadlocks.</p><p>I haven't tried running the game through HDMI audio yet to see if there is any difference in performance.</p>

[Lthena]

<p><cite>Avirodar@Oasis wrote:</cite></p><blockquote><p><cite>Lthena wrote:</cite></p><blockquote><p><strong>Just because the game cannot allocate any more RAM, does NOT mean there is a memory leak. </strong>As others have said, EQ2 is 32 bit, and therefore if it tries to allocate more than 2 GB of RAM, you'll automatically get that error even if you have more memory available.</p><p>I run the game on pretty 'low' settings and I'm around 1.4 GB of RAM for EQ2. I'm assuming if you have the game set to the highest settings it will indeed near 2 GB and automatically cause the error as it loads more assets.</p><p>I'm also greatly surprised many people complained about getting the error and reported how much total memory they have, <strong>but did not bother to report how much RAM the game was using when it crashed</strong>, especially with complaining about a memory leak.</p><p>Also I'm not saying there isn't a memory leak, but rather the out of memory error can be reported when a 32bit program NORMALLY requests too much memory.</p></blockquote><p>Hi.I have had my EQ2 client up to 2.8GB of memory used.  Default EQ2 install. Default OS install. No modified system settings.With such, you may want to validate your facts before you talk about what will and will not happen automatically.</p></blockquote><p>Take a peek at: <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/aa366778%28v=vs.85%29.aspx#memory_limits" target="_blank" rel="nofollow">http://msdn.microsoft.com/en-us/lib...x#memory_limits</a>You'll see that with the default settings a 32 bit application is stuck at 2 GB of virtual space, which does include paging.Now I could believe the Microsoft article, or I could believe a random forum poster, who claims that they haven't changed any settings, but failed to include some key details (OS? Architecture?) and expect me to believe they haven't inadvertently changed any system settings.I'll be optimistic of your report though, and assume Windows 7 (are you using Windows 7?) combines File Cache into the process memory usage in some manner, so you can't accurately see how much memory the process is actually using.</p>

[Lthena]

<p><cite>Felshades wrote:</cite></p><blockquote>I want to say larger, less wiggle room.<p>Ideally you'd want windows to defragment the pagefile now and again as it's being used, as the page file is whats being used when theres not enough space in your ram to fit the item in, but pagefile is only defragmented when you tell it to be, much like hard drive space.</p><p>Defragmenting ram occurs when you reboot.</p></blockquote><p>I think mentioning the page file stuff can be helpful, especially for those who keep a lot of stuff running or have limited system RAM, but I think most people these days have more than 2GB free (Windows 7 may report less free, since it likes to use unused RAM for File Cache).</p><p>Increasing the size of the Page File, won't help if EQ2 does hit the 32-bit 2GB limit. There's a switch/flag that off by default that people can turn on to allow 32-bit applications to use more RAM (if the application supports the flag). Since there's an article on the support forums on it, I assume it does work for EQ2 and it can be found here: <a href="http://forums.station.sony.com/eq2/posts/list.m?topic_id=506883" target="_blank" rel="nofollow">http://forums.station.sony.com/eq2/...topic_id=506883</a></p>

[Wurm]

<p><cite>Felshades wrote:</cite></p><blockquote><p><cite>Mayerling wrote:</cite></p><blockquote><p>24gigs ram... Intel I7-950... Windows 7 pro... Velociraptor and SSD drive... AMD 6850 1Gig GDDR5 Vmem... MemLeak... not my computer.</p></blockquote><p>How big's the pagefile?</p><p>Also, Im not entirely sure even windows 7 can handle 24 gigs of ram off the top of my head. I'd have to look it up.</p><p>And if you got 24 gigs of ram I'm hoping you're still using the standard size pagefile(double your ram).</p><p>I have an 8 gig page file and no issues...</p></blockquote><p>Windows 7 64bit:</p><p>Pro or better supports up to 192gigs of ram.</p><p>Home starter/basic 8 gigs and Home premium 16 gigs.</p>

[Avirodar]

<p><cite>Lthena wrote:</cite></p><blockquote><p><cite>Avirodar@Oasis wrote:</cite></p><blockquote><p><cite>Lthena wrote:</cite></p><blockquote><p><strong>Just because the game cannot allocate any more RAM, does NOT mean there is a memory leak. </strong>As others have said, EQ2 is 32 bit, and therefore if it tries to allocate more than 2 GB of RAM, you'll automatically get that error even if you have more memory available.</p><p>I run the game on pretty 'low' settings and I'm around 1.4 GB of RAM for EQ2. I'm assuming if you have the game set to the highest settings it will indeed near 2 GB and automatically cause the error as it loads more assets.</p><p>I'm also greatly surprised many people complained about getting the error and reported how much total memory they have, <strong>but did not bother to report how much RAM the game was using when it crashed</strong>, especially with complaining about a memory leak.</p><p>Also I'm not saying there isn't a memory leak, but rather the out of memory error can be reported when a 32bit program NORMALLY requests too much memory.</p></blockquote><p>Hi.I have had my EQ2 client up to 2.8GB of memory used.  Default EQ2 install. Default OS install. No modified system settings.With such, you may want to validate your facts before you talk about what will and will not happen automatically.</p></blockquote><p>Take a peek at: <a rel="nofollow" href="http://msdn.microsoft.com/en-us/library/windows/desktop/aa366778%28v=vs.85%29.aspx#memory_limits" target="_blank">http://msdn.microsoft.com/en-us/lib...x#memory_limits</a>You'll see that with the default settings a 32 bit application is stuck at 2 GB of virtual space, which does include paging.Now I could believe the Microsoft article, or I could believe a random forum poster, who claims that they haven't changed any settings, but failed to include some key details (OS? Architecture?) and expect me to believe they haven't inadvertently changed any system settings.I'll be optimistic of your report though, and assume Windows 7 (are you using Windows 7?) combines File Cache into the process memory usage in some manner, so you can't accurately see how much memory the process is actually using.</p></blockquote><p>Was it you, or someone else, who said this? :  <em>"As others have said, EQ2 is 32 bit, and therefore if it tries to allocate more than 2 GB of RAM, you'll automatically get that error even if you have more memory available."</em>... Yes, or no?So if a 32 bit application has to follow relevant 32 bit rules, even when run on a 64 bit OS, how does EQ2 exceed 2GB of RAM for me on stock settings? You then went on to talk in profound amazement that people who crash are not saying how much RAM was being used at the time they crashed. I have not crashed from running out of memory since AoD launched. But within 2 minutes, I can easily get my memory usage in EQ2 up over 2.5GB. If I spend a few minutes, I can get it up to 2.7-2.8GB. According to you, I should have crashed 700-800MB of RAM ago?From watching my resource monitor tool, I was able to observe pagefile usage, physical ram usage, and more. I can confirm that the EQ2 client was indeed consuming the 2.5+GB of physical RAM stated. So unless my PC came with 4GT/LLA already enabled for 32 bit apps, which is quite unlikely for stock default, I can either listen to you try to tell me I did something that is impossible, or stand by the results that I can replicate at whim.So either the post by some random on a microsoft website is wrong.Or the RAM usage as displayed by the Resource Monitor in Win7 is wrong.Or you misunderstood the information posted on the website by a microsoft staff member, and/or how it applies to EQ2.There is a reason I cautioned people (on another thread) from jumping blindly and changing system settings, without understanding exactly what it does, and if it applies directly to them. If you are all about posting links from microsoft pages, here is another observation from another microsoft staff member : <a href="http://blogs.msdn.com/b/oldnewthing/archive/2005/06/01/423817.aspx" target="_blank">http://blogs.msdn.com/b/oldnewthing.../01/423817.aspx</a>As others have noted, it appears EQ2 is large file address aware, which means...</p>

[Griffildur]

<p><cite>Mowster@Everfrost wrote:</cite></p><blockquote><p>Although I know that the response will be "Upgrade your computer its not the game"....</p><p>Fact...I had no issues playing until the freeport revamp. Xpac=sudden major memory crashes.</p><p>Fact...I uninstalled and reinstalled the game.</p><p>Fact...after said reinstall memory issue was gone. No issue loading even into large gh even on balanced settings.</p><p>Fact...physical memory usage after reinstall once again showed around 60%</p><p>Fact...thursday they did an update.</p><p>Fact...after the update, again with the crashing and running out of memory.</p><p>Fact...now my memory usage is, once again, hitting 100% then crashing.</p><p>Fact...I am NOT the only player experiencing this problem and it has gotten worse since the Xpac.</p><p>Fact...I could double my memory to 8 gigs and I am sure that I would still crash from low memory.</p><p>Fact...this is the ONLY game that I cannot play now much of the time because of crashes, yet it is the only game that I pay to play<---gee am i the only one who thinks there is something seriously wrong with that picture.</p><p>Fact...this game has a known issue with memory leakage.</p><p>Fact...I pay $15 for 30 days of this game, yet cannot play all 30 days because of game issues and crashes.</p><p>Conclusion...it's not my computer, it's the game.</p><p>Suggestion...hey Sony, instead of charging us $15 for 30 days regardless of our ability to play, how about only racking up the charge for the days we actually can log in and play. If I have paid for 30 days(a month)but only have logged on for say 15 of those, don't charge account again until 30 days of actual play time has been logged. Because I bet the impact of players not logging on and getting charged because they are unable to actually log in and play the game would encourage the devs to fix the problem post haste.</p><p>Fact...memory leaks, game crashes, lagging, and station launcher snafus would hasitly become a thing of the past.</p></blockquote><p>I am not saying you're wrong , I do have 8 gb of memory though and nevr had out of memory issues. That was the whole point <img src="/eq2/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" />.</p><p>At this point in time I get some disconnects sometimes, 1 maybe 2 per day. This does not make the game unplayable at all.</p><p>You might have some points but you need to stop being so melodramatic, it's not as bad as you make it sound.</p>

[CoLD MeTaL]

<p>I have three machines i play all day on.</p><p>I with 2gb of RAM, the other 2 have 4Gb, no crashes etc.  No zone times over a minute these days.</p><p>I don't think its the game.</p><p>I would suspect a custom UI, although i use profit and its fine.</p>

[Loxus]

<p><cite>Gaealiege@Butcherblock wrote:</cite></p><blockquote><p>Yeah, there is definitely a memory leak in game.  ESPECIALLY observed in Freeport.  I'm running with 12 Gig of RAM and my client will crash letting me know I don't have enough memory to allocate....yeah right. </p><p><strong><span style="font-size: small;">I run the top PC games in existence in their highest settings well over 60 FPS and never, after hours of gameplay, have I seen a memory issue. <span style="text-decoration: underline;">(Skyrim,</span> Crysis 2, etc.)</span></strong></p><p>The last time SOE had a memory leak they told the players for months "nuh uh!"</p><p>Then after a few months they said "Well ...yeah you were right" and fixed it.  I expect them to do the same thing again here.  You'll see reps responding with the usual soft-headed, imbecilic replies like "Have you updated your drivers?"</p></blockquote><p>Um, you realize Skyrim had a HUGE memory leak up to the 1/4/12 patch right?  Kinda shoots your knowledge of memory leaks right out of the water wouldn't you say?</p>

[TSR-JoshuaM]

<p><cite>Gaealiege@Butcherblock wrote:</cite></p><blockquote><p>Yeah, there is definitely a memory leak in game.  ESPECIALLY observed in Freeport.  I'm running with 12 Gig of RAM and my client will crash letting me know I don't have enough memory to allocate....yeah right.  I run the top PC games in existence in their highest settings well over 60 FPS and never, after hours of gameplay, have I seen a memory issue. (Skyrim, Crysis 2, etc.)</p><p>The last time SOE had a memory leak they told the players for months "nuh uh!"</p><p>Then after a few months they said "Well ...yeah you were right" and fixed it.  I expect them to do the same thing again here.  You'll see reps responding with the usual soft-headed, imbecilic replies like "Have you updated your drivers?"</p></blockquote><p>Just to let you know, no version of windows allows you to actually use all of your ram for a single application.  There are per application limitations, which by default is 2GB.  You can have 500000000000GB of ram but EQII won't be able to use over 2GB of it unless you allow it to.</p><p>In any case, I'll provide troubleshooting on a case by case basis.  For this thread, I am locking it up and asking everyone here with ongoing problems to open a support ticket and stick to it.</p><p>There have been hundreds of threads separating what ongoing issues we have right now and the misuse of terms like memory leaks and so on, so I am not going to allow further discussion unless it is a request for troubleshooting from your fellow players or myself.  </p>