I too was crashing frequently from no memory.  It has gotten better since the patch, but I am still having major lag issues in almost every zone and you can forget getting into the guild hall without a very long wait.  I have all my settings to med - low where as before I was running everything at EQ 2 default.  I am not sure what is going on, but the lag is so bad that I can barely play at all anymore.

Here is my opinion.  Since the introduction of Guild Halls the memory footprint of the game has gotton out of hand.  And imo the only way to fix it is for the game to flush ALL guild hall textures out of memory when you leave.

That's the only way you are going to fix this problem.

Guild Hall testing.  All tests start on Commonlands Dock:

Mode: Extreme Performance

MEM usage: 602,612KB

Zone to Guild Hall

MEM usage: 1,318,308KB

Exit door back to Commonlands

MEM usage: 1,193,728KB

So even on the lowest graphics setting after entering my guild hall I walk around with almost double my initial memory footprint.  Now let's try it at High Quality:

Mode: High Quality

MEM usage: 788,660KB

Zone to Guild Hall

MEM usage: 2,288,884KB

Exit door back to Commonlands

MEM usage: 1,987,360KB

So almost 1.2GB of memory more than I started with and I am back in the same starting zone.

My bet is every single person who is experiencing significant crashing is doing so after entering their Guild Hall.  If they did a night of gaming and never went into their Guild Hall they would likely have no problems unless they zoned a significant amount of times.

So you need to flush Hall textures and let us have longer load times to get in when we want to get in.....which for most people who are not raiding will only be 2 times a night most likely.

Kulanae@Blackburrow wrote:

So you need to flush Hall textures and let us have longer load times to get in when we want to get in.....which for most people who are not raiding will only be 2 times a night most likely.

This is already being done.  The memory that you're noticing is memory that Windows is holding on to in order to optimize performance for the application.  I assume you're looking at the "Working Set" value in Task Manager?

http://msdn.microsoft.com/en-us/lib...28VS.85%29.aspx

From the recent tests we've done, the EQ2 client is not holding any references to guild hall resources when you leave.  The working set generally does not get decreased in size until Windows needs the ram for something else.

Personally I found the latest patch to have -- for the most part -- improved things a great deal. The only area I noticed which was actually worse than before was while inside Neriak. Every time I've zoned in since the patch, the game begins to stutter (not happening anywhere else), and twice I've crashed with out of memory errors.

D.

I again crashed due to teh memory erro when leaving from my last kill on a second Solo shard run. I play the game at high quality (Which I did before this problem occured and it did nto crash -at all- ) So that was a bunch of zone ins... two from teh guildhall, three from the portal in LS.

Rothgar wrote:

Kulanae@Blackburrow wrote:

So you need to flush Hall textures and let us have longer load times to get in when we want to get in.....which for most people who are not raiding will only be 2 times a night most likely.

This is already being done.  The memory that you're noticing is memory that Windows is holding on to in order to optimize performance for the application.  I assume you're looking at the "Working Set" value in Task Manager?

http://msdn.microsoft.com/en-us/lib...28VS.85%29.aspx

From the recent tests we've done, the EQ2 client is not holding any references to guild hall resources when you leave.  The working set generally does not get decreased in size until Windows needs the ram for something else.

One of the old school "tricks" to get eq2 to release some ram was to go windowed mode and then minimize the window.  Does it keep the "working set" memory when you do that?

ArivenGemini wrote:

Rothgar wrote:

Kulanae@Blackburrow wrote:

So you need to flush Hall textures and let us have longer load times to get in when we want to get in.....which for most people who are not raiding will only be 2 times a night most likely.

This is already being done.  The memory that you're noticing is memory that Windows is holding on to in order to optimize performance for the application.  I assume you're looking at the "Working Set" value in Task Manager?

http://msdn.microsoft.com/en-us/lib...28VS.85%29.aspx

From the recent tests we've done, the EQ2 client is not holding any references to guild hall resources when you leave.  The working set generally does not get decreased in size until Windows needs the ram for something else.

 

One of the old school "tricks" to get eq2 to release some ram was to go windowed mode and then minimize the window.  Does it keep the "working set" memory when you do that?

When you minimize a window, by default, Windows trims the Working Set of unused pages.  In the case of an application that uses DirectX, you also lose the rendering context which causes other resources to be unloaded as well.  But all of this is done at the system level.  EQII isn't specifically freeing any resources when you minimize.  Most of what you are losing are resources and memory pages that EQII has already "released".

Here's some more reading if interested.

http://support.microsoft.com/defaul...kb;en-us;293215

Just another update since the last hotfix.

Pre GU53 for last 4 years i could play up to 12 hours at a time with no problems period.

I play on extreme quality all the time including in raids and have never had an issue till GU53.

After GU53, and even now after the latest hotfix I still crash 4 to 6 times a night with the

application ran out of memory error. last night 10-28-2009, i logged in already in our guild hall.

I stayed in the guild hall since ive been redecorating it for the last 6 weeks or so. Never left the

guild hall but after 45 minutes of playing CRASH : OUT OF MEMMORY REQUESTING .........

This last hotfix didnt seem to change a thing for me, and its not like I'm playing on a crappy

or outdated computer either.

Ohh and just wanted to add , at one point last night since I am getting ready to post the  pictures

of guild hall for the Norrathian Homeshow, the second I hit the PrintScreen button to take a screenshot

it instantly crashed with the Out Of Memmory error, if that is a help in any way to tracking down the issue.

System Specs:

Gigabyte MA790GP-UD4H Motherboard

AMD Phenom 9950 Quad Core CPU 2.6GHz

4 X 1 gig Corsair XMS2 PC 6400 ram sticks

Nvidia 9800 GTX w/ 1 gig DDR3 Ram

OS : Windows XP

Rothgar, I just want  to add that last night was the first night that i didnt crash thanks for the hotfix, now i have lowered my settings to balanced and experienced no probs last night while zoning between gh and TT and other zones. i was online from 10pm to 2am with no problems at these settings.

I did move the settings up to extreme Quality as to where i was running before GU53 and with in 3 minutes i did crash..Critical Error - Out of Memory.

So you have somewhat fixed the issues but this still needs to be looked into futher and have it back to where is was prior to GU53.

Keep up the good work, i have faith in you and our Devs this coming from a long time and loyal SOE Player.

Started in Eq1 at launch up to launch of Eq2 and been here ever since.

Chubbylilbuddy.

Sadly, after a full day from the last hotfix, I thought it was improving but it's definitely not. Things are the same or possibly worse. It must have been random luck that I was able to stay on for 6 hours, but today I was on for 2 hours before a full spamming memory error (pop-up error box repeatedly plus a thrown exception pop-up repeatedly) and then again after only 30 minutes! Zoning for each session was about 12-15. I was in Lavastorm for the last one, set at balanced mode. Going to try again at... sigh... extreme performance. =(

I was lucky enough to get a x2 for Opal Darkbriar for my epic, we pull it, i hit my temps... and I crash, again. No update, half the people leave after killing.

This is the 3rd crash this day. I am really really getting tired of this. EQ2 is working so slow its not even funny, and I run other games with max details. I mean cmon...

Kizaxia@Kithicor wrote:

 

Ohh and just wanted to add , at one point last night since I am getting ready to post the  pictures

of guild hall for the Norrathian Homeshow, the second I hit the PrintScreen button to take a screenshot

it instantly crashed with the Out Of Memmory error, if that is a help in any way to tracking down the issue.

 

I can support this problem. takign screenshtos mostly crashes me with the same error.

I ran a series of memory monitoring with notes today when I got home. I dunno if this helps at all. I tried to write down what I was doing at key moments in the game, and then what my memory was doing. This is essentially a timeline of events from the moment I logged on until I crashed. About 3 hours.. Format is as follows:

Time CST PM Memory of EverQuest in Task Manager (I tried to wait until it was relatively stable and no longer adjusting)
- activities done

Here's the log:

7:13 900mb
- logged into guild hall
- crafted 4 items
- broker
7:33 1gb
- zoned to lavastorm
7:36 1.03gb
- used in-game browser to open wikia
7:38 1.05gb
- combat, various quests
- teleport within lavastorm 4 times
8:13 1.00gb
- afk, character standing still
9:10 1.00gb
- moved up to very high performance
9:17 1.07gb
- ran around lavastorm for quests
9:38 1.14gb
- zoned to Nektulos
9:39 1.05gb
- zone to Thundering Steppes
9:40 1.05gb
- zone to antonica
9:41 1.06gb
- zone to guild hall (T3 980/1600 items)
9:42 1.07gb
- teleport to crafting area
9:43 1.09gb
- standing still in guild hall
9:45 1.16gb
- spinning in place in guild hall
9:46 1.19gb
- running around in guild hall for 4 minutes
- jumped off balconies 10 times
9:49 1.36gb
- teleported 5 times within the guild via pads
9:51 1.395gb
- left guild hall via front door
- stood still on docks for 2 minutes
9:53 1.35gb
- re-entered guild hall
9:54 1.34gb
- teleport to crafting area
- stood still 2 minutes
9:56 1.30gb
- ran around guild hall jumping off balconies for 2 minutes
9:58 1.33gb
- removed horse, repeat run around
10:00 1.30gb
- afk, stood still
10:10 1.25gb
- zone to house (Gorowyn, 66/600 items)
10:11 1.21gb
- turned up to high performance
10:14 1.39gb
- (it took 3 minutes to shift from very high to high performance)
- zone to guild hall
10:15 1.42gb
- teleport to transportation room
- zone to house
10:17 1.40gb
- upgrade to balanced mode
- (took no time to upgrade modes)
10:18 1.49gb
- zone to guild hall
10:19 1.55gb
- teleport to crafting area
- stood still 2 minutes
10:21 1.61gb
- jumped off balcony 1, ran up stairs, jumped off different balcony

10:22 1.643gb
- Very laggy then ... CRASH!!

****CRASH!****

EverQuest II has detected an unrecoverable error and must shutdown.
<verify>
E:\live\eq2\framework\core\devices\src\DirectX9RenderDevice.cpp
(2704):
DirectX Error. (E_OUTOFMEMORY)
009c72b5 009ca778

Other applications running:
iTunes 56k
firefox 150k (variable)

Other info:
gnome necromancer 55 riding the RaF evil horse
guild hall is T3 Blackhawks, mostly empty (most people were raiding at the time)
house is Gorowyn 6-room house, few items out, most in moving crate

Not sure if any of this is helpful. It seems to me that guild hall and possibly instances (I have yet to test this, but this is my impression from previous crash issues) have trouble getting rid of memory. When I leave the guild hall, I still have a very high memory usage, that is then compounded when I return later. Of course, this is just my observation. I hope this helps track down possible memory leaks or whatnot. I will post more logs like this if they help, it's no problem really.