EverqQuest2.exe 1.8gigs of memory usage?!?!? [Archive]

Hiburp

09-23-2009, 09:07 PM

Newest update greatly increased memory usage.One instance of EQ is using 1,888,824k of memory and the other instance is using 1,406,688k.I'm getting low memory issuses with just 2 instances of EQ running. Before I could run 3 plus Firefox without issues.

cr0wangel

09-23-2009, 09:29 PM

I went out memory while being AFK in my guild hall... I wasn't even zoning, I was standing AFK and the game crashed, out of the memory. There is something wrong in that patch/update.

Yarginis

09-24-2009, 12:59 AM

Memory useage is indeed WAY up since GU53. I'm showing EQ2 using between 2.7 and 2.9gb... and as I just posted actually crashed due to reaching the 3gb memory (thats 3072 mb...) Thats a bit rediculous. Before I would sometimes see 2.6gb in a full t3 guild hall, but now I am seeing 2.7gb+ in almost all zones.Would much appriciate this being looked into.

Rigamort

09-24-2009, 02:04 AM

seeing the same issues. Pre Update of 23rd I was running 2-3 clients in Custom w/ max textures / lighting and Particles using GPU Shadows. If I went into guild hall I would lag a bit, but anywhere else I was fine. 3boxing SoF, Cruc, whever I was able to run all 3 in that performance mode no problems.As of today, First client lags like it did running 3 when in GH alone. Zoning is 30% slower, running 2 clients the second client will show wireframe only for spell effects, and particles and will show NO ground harvestable items. For instance SoF, most things like the arrow above my head are all wireframe on account #1 and no harvestable items like the hearts or essance can be seen.If I log that one account in, works fine. 2 accounts no longer. To repeat this worked as of yesterday, and everyday before that. I have never had issues outside of our guild house which has a ton of items. The memory usage has gone up and it also seems as the pagefile (Virtual Ram) is getting Hammered every few seconds.

Autenil

09-24-2009, 03:07 AM

Hi all,Thanks for reporting this issue. I believe I know what is causing the additional memory usage. I'll let Rothgar and Brenlo know so they can get it hotfixed.

Ldarax

09-24-2009, 08:34 AM

<cite>Autenil wrote:</cite><blockquote>Hi all,Thanks for reporting this issue. I believe I know what is causing the additional memory usage. I'll let Rothgar and Brenlo know so they can get it hotfixed.</blockquote>Thank you! <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" />

ElsaRat

09-24-2009, 11:16 AM

Thank you, Autenil. Just now Everquest crashed for lack of memory on me. It's true I only have 2 gigabytes, but that's never happened to me before, and I wasn't running much in the background.

Pijotre

09-24-2009, 11:18 AM

So EQII is set a large adress aware by default then?Because according to<a href="http://msdn.microsoft.com/en-us/library/aa366778%28VS.85%29.aspx" target="_blank"><a href="http://msdn.microsoft.com/en-us/library/aa366778%28VS.85%29.aspx" target="_blank">MSDN</a></a>it could only adress up to 2gb otherwise.If it is set as descibed then I can use 4gb of my 6gb just for 1 instance of EQII correct?

Enever

09-24-2009, 12:26 PM

Is this related to the memory leaks I've been getting since the LU too?

Drevva

09-24-2009, 06:49 PM

Just wanted to confirm that I too am seeing much higher memory usage. Use to run two instances fine with 4gb mem (vista 64) now end up swapping a lot, performance is much much worse. Seems like each instance is using at least 500MB more than they use to use.D

Rothgar

09-24-2009, 07:50 PM

We are posting a new version of the EQ2 client EXE file to the patcher very soon. This will fix the problem we have with the memory allocation that is causing these crashes. All you'll need to do is repatch and you'll get the new EXE.I'll post an official announcement when the new EXE is available.

Yarginis

09-24-2009, 08:05 PM

<cite>Pijotre@Lucan DLere wrote:</cite><blockquote>So EQII is set a large adress aware by default then?Because according to<a href="http://msdn.microsoft.com/en-us/library/aa366778%28VS.85%29.aspx" target="_blank"></a><a href="http://msdn.microsoft.com/en-us/library/aa366778%28VS.85%29.aspx" target="_blank">MSDN</a>it could only adress up to 2gb otherwise.If it is set as descibed then I can use 4gb of my 6gb just for 1 instance of EQII correct?</blockquote>EQ2 is large address aware (up to 3gb). This was introduced sometime shortly after RoK as this was when the client started hitting the 2gb limit it was previously locked at. (technically it was always designed as large address aware and could be moddified to be so, this is just when the modification became standard instead of 3rd party)Last night I still hard crashed at 3gb however, so it is not capable of using more than 3gb for one client as far as I can tell. (Which after this issue is patched is all it needs currently on max setting except in extremely full t3 GH's)Thx for the quick fix btw, Rothgar. <img src="/smilies/283a16da79f3aa23fe1025c96295f04f.gif" border="0" alt="SMILEY" />

Pijotre

09-24-2009, 08:50 PM

<cite>Alexiiya@Nektulos wrote:</cite><blockquote>EQ2 is large address aware (up to 3gb). This was introduced sometime shortly after RoK as this was when the client started hitting the 2gb limit it was previously locked at. (technically it was always designed as large address aware and could be moddified to be so, this is just when the modification became standard instead of 3rd party)Last night I still hard crashed at 3gb however, so it is not capable of using more than 3gb for one client as far as I can tell. (Which after this issue is patched is all it needs currently on max setting except in extremely full t3 GH's)Thx for the quick fix btw, Rothgar. <img src="/eq2/images/smilies/283a16da79f3aa23fe1025c96295f04f.gif" border="0" /></blockquote>Err 3gb? Under a 32-bit system yeah sure but a 32-bit application with largeadressawareness should give up to 4gb.The way I understand the flag is if disabled then 2gb if enabled then 3gb under 32-bit and 4gb under 64-bit.These restriction of course don't apply to 64-bit applications under a x64 system.

Yarginis

09-25-2009, 01:53 AM

<cite>Pijotre@Lucan DLere wrote:</cite><blockquote><cite>Alexiiya@Nektulos wrote:</cite><blockquote>EQ2 is large address aware (up to 3gb). This was introduced sometime shortly after RoK as this was when the client started hitting the 2gb limit it was previously locked at. (technically it was always designed as large address aware and could be moddified to be so, this is just when the modification became standard instead of 3rd party)Last night I still hard crashed at 3gb however, so it is not capable of using more than 3gb for one client as far as I can tell. (Which after this issue is patched is all it needs currently on max setting except in extremely full t3 GH's)Thx for the quick fix btw, Rothgar. <img src="/eq2/images/smilies/283a16da79f3aa23fe1025c96295f04f.gif" border="0" /></blockquote>Err 3gb? Under a 32-bit system yeah sure but a 32-bit application with largeadressawareness should give up to 4gb.The way I understand the flag is if disabled then 2gb if enabled then 3gb under 32-bit and 4gb under 64-bit.These restriction of course don't apply to 64-bit applications under a x64 system.</blockquote>Yes, 3gb I am sure. I am running win7 x64 (4gb RAM, 4gb pagefile, 512mb readyboost) & I crashed as soon as eq2 hit 3gb used with application has run out of memort while requesting error, limit 3072mb (aka 3gb)& on a note of the client patch tonight. This has helped greatly, but it is still using significantly more memory than before GU53. (I'd say we're 2/3-3/4 of the way back to where we were)

Pijotre

09-25-2009, 06:21 AM

Yeah but that is because the Kernel reserves 1 GB for itself. So still not a proof.

Dawnya

09-25-2009, 03:25 PM

So I thought the memory crashing problem was fixed? I'm still crashing due to it unfortunately though and I've tried patching several times... its particularly annoying really... was not having this issue before the update. <img src="/eq2/images/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" />

Rothgar

09-25-2009, 03:26 PM

<cite>Dawnya@Antonia Bayle wrote:</cite><blockquote>So I thought the memory crashing problem was fixed? I'm still crashing due to it unfortunately though and I've tried patching several times... its particularly annoying really... was not having this issue before the update. <img src="/eq2/images/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" /></blockquote>We did indeed fix the problem that was causing the client to allocate more memory than necessary, but its possible you are suffering from a different issue.PM me your server and character name. I will look at your uploaded crash logs.

Sphiriah

09-25-2009, 04:15 PM

<cite>Rothgar wrote:</cite><blockquote><cite>Dawnya@Antonia Bayle wrote:</cite><blockquote>So I thought the memory crashing problem was fixed? I'm still crashing due to it unfortunately though and I've tried patching several times... its particularly annoying really... was not having this issue before the update. <img src="/eq2/images/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" /></blockquote>We did indeed fix the problem that was causing the client to allocate more memory than necessary, but its possible you are suffering from a different issue.PM me your server and character name. I will look at your uploaded crash logs.</blockquote>Are you sure about that? Because I tried playing today for the first time after the patch, and I can't play for more than 10 minutes without crashing due to memory usage.

zhiDarkivel

09-25-2009, 05:10 PM

I was also having crash issues today, still.

Enever

09-25-2009, 05:36 PM

Still have Ran out of Memory Errors here. my most recent one was due to fens not fully rendering.

buffquinn

09-25-2009, 05:40 PM

Issue is still occuring, even after the .exe patch.

Krishti

09-25-2009, 06:11 PM

I am also having the same crashing issue as mentioned here. Even after that patch *sad panda face*

Jeyne

09-25-2009, 08:17 PM

I have also the "ran out of memory" issue. I had this only one time in the past, and since GU53, 2 times in an evening. That's odd.I'm on Storms server, i don't know if the new exe was delivered on it, too ...First time, i was solo (i was zoning to Lavastorm), second time during a raid.

cr0wangel

09-25-2009, 10:00 PM

I still get that bug and the game was working fine before the update, that's frankly annoying.Is there a way to fix this? I get out of memory very often and I can't really play.

Draxknor

09-25-2009, 11:13 PM

Still crashing with the ..Out of Memory.. issue... and before the patch .. everythign was "A" ok.

ra1f

09-26-2009, 01:36 AM

Getting "Application Ran out of memory when requesting 1048608 bytes..." CTD'sThis is happening only on my Vista 32, 4 gig ram installed (no comments necessary) at High Graphics setting. Never had any problems with this system previously. Once happened after running about 2 hours, second was only after about 20 minutes.Running on 2 other sytems fine, both XP, one 4 gig, one 2 gig, both low graphics settings... no problems at all on those.

Foolsfolly

09-26-2009, 03:10 AM

I really appreciate you guys getting the fix out there so fast!But yeah...like the others, after patching I'm still getting memory crashes.

Iceman7

09-26-2009, 03:32 AM

Game has been crashing with the same out of memory error for me as well. EQ2 never crashed before GU53. Crashes happened while trying to move in NQ, and while bringing up my crafting menu in Moors. Time wise about every 3 hours today. Happened on 2 different characters. EQ2 is obviously sucking up memory like never before.

MickeysIce

09-26-2009, 04:16 AM

Same, have had issues since the Update, after the patch, same deal. Never used to have this issue, I have 4 gig of ram and never had an issue running my group settings with full particles or raid settings with things turned down so you can see better. Now, with either settings, large, heavily populated/decorated guild halls = crash. Long play time is causing crashes as well.

ashen1973

09-26-2009, 11:51 AM

Lots of peopel on Splitpaw complaining of memory crashes and lower performance since the patch. I have 4Gb memory. Before GU53 my performance monitor would show memory usage at maximum of 45-50%, now it sshows a constant 65-75%

Artaguss

09-26-2009, 12:28 PM

Ditto.............Out of mem crash for me and Oasis as well

Slici

09-26-2009, 02:56 PM

Yup same here, crashing after about an hour to 2 hours play giving me application out of memory error.

cr0wangel

09-26-2009, 03:54 PM

Here part of my log:SOEBuild=5916LSOEVersionString=2009/9/24 17:56:49EVERQUEST2 CRASH LOG=============================================== ================================================== =Unhandled exception EXCEPTION_ACCESS_VIOLATION at 0x00B3CD1FApplication was trying to write to 0x00000002 Region Begins At: 0x00000000 Region Ends At: 0x00010000 Region Size Is: 0x00010000 bytes Memory Protection: PAGE_NOACCESS (00000001) Memory State: MEM_FREE Memory Type: FreeGame Data: SOEBuild: SOEBuild=5916L SOEVersionString: SOEVersionString=2009/9/24 17:56:49 OS Version: 5.1.2600 Service Pack 2 VER_SUITE_PERSONAL VER_NT_WORKSTATION CPU: 2 x86 GenuineIntel 2672MHz RDTSC MSR CMPXCHG8 SSE SSE2 DirectX Version: 9.0c Video Card/Driver: [ATI Radeon HD 3800 Series ] [ati2dvag.dll] 6.14.10.6783 {d7b71ee2-d645-11cf-cd69-3ac6a1c2cb35} Time at crash: Sat Sep 26 07:17:20 2009 Login Server: none Performance: 7 Game Uptime: 506 seconds Position last frame: -0.19, 0.01, -4.87 Zone name: qey_guildhall_tier2 Time in Zone: 38 seconds Previous Zone name: GameScene::ZR_NETWORKED_ZONE_CHANGE Multi-core support: enabled Low-Memory Mode: enabledLog: Done loading zone resources Done sending initial entities msg Set POV ghost cmd... Enabling low memory mode (current: 1639 MB, limit: 2048 MB, maxalloc: 1738 MB, addrspace: 2048 MB) Received chat channel update msg... Received chat channel update msg... Received chat channel update msg... Received chat channel update msg... <MEMORY> E:liveeq2frameworkmemoryManagersrcsharedMemoryMana ger.cpp(2010): Application ran out of memory when requesting 32784 bytes (limit: 2048 MB, current: 740 MB) <MEMORY> E:liveeq2frameworkmemoryManagersrcsharedMemoryMana ger.cpp(2010): Application ran out of memory when requesting 8208 bytes (limit: 2048 MB, current: 740 MB)

Artaguss

09-26-2009, 05:34 PM

Yep, 2 to 3 hours... Crash log from me as well..SOEBuild=5916LSOEVersionString=2009/9/24 17:56:49EVERQUEST2 CRASH LOG=============================================== ================================================== =Unhandled exception EXCEPTION_ACCESS_VIOLATION at 0x00B3CD1FApplication was trying to write to 0x00000002 Region Begins At: 0x00000000 Region Ends At: 0x00010000 Region Size Is: 0x00010000 bytes Memory Protection: PAGE_NOACCESS (00000001) Memory State: MEM_FREE Memory Type: FreeGame Data: SOEBuild: SOEBuild=5916L SOEVersionString: SOEVersionString=2009/9/24 17:56:49 OS Version: 5.1.2600 Service Pack 3 VER_NT_WORKSTATION CPU: 1 x86 AuthenticAMD 4MHz RDTSC MSR CMPXCHG8 SSE SSE2 DirectX Version: 10.0 Video Card/Driver: [ATI Radeon HD 3600 Series ] [ati2dvag.dll] 6.14.10.6983 {d7b71ee2-d6d6-11cf-706f-2220a1c2cb35} Time at crash: Sat Sep 26 15:29:02 2009 Login Server: none Performance: 7 Game Uptime: 13041 seconds Position last frame: 1765.53, 450.64, 972.25 Zone name: exp05_rgn_innothule Time in Zone: 62 seconds Previous Zone name: GameScene::ZR_NETWORKED_ZONE_CHANGE Multi-core support: disabled Low-Memory Mode: disabledLog: **** Unrecognized command - Activaed **** Unrecognized command - Activaed **** Unrecognized command - Activaed **** Unrecognized command - Activaed **** Unrecognized command - Activaed **** Unrecognized command - Activaed **** Unrecognized command - Activaed m_processUpdateSpellBookMsg() saving UI: Map2_clone_0 E:liveeq2frameworkmemoryManagersrcsharedMemoryMana ger.cpp(2010): Application ran out of memory when requesting 5625072 bytes (limit: 2048 MB, current: 908 MB)Thread Data: Primary Thread Id: 3044 Current Thread Id: 3044 Current Thread Priority: 0Memory: AddressLimitMB: 2048 Load: 78% Total physical: 3489107968 Free physical: 747835392 Total pagefile: 4294967295 Free pagefile: 4294967295 Total virtual: 2147352576 Free virtual: 131985408Memory Manager: Allocations: 373058 Bytes Allocated: 839485152 Max Allocations: 384959 Max Bytes Allocated: 944803088 System Memory Allocated (MB): 908 Limit: 2048 Number of Allocate Calls: 5897871 Number of Free Calls: 5524813

Artaguss

09-26-2009, 05:35 PM

cont...Registers: EAX 0x00000001 EBX 0x7C91005D ECX 0xA969007D EDX 0x00C5E8AA ESI 0x7C85AD4C EDI 0x0055D4F0 GS 0x00000000 FS 0x0000003B ES 0x00000023 DS 0x00000023 EBP 0x0012F0D0 ESP 0x0012E84C EIP 0x00B3CD1F FLAGS 0x00210246 CS 0x0000001B SS 0x00000023FPU Registers: CW 0xFFFF027F SW 0xFFFF0120 TW 0xFFFFFFFFFPU Rounding Mode: NearestCall Stack: 0x00B3CD1F: MemoryManager::allocate+302f 0x00C5F8C6: MemoryManager::allocate+125bd6 0x00C60BBB: MemoryManager::allocate+126ecb 0x0041F3BC in C:Program FilesSonyEverQuest IIEverQuest2.exe 0x78787878 in ????????End of Call Stack

Artaguss

09-26-2009, 05:35 PM

Stack Scan: 0x0012E84C: 0x00000000 0x0012E850: 0x6C707041 0x0012E854: 0x74616369 0x0012E858: 0x206E6F69 0x0012E85C: 0x206E6172 0x0012E860: 0x2074756F 0x0012E864: 0x6D20666F 0x0012E868: 0x726F6D65 0x0012E86C: 0x68772079 0x0012E870: 0x72206E65 0x0012E874: 0x65757165 0x0012E878: 0x6E697473 0x0012E87C: 0x36352067 0x0012E880: 0x37303532 0x0012E884: 0x79622032 0x0012E888: 0x20736574 0x0012E88C: 0x6D696C28 0x0012E890: 0x203A7469 0x0012E894: 0x38343032 0x0012E898: 0x2C424D20 0x0012E89C: 0x72756320 0x0012E8A0: 0x746E6572 0x0012E8A4: 0x3039203A 0x0012E8A8: 0x424D2038 0x0012E8AC: 0x38740029 0x0012E8B0: 0x00000048 0x0012E8B4: 0x387450C8 0x0012E8B8: 0x00140168 0x0012E8BC: 0x00140178 0x0012E8C0: 0x00000048 0x0012E8C4: 0x00005080 0x0012E8C8: 0x00140000 0x0012E8CC: 0x0012E6C4 0x0012E8D0: 0x00000000 0x0012E8D4: 0x0012E920 0x0012E8D8: 0x7C90E920, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012E8DC: 0x7C9101E0, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012E8E0: 0xFFFFFFFF, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012E8E4: 0x7C9101DB, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012E8E8: 0x7C809A7F, in C:WINDOWSsystem32kernel32.dll (0x7c800000) 0x0012E8EC: 0x00140000 0x0012E8F0: 0x00140008 0x0012E8F4: 0x7C809A90, in C:WINDOWSsystem32kernel32.dll (0x7c800000) 0x0012E8F8: 0x490E0B48 0x0012E8FC: 0x0012E96C 0x0012E900: 0x00000007 0x0012E904: 0x00140000 0x0012E908: 0x00140008 0x0012E90C: 0x7C809A90, in C:WINDOWSsystem32kernel32.dll (0x7c800000) 0x0012E910: 0x0012EA68 0x0012E914: 0x00000008 0x0012E918: 0x0012E8F8 0x0012E91C: 0x00000000 0x0012E920: 0x0012EECC 0x0012E924: 0x7C839AD8, in C:WINDOWSsystem32kernel32.dll (0x7c800000) 0x0012E928: 0x7C809A98, in C:WINDOWSsystem32kernel32.dll (0x7c800000) 0x0012E92C: 0xFFFFFFFF, in C:WINDOWSsystem32kernel32.dll (0x7c800000) 0x0012E930: 0x7C809A90, in C:WINDOWSsystem32kernel32.dll (0x7c800000) 0x0012E934: 0x4FE0A451, in C:WINDOWSsystem32d3d9.dll (0x4fdd0000) 0x0012E938: 0x00000040 0x0012E93C: 0x00000040 0x0012E940: 0x0012E950 0x0012E944: 0x4FDFB0AB, in C:WINDOWSsystem32d3d9.dll (0x4fdd0000) 0x0012E948: 0x00000040 0x0012E94C: 0x0012E974 0x0012E950: 0x0012E984 0x0012E954: 0x00140000 0x0012E958: 0x7C910222, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012E95C: 0x00000045 0x0012E960: 0x00141378 0x0012E964: 0x00140000 0x0012E968: 0x53239050 0x0012E96C: 0x0012E95C 0x0012E970: 0x00000020 0x0012E974: 0x0012EBA0 0x0012E978: 0x7C90E920, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012E97C: 0x7C910228, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012E980: 0xFFFFFFFF, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012E984: 0x7C910222, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012E988: 0x7C91019B, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012E98C: 0x7C9101DB, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012E990: 0x00000000 0x0012E994: 0x0012EED4 0x0012E998: 0x0012EEAC 0x0012E99C: 0x00000007 0x0012E9A0: 0x00000007 0x0012E9A4: 0x001AA180 0x0012E9A8: 0x00000100 0x0012E9AC: 0x00000100 0x0012E9B0: 0x00000000 0x0012E9B4: 0x68655020 0x0012E9B8: 0x00000400 0x0012E9BC: 0x00000000 0x0012E9C0: 0x490E0C78 0x0012E9C4: 0x00000080 0x0012E9C8: 0x00000080 0x0012E9CC: 0x00000000 0x0012E9D0: 0x68665020 0x0012E9D4: 0x00000200 0x0012E9D8: 0x00000000 0x0012E9DC: 0x490E0CD0 0x0012E9E0: 0x00000040 0x0012E9E4: 0x00000040 0x0012E9E8: 0x00000000 0x0012E9EC: 0x68669020 0x0012E9F0: 0x00000100 0x0012E9F4: 0x00000000 0x0012E9F8: 0x490E0D28 0x0012E9FC: 0x00000020 0x0012EA00: 0x00000020 0x0012EA04: 0x00000000 0x0012EA08: 0x6866A020 0x0012EA0C: 0x00000080 0x0012EA10: 0x00000000 0x0012EA14: 0x490E0D80 0x0012EA18: 0x00000010 0x0012EA1C: 0x00000010 0x0012EA20: 0x00000000 0x0012EA24: 0x6866A420 0x0012EA28: 0x00000040 0x0012EA2C: 0x00000000 0x0012EA30: 0x490E0DD8 0x0012EA34: 0x00000008 0x0012EA38: 0x00000008 0x0012EA3C: 0x00000000 0x0012EA40: 0x6866A520 0x0012EA44: 0x00000020 0x0012EA48: 0x00000000 0x0012EA4C: 0x490E0E30 0x0012EA50: 0x00000004 0x0012EA54: 0x00000004 0x0012EA58: 0x00000000 0x0012EA5C: 0x6866A560 0x0012EA60: 0x00000010 0x0012EA64: 0x00000000 0x0012EA68: 0x490E0E88 0x0012EA6C: 0x00000000 0x0012EA70: 0x00000000 0x0012EA74: 0x00000000 0x0012EA78: 0x00000000 0x0012EA7C: 0x00000000 0x0012EA80: 0x00000000 0x0012EA84: 0x00000000 0x0012EA88: 0x00000000 0x0012EA8C: 0x00000000 0x0012EA90: 0x00000000 0x0012EA94: 0x00000000 0x0012EA98: 0x00000000 0x0012EA9C: 0x00000000 0x0012EAA0: 0x00000000 0x0012EAA4: 0x00000000 0x0012EAA8: 0x00000000 0x0012EAAC: 0x00000000 0x0012EAB0: 0x00000000 0x0012EAB4: 0x00000000 0x0012EAB8: 0x00000000 0x0012EABC: 0x7C910435, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012EAC0: 0x7C91043E, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012EAC4: 0x0012EE30 0x0012EAC8: 0x00020024 0x0012EACC: 0x0012EC1C 0x0012EAD0: 0x00000005 0x0012EAD4: 0x7C914388, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012EAD8: 0x7FFD6000 0x0012EADC: 0x00000002 0x0012EAE0: 0x0012EAF4 0x0012EAE4: 0x7C918DFC, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012EAE8: 0x00020290 0x0012EAEC: 0x00000000 0x0012EAF0: 0x7C910460, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012EAF4: 0x7C980600, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012EAF8: 0x7C914049, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012EAFC: 0x7C91403C, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012EB00: 0x00000208 0x0012EB04: 0x0012EED4 0x0012EB08: 0x0012EEAC 0x0012EB0C: 0x000000B6 0x0012EB10: 0x00000000 0x0012EB14: 0x00000000 0x0012EB18: 0x00000000 0x0012EB1C: 0x00000000 0x0012EB20: 0x0012EC26 0x0012EB24: 0x00000000 0x0012EB28: 0x00000038 0x0012EB2C: 0x00000005 0x0012EB30: 0x00720070, in C:Program FilesSonyEverQuest IIEverQuest2.exe (0x00400000) 0x0012EB34: 0x0579AE60 0x0012EB38: 0x00000000 0x0012EB3C: 0x00000000 0x0012EB40: 0x0579AE60 0x0012EB44: 0x00000000 0x0012EB48: 0x020800B6 0x0012EB4C: 0x00000045 0x0012EB50: 0x00000000 0x0012EB54: 0x00000070 0x0012EB58: 0x00000023 0x0012EB5C: 0x00000003 0x0012EB60: 0x0012ECDE 0x0012EB64: 0x00000046 0x0012EB68: 0x01000000, in C:Program FilesSonyEverQuest IIEverQuest2.exe (0x00400000) 0x0012EB6C: 0x0012EC28 0x0012EB70: 0x00000000 0x0012EB74: 0x02080046 0x0012EB78: 0x00020290 0x0012EB7C: 0x0579AED0 0x0012EB80: 0x7C910435, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012EB84: 0x7C91043E, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012EB88: 0x0000F7BB 0x0012EB8C: 0x0012EB00 0x0012EB90: 0x0012EEAC 0x0012EB94: 0x0012EE40 0x0012EB98: 0x7C90E920, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012EB9C: 0x0012EED4 0x0012EBA0: 0x00000008 0x0012EBA4: 0x00000008 0x0012EBA8: 0x00020024 0x0012EBAC: 0x0012EEAC 0x0012EBB0: 0x0012EE50 0x0012EBB4: 0x7C910460, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012EBB8: 0x7C980600, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012EBBC: 0x7C9142E7, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012EBC0: 0x7C9142AF, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012EBC4: 0x00000000 0x0012EBC8: 0x0579AE60 0x0012EBCC: 0xFFFFFFFF 0x0012EBD0: 0x00000002 0x0012EBD4: 0x0000005F 0x0012EBD8: 0x00020024 0x0012EBDC: 0x7FFDF000 0x0012EBE0: 0x00000000 0x0012EBE4: 0x000A0008 0x0012EBE8: 0x7C91407C, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0012EBEC: 0x0000021A 0x0012EBF0: 0x00000000 0x0012EBF4: 0x00000000 0x0012EBF8: 0x00000000 0x0012EBFC: 0x00000000 0x0012EC00: 0x000000B6 0x0012EC04: 0x00000000 0x0012EC08: 0x00B80046, in C:Program FilesSonyEverQuest IIEverQuest2.exe (0x00400000) 0x0012EC0C: 0x0012EC28 0x0012EC10: 0x00720070, in C:Program FilesSonyEverQuest IIEverQuest2.exe (0x00400000) 0x0012EC14: 0x0579AE60 0x0012EC18: 0x0012EC28 0x0012EC1C: 0x00000005 0x0012EC20: 0x53239050 0x0012EC24: 0x01000000, in C:Program FilesSonyEverQuest IIEverQuest2.exe (0x00400000) 0x0012EC28: 0x003A0043, in C:Program FilesSonyEverQuest IIplc4.dll (0x003a0000) 0x0012EC2C: 0x0050005C, in C:Program FilesSonyEverQuest IIEverQuest2.exe (0x00400000) 0x0012EC30: 0x006F0072, in C:Program FilesSonyEverQuest IIEverQuest2.exe (0x00400000) 0x0012EC34: 0x00720067, in C:Program FilesSonyEverQuest IIEverQuest2.exe (0x00400000) 0x0012EC38: 0x006D0061, in C:Program FilesSonyEverQuest IIEverQuest2.exe (0x00400000) 0x0012EC3C: 0x00460020, in C:Program FilesSonyEverQuest IIEverQuest2.exe (0x00400000) 0x0012EC40: 0x006C0069, in C:Program FilesSonyEverQuest IIEverQuest2.exe (0x00400000) 0x0012EC44: 0x00730065, in C:Program FilesSonyEverQuest IIEverQuest2.exe (0x00400000) 0x0012EC48: 0x0053005C, in C:Program FilesSonyEverQuest IIEverQuest2.exe (0x00400000)End of Stack ScanEND OF LOG

thecynic315

09-26-2009, 06:09 PM

Having same problems, just crashed out myself. When EQ2 crashed and window closed my system monitor still showed EverQuest2.exe open and using over 1GB of RAM.Toon name and sever are in my Sig

Arianah

09-27-2009, 01:44 AM

I've been playing on High Quality for years now, and since the last GU I can't play in anything better than High Performance without crashing because of memory issues. My husband ran a bunch of updates for my computer, I just tried to go back to High Quality, and crashed again due to a memory issue. Either the new EXE didn't fix the problem or my computer needs to be replaced or something <img src="/eq2/images/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" />

Jayy

09-27-2009, 09:45 AM

I too am having the 'Application ran out of memory when requesting X amounts of bytes...' since the new LU <img src="/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" alt="SMILEY" /> I play with almost max Quality settings usually and i have even turned some settings down but still the same. As everyone else has also said, i never had these problems before and its really annoying! Cant play like this... When is there gonna be some sort of permanant fix?

Artaguss

09-27-2009, 10:28 AM

I guess there are 2 Threads on this...<a href="http://forums.station.sony.com/eq2/posts/list.m?topic_id=364955" target="_blank">http://forums.station.sony.com/eq2/...topic_id=364955</a>...watching to see whats next.

Collin_Rowanstaff

09-27-2009, 01:51 PM

Add me to the list of people getting first time out of memory issues since patch.

cr0wangel

09-27-2009, 03:08 PM

Do reinstalling the game may fix the problem? Because I consider moving away from EQ if the issue continue, really, the game close up each time I zone or so due out of memory bug and it seems there is no fix and a huge thread of 90 pages...

Qaeowin

09-27-2009, 03:38 PM

THIS REPEATED CRASHING IS EXTREMELY ANNOYING!!!!!!!!!!!!!!!!!!!

stayx

09-27-2009, 03:49 PM

Now i have the problem too, eq2 use 2gb of memory sorry but its too much...I have a screenshot from the isue and my second problem is the zoning is terrible it needs so much time now...<img src="http://img.xrmb2.net/images/832735.jpeg" width="419" height="159" />

Drevva

09-27-2009, 07:47 PM

Even after hotfix.Not crashing but still using way more memory than I did Pre GU53, I use to run two instances of game without issue (4GB, quad core) now things are hitchy slow, swapping memory , forget having anything else up (browser etc).Same issue on my second box, running one instance is much more hitchy, checked and using way more memory.I'm guessing the client is using 500MBish more than before GU53, taking a full 2GB now.Didn't really notice much improvement with the hot fix.

Lorriana

09-27-2009, 09:35 PM

Just adding that I am having the same issues. Before th GU, I had no issues with boxing. I was even able to tri-box for a bit. Now boxing is impossible. I have one instance of EQ2 taking as much as two gigs of memory. I only get crashes while boxing, but a single instance is using much more memory than before. Oh, and I noticed no change at all after the hotfix.

screenid

09-27-2009, 09:42 PM

Rothgar

09-27-2009, 10:10 PM

I just wanted to let you guys know we are still looking into the memory issues and will make the appropriate hotfix when we find the problem.

Jimako

09-27-2009, 10:18 PM

This is ridiculous. My game uses up to 2.7 gigs of memory. I have 4 Gig of memory. While it doesnt crash it thrashes my harddrive to the point the game is unplayable.How did this patch ever pass QA??<img src="http://img143.imageshack.us/img143/2770/capturei.png" />

Rothgar

09-27-2009, 10:38 PM

<cite>Jimako wrote:</cite><blockquote>This is ridiculous. My game uses up to 2.7 gigs of memory. I have 4 Gig of memory. While it doesnt crash it thrashes my harddrive to the point the game is unplayable.How did this patch ever pass QA??<img src="http://img143.imageshack.us/img143/2770/capturei.png" /></blockquote>It seems to be doing different things for different people. I'm playing right now on my home computer and the client is using 1.2gb of RAM. Thats still a lot, but obviously nowhere near the problem you're having. I've been raiding for about 2 hours now and i've been watching the memory usage. For me, its capping out around 1.2gb.So I'm not sure if the problem is worse depending on hardware, O/S or driver versions, but we will get to the bottom of it.I'm running in Windows 7 64bit at the moment. On my work machine, running XP, I haven't seen this problem either.We'll have our compatibility lab try to repro this on some different machines so we can get to the bottom of it.

tkia

09-27-2009, 11:52 PM

I've been getting this since the update too. I dropped my settings down from High Quality to High Performance and can now go 10 hours before it crashes instead of 2. I'm running on 32bit XPPro, 4GB of RAM with 1GB of RAM on the video card and have tried various settings of the 3GB switch, but it actually seems more stable not using the switch at all with my setup. I've also been playing on test a fair bit and over there it's perfectly stable for hours using my normal High Quality settings.

Jimako

09-27-2009, 11:59 PM

<cite>Rothgar wrote:</cite><blockquote><cite>Jimako wrote:</cite><blockquote>This is ridiculous. My game uses up to 2.7 gigs of memory. I have 4 Gig of memory. While it doesnt crash it thrashes my harddrive to the point the game is unplayable.How did this patch ever pass QA??<img src="http://img143.imageshack.us/img143/2770/capturei.png" /></blockquote>It seems to be doing different things for different people. I'm playing right now on my home computer and the client is using 1.2gb of RAM. Thats still a lot, but obviously nowhere near the problem you're having. I've been raiding for about 2 hours now and i've been watching the memory usage. For me, its capping out around 1.2gb.So I'm not sure if the problem is worse depending on hardware, O/S or driver versions, but we will get to the bottom of it.I'm running in Windows 7 64bit at the moment. On my work machine, running XP, I haven't seen this problem either.We'll have our compatibility lab try to repro this on some different machines so we can get to the bottom of it.</blockquote>Im running Windows 7 64-Bit myself. This has never been an issue in the past. I havent upgraded any kind of drivers at all in over 3 months. Now I have the problem every single time i run eq2

Wrapye

09-28-2009, 12:16 AM

I find it is very dependent on the video quality that I am running. I was raiding all night in 'High Performance' mode, and the worst it got was 1.4GB. Afterwards I changed it to 'High Quality' and it immediately jumped to 2.0GB.

Despak

09-28-2009, 03:15 AM

Do you folk want to try again on fixing this issue. You didn't actually fix anything with the last patch.

Guy De Alsace

09-28-2009, 05:08 AM

Win xp SP 2 (3 crashes my system) using a Radeon 512mb x1950pro on AGP, single core with 1.5GB internal. Believe it or not I used to be able to run 2 instances of EQ2 on it as well for 2 boxing. Now running one is tough.Playing on Balanced I got acceptable perfomance even in GH. Now gameplay is choppy after a few minutes. If I drop the performance to High Performance the game freezes sometimes for as long as 5 minutes while it swaps out files. This is on RE.

MrWolfie

09-28-2009, 07:47 AM

I'm seeing abnormally high ram usage, win xp sp3, custom settings, but probably close to what you'd say was high quality. I've had it crash to desktop once or twice, and become so slow that I just needed to turn it off (thanks for this bug during a bonus xp weekend btw <img src="/smilies/69934afc394145350659cd7add244ca9.gif" border="0" alt="SMILEY" />)My partner's PC suffered even worse, frequently hanging and crashing, even having the PC just reboot itself.Some of my observations:1. it's much worse with GPU shadows turned on. Especially in large zones like GF, where almost everything is in shadow.2. you're not going to see it much while raiding, you're technically just sitting in the same zone for hours. Try running around getting the discoveries that aren't in your Achievements. Lots of zoning seems to make the exe eat memory like crazy.3. on extreme performance I can run two instances of eq2 and they run consistently at around 700mb each.

Wrapye

09-28-2009, 08:09 AM

In my specific case yesterday, 'raiding' was pulling two avatars and running all of Palace. That was two different outside zones, one of which had horrendous lag (Everfrost).

Calismic

09-28-2009, 10:23 AM

Since you seem to feel it may be system dependent, I thought I'd toss my specs into the mix. The game eats up about 2.7GB of memory on high quality. Oddly enough if I go into WIndowed mode and then back to full screen I'll regain ~700MB of memory. I do this when the game starts to feel unstable and it will keep it from crashing.AMD 64 28004GB DDR2 533 Crucial MemoryGeforce 8800 GTS Latest driversWindows 7 Ultimate 64Bit

Fendaria

09-28-2009, 11:01 AM

Crashing since GU53 has just been horrible. I can't run on my old high graphics settings, I've had to start using my raid settings all the time now just to play.The GU came out and I ran around in South Qeynos to see the new house rooms. On my 3rd or 4th house, crash.My guildhall is a crashtrap now. Previously, I would crash in the guildhall, but only if I've been playing a while (2+ hours or off running an instance). Now I can't even do that. My framerate just dies in there easily too.Last night I was playing for about two hours on 'raid' quality. Decided to try for fun and see how quickly I could get the game to crash. Loaded up the high settings and crashed immediately. I didn't even get to move and the out of memory error popped up.Last night my second box crashed with the out of memory error. It hasn't had that problem for 6+ months. It just sits and lives at raid settings because the hardware isn't as good.I've even had voice chat crash two or three times now since the GU went live. Its been fine for months before this.I've been patient for the past year or so. I generally crash at least once a night. I've lived with it. I no longer go on a raid with just 'raid' graphics settings, I make sure I have started EQ2 without 'high' graphics settings at all to raid. I make sure I don't visit my guild hall before raids. I even try to make sure I don't visit the guild hall before I run TSO instances.I really like the game alot, but something has to be done.I heard you can pull crash logs from accounts, they are uploaded the next time you log in or something. Please look at mine! Please! I have to have lots of crash log goodness.I love the new shadows, they look great. The new shaders look good too. But this crashing has got to go. Put those other graphics issues on the backburner till this can get resolved please.Fendaria

cr0wangel

09-28-2009, 11:24 AM

<cite>Rothgar wrote:</cite><blockquote>I just wanted to let you guys know we are still looking into the memory issues and will make the appropriate hotfix when we find the problem. </blockquote>Thank you for looking into it, because right now it's unplayable. The more I zone, the more it eats memory until it crashes... I am on WinXP (service pack 2), shadows are off, voicechat is off.

Despak

09-28-2009, 11:28 AM

It is definately connected with zoning. After doing Raincaller and in the process of Magi's Craft (so lots of zoning) EQ2 is running at nearly 3gig!<img src="http://www.dcads.co.uk/eq2mem.gif" width="601" height="60" />

rsliv

09-28-2009, 11:39 AM

<cite>Rothgar wrote:</cite><blockquote>It seems to be doing different things for different people. I'm playing right now on my home computer and the client is using 1.2gb of RAM. Thats still a lot, but obviously nowhere near the problem you're having. I've been raiding for about 2 hours now and i've been watching the memory usage. For me, its capping out around 1.2gb.So I'm not sure if the problem is worse depending on hardware, O/S or driver versions, but we will get to the bottom of it.I'm running in Windows 7 64bit at the moment. On my work machine, running XP, I haven't seen this problem either.We'll have our compatibility lab try to repro this on some different machines so we can get to the bottom of it.</blockquote>Running on a 32bit WinXP with 3Gig of RAM EQ2 Test Client seems to max out around 1.2gb. That's running with Very High Performance settings. This machine has a GeForce 8600 Nvidia card with latest drivers (not beta drivers).Running on a 32bit Vista machine with 4Gig of RAM EQ2 Test Client goes to well over 2gb (close to 3gb). That's running with Very High Quality settings. This machine has a GeForce 250 Nvidia card with latest drivers (not beta drivers). Of note: It doesn't actually climb to over 2gb until I've been playing a while across multiple zones. It seems to get worse if I camp to character select and then go back in with a different character, due to this I have been camping all the way out to the desktop if I want to switch characters.I am using ProfitUI on both machines.

Jimako

09-28-2009, 11:44 AM

<cite>Calismic wrote:</cite><blockquote>Since you seem to feel it may be system dependent, I thought I'd toss my specs into the mix. The game eats up about 2.7GB of memory on high quality. Oddly enough if I go into WIndowed mode and then back to full screen I'll regain ~700MB of memory. I do this when the game starts to feel unstable and it will keep it from crashing.AMD 64 28004GB DDR2 533 Crucial MemoryGeforce 8800 GTS Latest driversWindows 7 Ultimate 64Bit</blockquote>No i dont believe its system dependent and i dont believe its a memory leak. I max out at 2.7gig of usage, it never creeps up any higher than that. I can reproduce this behavior every single time i play the game.Other threads relating to poor performance, bad frame rates, stuttering etc are all a result of this issue.For whatever reason GU53 allocates and needs *much* more RAM that any of the updates before it. Why? I have no idea.Im sorry SOE, but this is a dealbreaker to me. No game should ever need to allocate and use this much memory. Its rendered the game unplayable and i dont feel like i need to adjust my graphics options to try and minimize memory usage when i have a perfectly fine PCIn short, get this fixed. Make it a priority above *anything*

Tro

09-28-2009, 12:12 PM

Jeez cut them some slack.. They are well aware of the issue and I am sure are working diligently to fix it. I am getting alot of 5-7 second game freezes every 3-5 minutes.. It sucks I know but give them time to get it figured out.With all the different hardware configs out there.. it's prolly gonna be a intense effort to get it worked out.. I will just be patient and let them work it out.I kinda understand how this can make it past QA.. It seems that some folks are not affected by this and some are. I don't think the QA dept has each and very possible hardware config out there.. I am guessing millions of different H/W configs so give it some time.. I am sure they will get it fixed (Don't make a liar out of me plz... ok) ;- )

Jimako

09-28-2009, 12:28 PM

<cite>Talsmar@Crushbone wrote:</cite><blockquote>Jeez cut them some slack.. They are well aware of the issue and I am sure are working diligently to fix it. I am getting alot of 5-7 second game freezes every 3-5 minutes.. It sucks I know but give them time to get it figured out.With all the different hardware configs out there.. it's prolly gonna be a intense effort to get it worked out.. I will just be patient and let them work it out.I kinda understand how this can make it past QA.. It seems that some folks are not affected by this and some are. I don't think the QA dept has each and very possible hardware config out there.. I am guessing millions of different H/W configs so give it some time.. I am sure they will get it fixed (Don't make a liar out of me plz... ok) ;- )</blockquote>Uh , everyone is affected by this. People who run the game with higher performance options over higher quality wont notice it, but it still there. I play on a Intel Quad Core Q9550 with 4 gigs DDR2-800, BFG 9600 GT 512, Windows 7 64-Bit.My graphics settings are High Quality, however i turn shadows off and play at 1600x900.Steps to reproduce:- Log into game (1.2 gig used)- Port to guild hall (2.0 gig used)- Port to Kylong Plains (2.7 gig used)

Psyren

09-28-2009, 12:28 PM

Is there a reason why this client wasn't bug tested?

screenid

09-28-2009, 12:58 PM

Things to note... not sure if it helpsI play in windowed mode...-when I minimize eq2 it clears all memory allowing me to play a bit longer (however it climbs quickly) ...game seems to hover around 1.2 if I stay in one zone-if I zone 2 or 3 times the memory usage jumps drastically (and game crashes unless I minimize as stated above)-OS XP service pack 3

Tro

09-28-2009, 01:03 PM

<cite>Jimako wrote:</cite><blockquote><cite>Talsmar@Crushbone wrote:</cite><blockquote>Jeez cut them some slack.. They are well aware of the issue and I am sure are working diligently to fix it. I am getting alot of 5-7 second game freezes every 3-5 minutes.. It sucks I know but give them time to get it figured out.With all the different hardware configs out there.. it's prolly gonna be a intense effort to get it worked out.. I will just be patient and let them work it out.I kinda understand how this can make it past QA.. It seems that some folks are not affected by this and some are. I don't think the QA dept has each and very possible hardware config out there.. I am guessing millions of different H/W configs so give it some time.. I am sure they will get it fixed (Don't make a liar out of me plz... ok) ;- )</blockquote>Uh , everyone is affected by this. People who run the game with higher performance options over higher quality wont notice it, but it still there.I play on a Intel Quad Core Q9550 with 4 gigs DDR2-800, BFG 9600 GT 512, Windows 7 64-Bit.My graphics settings are High Quality, however i turn shadows off and play at 1600x900.Steps to reproduce:- Log into game (1.2 gig used)- Port to guild hall (2.0 gig used)- Port to Kylong Plains (2.7 gig used)</blockquote>I could have sworn Rothgar posted on Page 4 he wasn't seeing the problem on atleast one of his systems.. and I am sure there are some folks unaffected and they probably would not post here because well .. they are unaffected.If you honestly believe each and every individual playing is having this issue then you have your opinion. I think it is more likely a crap load of folks are but not everyone.. Could be wrong but don't think so..

Jimako

09-28-2009, 01:17 PM

<cite>Talsmar@Crushbone wrote:</cite><blockquote><cite>Jimako wrote:</cite><blockquote><cite>Talsmar@Crushbone wrote:</cite><blockquote>Jeez cut them some slack.. They are well aware of the issue and I am sure are working diligently to fix it. I am getting alot of 5-7 second game freezes every 3-5 minutes.. It sucks I know but give them time to get it figured out.With all the different hardware configs out there.. it's prolly gonna be a intense effort to get it worked out.. I will just be patient and let them work it out.I kinda understand how this can make it past QA.. It seems that some folks are not affected by this and some are. I don't think the QA dept has each and very possible hardware config out there.. I am guessing millions of different H/W configs so give it some time.. I am sure they will get it fixed (Don't make a liar out of me plz... ok) ;- )</blockquote>Uh , everyone is affected by this. People who run the game with higher performance options over higher quality wont notice it, but it still there.I play on a Intel Quad Core Q9550 with 4 gigs DDR2-800, BFG 9600 GT 512, Windows 7 64-Bit.My graphics settings are High Quality, however i turn shadows off and play at 1600x900.Steps to reproduce:- Log into game (1.2 gig used)- Port to guild hall (2.0 gig used)- Port to Kylong Plains (2.7 gig used)</blockquote>I could have sworn Rothgar posted on Page 4 he wasn't seeing the problem on atleast one of his systems.. and I am sure there are some folks unaffected and they probably would not post here because well .. they are unaffected.If you honestly believe each and every individual playing is having this issue then you have your opinion. I think it is more likely a crap load of folks are but not everyone.. Could be wrong but don't think so..</blockquote>I do, and im saying that because ive been a developer myself for 12 years. The client *itself* is responsible for allocating ram that the game needs. Everyone has the same client right? So what is the problem here? Hardware configurations mean nothing in the grand scheme of things. Rothgar claims that he doesnt have the problem on his work compuer, but he also doesnt tell us what graphics/other options he uses. Id be interested to see what his RAM usage is with the test scenario i posted above.And If i turn my settings down to the performance options over quality, the memory footprint decreases. Unfortunatly i cant compare it to a previous patchs usage. But it doesnt eliminate the fact that the memory footprint since this patch has grown much higher and needs to be addressed.Its a sad day when 4 gigs of RAM isnt enough to play games anymore, dont you think?

Tro

09-28-2009, 01:27 PM

<cite>Jimako wrote:</cite><blockquote><cite>Talsmar@Crushbone wrote:</cite><blockquote><cite>Jimako wrote:</cite><blockquote><cite>Talsmar@Crushbone wrote:</cite><blockquote>Jeez cut them some slack.. They are well aware of the issue and I am sure are working diligently to fix it. I am getting alot of 5-7 second game freezes every 3-5 minutes.. It sucks I know but give them time to get it figured out.With all the different hardware configs out there.. it's prolly gonna be a intense effort to get it worked out.. I will just be patient and let them work it out.I kinda understand how this can make it past QA.. It seems that some folks are not affected by this and some are. I don't think the QA dept has each and very possible hardware config out there.. I am guessing millions of different H/W configs so give it some time.. I am sure they will get it fixed (Don't make a liar out of me plz... ok) ;- )</blockquote>Uh , everyone is affected by this. People who run the game with higher performance options over higher quality wont notice it, but it still there.I play on a Intel Quad Core Q9550 with 4 gigs DDR2-800, BFG 9600 GT 512, Windows 7 64-Bit.My graphics settings are High Quality, however i turn shadows off and play at 1600x900.Steps to reproduce:- Log into game (1.2 gig used)- Port to guild hall (2.0 gig used)- Port to Kylong Plains (2.7 gig used)</blockquote>I could have sworn Rothgar posted on Page 4 he wasn't seeing the problem on atleast one of his systems.. and I am sure there are some folks unaffected and they probably would not post here because well .. they are unaffected.If you honestly believe each and every individual playing is having this issue then you have your opinion. I think it is more likely a crap load of folks are but not everyone.. Could be wrong but don't think so..</blockquote>I do, and im saying that because ive been a developer myself for 12 years. The client *itself* is responsible for allocating ram that the game needs. Everyone has the same client right? So what is the problem here? Hardware configurations mean nothing in the grand scheme of things.Rothgar claims that he doesnt have the problem on his work compuer, but he also doesnt tell us what graphics/other options he uses. Id be interested to see what his RAM usage is with the test scenario i posted above.And If i turn my settings down to the performance options over quality, the memory footprint decreases. Unfortunatly i cant compare it to a previous patchs usage. But it doesnt eliminate the fact that the memory footprint since this patch has grown much higher and needs to be addressed.Its a sad day when 4 gigs of RAM isnt enough to play games anymore, dont you think?</blockquote>Good point.. That obviously is why you were a dev and I am not lol... I still stay hopeful that the problem will be resolved hopefully sooner than later. Time will tell ..Later..

Giara

09-28-2009, 03:15 PM

Add me to this list...I just built my new system on Friday and noticed that I am experiencing the same issue with the game using way more memory than it should be. While raiding last night, I kept the task manager up to keep an eye on memory usage and noticed a slow creep from around 1.7 gigs to leveling out to 3.7 gigs of memory usage. I play with high graphics settings and built this system with the expectation of using high graphics. Major System specsIntel Core i7 860 2.80GHz, overclocked to 3.5GHzAsus P7P55D motherboard6 gigs DDR3 1333MHz ramNVidia GeForce GTX 260 896mb video

Glymmyr

09-28-2009, 07:51 PM

Add me to the list !!!Notice this more often in Neriak, can't even log my toon into that zone anymore, just deleted the toon and started over with a different Necro.Gorowyn, pretty bad there. Took me 5 crashes to walk from my house, use the portal down to lower level and walk outside, got tired of crashing and moved to yet another toon.Just for kicks, I made a new human bruiser, could not even log into starting island without a crash. Have not tried to log him back in, but things look bad for starting.It does not seem to matter if I reboot computer at all. This crash happens when I go into graphic heavy, shadowy zones, or zone multiple times to get someplace. Going from Freeport to Nek to Thundering Steppes to do a TS task was two crashes there and back.I have 8 gb of RAM, I know only 4gb is accessable without 64bit operations, but this memory leaking and crashing is making my $29.99 a month for Station Pass $29.99 a month for something I can only use about 50% of the time I want to use it.I am not the most savy computer person in the world, but if somebody needs any info from me and can give me a checklist of how to get the correct info to the Devs, I will be more than willing to post info to help solve this problem.Glymmyr.

vochore

09-28-2009, 09:48 PM

1 more to add to the list...i keept rivatuner running while playing tonight and recorded my cpu usage,pagefile,and system memory.adding both memory and pagefile together was over 6 gigs being used...somethings not rt here and it needs to get fixed.

Sarriss

09-28-2009, 10:25 PM

EQ actually got to the point where iy would not zone anymore. I was only using 68% of my system RAMVista 64 bitIntell i7 9206 GB DDR3 16000 RAMa bunch of other fluiff I'm too tired to put in here<img src="http://img193.imageshack.us/img193/3834/memorycrash.jpg" />

Mactosh

09-28-2009, 11:42 PM

3.25gb of ram being used on 1 client after playing for 3 hrs and crossing about 6 zones.

Kegofbud

09-29-2009, 01:26 AM

Same complaints as everyone else. Never had issues like this before, haven't changed anything.GeForce 8800 GTS: Driver version 190.38Windows XP 64 - fully patched4GB RAM PC6400Issues grow worse every time I zone until I evetually have to relog. Sometimes when I /exit, the game hangs until I use taskmanager to force it closed.

Kandey

09-29-2009, 01:06 PM

And to think I've been getting frustrated at the guy who built my new computer for me. I've had him running in circles describing the problem I've been having with these memory issues...Just had a new computer built and the only requirement I had for him was "stupid fast". Well, he really did that and I have been able to run EQ2 at all max settings, including shadows at 1920x1200 averaging 40fps. It really is a beautiful game to play...for the 5-10 minutes I get to actually play it. I crash to desktop every 3rd zoning or so. Sometimes even just standing in the guildhall.This is the error I get most of the time: Application ran out of memory when requesting 146416 bytes (limit: 2048 MB, current: 828 MB).My computer specs are as follows:Windows XP Professional 32 bit SP3 (current updates)Intel Pentium Dual-Core @4GhzNVidia GeForce 9800 GTX+ (current drivers)OCZ PC2 6400 4GB RAM (2x2GB)Drive 1: 150GB 10,000 RPM Raptor (EQ installed here)Drive 2: 300GB 7,200 RPMDrive 3: 300GB 7,200 RPM <span style="font-family: "Calibri","sans-serif"; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;">I can't think of what else it has in it or what might be important, but thats all I can think of at the moment. But now that I know I'm not alone and this is an EQ related problem, I can stop bugging my computer guy about it. <span style="font-family: "Calibri","sans-serif"; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;">Odd thing is, I can still use my 'old' computer and not get these problems at all and its just a generic Compaq Presario. I upgraded the memory (4GB), video card (ATI Radeon) and sound card, but other than that, straight out of the box as purchased from Best Buy about 3 yrs ago.

Krystara

09-29-2009, 04:10 PM

Spent all weekend crashing over and over - I'd have been really upset except that I knew a lot of other people were having the problem and it wasn't just me. I could play for an hour, maybe two and then I'd be popped into windowed mode and then crash to desktop with an "out of memory" error.What do you need from me to help you hunt this bug? I want it dead. I miss my smooth sailing EQ2 - I've never really had connection errors or lag before. Except for that time my router died, but then it was my entire network, not just the game.

Rothgar

09-29-2009, 07:04 PM

We've made another change to the client that should reduce the memory usage quite a bit. As soon as it has passed QA we'll get it hotfixed.

Sphiriah

09-29-2009, 07:19 PM

<cite>Rothgar wrote:</cite><blockquote>We've made another change to the client that should reduce the memory usage quite a bit. As soon as it has passed QA we'll get it hotfixed.</blockquote>I hope it's better than the last fix.>.>

Enever

09-29-2009, 10:10 PM

Anything is better then nothing.

EQAditu

09-30-2009, 01:59 AM

This seemed somewhat interesting to me...<img src="http://advancedcombattracker.com/personal/EQ2-MemError3.png" width="545" height="392" />Is this indicating that EQ2 thought it had 840MB of memory allocated by its own counts but in actuality had 1.3-1.7GB allocated at the time of the crash? I know it's late to report much until the release of the next promised "fix". But the talk about reducing memory usage seems strange when it exibits memory leaks. Personally, I only see memory leaking when I change zones. Staying in a zone, I'll always stay below 1GB no matter how long I stay there and how many times I die and have to respawn. The most sure way for me to crash is to zone into my guild hall, go some place else and repeat until it crashes. Take my guild hall out of the equasion and the problem is merely slower.

Guy De Alsace

09-30-2009, 04:15 AM

The game shows all the symptoms of a memory leak. Performance gets progressively worse over time until you get the out of memory crash.I have to avoid the GH like the plague at the moment. I hope a fix comes soon because as it stands the game is close to unplayable - at least for any length of time.

Inferius

09-30-2009, 04:55 AM

Yes it is unplayable for any length of time and incredibly annoying. My "Hotfix" has been not to bother logging in and playing Runes of Magic instead untill Eq2 is fixed. I get enough stress at work all day without having to deal with long load times and constant out of memory crashes. I almost did a fresh xp install believing i had some virus i couldnt get off my system the performance dropped so badly.Surely this must have been happening on the test server? I understand there other variables to consider but perhaps playtesting ought to be limited to those that actually report problems instead of "touring new content" just to get the edge when it goes live.Sorry guys,Rant finished!

Tro

09-30-2009, 08:42 AM

I don't seem to have any memory issues.. I raided last night for 4 hours and all went well. No game errors.When I played a couple years ago I read on these boards about a setting you can change that helps with memory leaks.It is a simple change and may help until things get fixed.. here it is (Win XP Sp-2):Start/My comp/right click-properties/advanced tabUnder "performance" select Settings/Advanced tabUnder Memory usage select "System Cache" vice "Programs"Give it a whirl.. If it doesn't help then just set it back to programs..

Guy De Alsace

09-30-2009, 09:12 AM

You're alright if you dont change zones I think. The more often you zone the quicker the game goes out-of-memory.

Inferius

09-30-2009, 10:29 AM

It's hardly fair to put us into that position though where a lot of poeple have to stay in one zone all night or crash.I just want to play the game lol!! pretty please fix it soon guys i'm struggling here.

hansomepete

09-30-2009, 10:48 AM

Sounds alot like what I have going on. I was getting some decent frame rates heck I hit 52 at one time I have never seen that. Went from Freeport to commonlnads and it diped to 28, then nek forest where it really lagged I got a steady 2 then eventually came back up to 15. Once I hit lavastorm it was just bad, I did hit 20's but in the middle of a solo shard run it crashed to desktop but this time no error message. I heard the windows beep, then the screen froze and I saw my desktop but with no windows background. Didn't get it back until I did a restart.Fix something that needs to be fixed, instead of messing with stuff that actualy works. Game ran fine until the last update. I'm a tad miffed, can't play a game anymore that use to work fine. I mean come on... I use to play for 4 to 5 hours now I'm lucky to get 20 minuets.

Kegofbud

09-30-2009, 10:27 PM

My memory sits at about 2.2GB used for the game after zoning some. I sometimes just crash to desktop shortly after logging in, during raids. It's annoying as hell.

Despak

10-01-2009, 02:51 AM

Well the hotfix is out and nothing for the memory problems! However, Nexona doesn't have a DPS cap anymore!!

Guy De Alsace

10-01-2009, 04:20 AM

Took me 20 minutes to get into the GH lol. Did CoGH, game crashed out of memory then was sat at "receiving zone info" for 10 minutes.At the moment the game is really shaky!At the moment its also difficult to tell if these unannounced hotfixes have got to EU yet. Mine did an update last night but whatever that was it didnt affect the memory problem.

Koava

10-01-2009, 12:19 PM

I have played EQ2 since launch and have had no real complaints (except for the original memory leak that was finally fixed a long time ago). There has always been a certain amount of lag and we put up with it. Some times I turn my quality down and performance up to have better play. My wife and I both play and we both have similar numers but very different machines. I have a duel core and she has a single core machine, we both run GeForce 9800 cards.As of late Wednesday night / early Thursday morning (Seattle PST) I have seen no hotfix that effects memory in any way. I am still "stutter lag stepping" when I walk around, I am still running at the same FPS, I still see huge lag freezes in areas with no other mobs npcs or players, and I still crash out to desktop (no wall paper just icons) due to memory problems. Note that even from this crashed out situation I have to ALT CTRL DEL to get to my Task Manager so I can force a re-boot as the machine is so screwed up I can't use the START button to do so.This morning in desperation I shut off all shadows. We will see how that plays out, but it does not seem much better.

MrWolfie

10-01-2009, 02:16 PM

CTD, splitpaw, 01/10/2009 18:09. One character, four zones entered: SF, LP, GF, LF. Here's the contents of the crashlog.txtbuild="SOEBuild=5916L" version="SOEVersionString=2009/9/24 17:56:49" build_type="USER OPTIMIZED" ls_address="none" zone="exp03_rgn_lesser_faydark" loc="-449.94 -37.98 -162.23" performance="7" stack="4fe4b48c 4fe62173 009d6199 009da52c 009db4ba 0090857b "

Artaguss

10-01-2009, 02:37 PM

Maybe a temp work-around, at least it has kept me playing...if anyone is interested.<a href="http://forums.station.sony.com/eq2/posts/list.m?start=1365&topic_id=364955" target="_blank">http://forums.station.sony.com/eq2/...topic_id=364955</a>I run in windowed mode and minimize or restore down/up as needed.Not the greatest way to keep playing, but it seems to help me.

TSR-KenC

10-01-2009, 03:11 PM

<cite>Artaguss wrote:</cite><blockquote>Maybe a temp work-around, at least it has kept me playing...if anyone is interested.<a href="http://forums.station.sony.com/eq2/posts/list.m?start=1365&topic_id=364955" target="_blank">http://forums.station.sony.com/eq2/...topic_id=364955</a>I run in windowed mode and minimize or restore down/up as needed.Not the greatest way to keep playing, but it seems to help me.</blockquote>True enough. Thanks for linking that particular work around. It's at least something until the final fix can be pushed and patched!

Jimako

10-01-2009, 03:42 PM

This is absurd.So let me understand this:A bug that affects everyone. That uses up to 2/3's of a users total memory, rendering the game unplayable, resulting in crashing/lagging/stuttering and frustration is ignored while another "hotfix" is released today.Apparently this is not a high enough priority for SOE devs to fix.

Rothgar

10-01-2009, 03:50 PM

<cite>Jimako wrote:</cite><blockquote>This is absurd.So let me understand this:A bug that affects everyone. That uses up to 2/3's of a users total memory, rendering the game unplayable, resulting in crashing/lagging/stuttering and frustration is ignored while another "hotfix" is released today.Apparently this is not a high enough priority for SOE devs to fix.</blockquote>We *do* have multiple people on team and while someone was working on the memory issue, other people were fixing other things. The complexity of the changes that led to the memory issue took more time to fix, and more time to QA. The memory problem was a result of something that we have been working on for months. Its not as easy as going in and flipping a switch to fix it.We've been converting the game engine to load many objects asynchronously and use the resource manager (which is multi-threaded) more heavily for other objects. This will allow us to increase performance of the game as well as support the new streaming client. I assure you that issues of this magnitude have our top priority. You just can't make assumptions based on a hotfix schedule as to what is really going on behind the scenes.

Jimako

10-01-2009, 04:16 PM

<cite>Rothgar wrote:</cite><blockquote><cite>Jimako wrote:</cite><blockquote>This is absurd.So let me understand this:A bug that affects everyone. That uses up to 2/3's of a users total memory, rendering the game unplayable, resulting in crashing/lagging/stuttering and frustration is ignored while another "hotfix" is released today.Apparently this is not a high enough priority for SOE devs to fix.</blockquote>We *do* have multiple people on team and while someone was working on the memory issue, other people were fixing other things. The complexity of the changes that led to the memory issue took more time to fix, and more time to QA. The memory problem was a result of something that we have been working on for months. Its not as easy as going in and flipping a switch to fix it.We've been converting the game engine to load many objects asynchronously and use the resource manager (which is multi-threaded) more heavily for other objects. This will allow us to increase performance of the game as well as support the new streaming client. I assure you that issues of this magnitude have our top priority. You just can't make assumptions based on a hotfix schedule as to what is really going on behind the scenes.</blockquote>Im not really concerned with what goes on behind the scenes. As mentioned previously, im a developer myself and I support my customer base just like every one else. I also know that my clients would not put up with something like this and nor should they. It should be a #1 priority to resolve and fix. Hotfixes and other such things should be put on hold. The fact that a hotfix was released today, without memory issue resolved, looks bad.Perception is reality and the perception to me is, you guys dont really seem to be to concerned about this issue.

Koava

10-01-2009, 04:59 PM

Rothgar, I think you can appreciate the frustration on the players part. Imagine if you sent your car to the dealership ... asked them for a major overhaul of the engine at 150k miles with no service significant service (no upgrades to the engine).So they call you back, from a different department and tell you that they changed the oil and fixed a dent ... no mention of how the overhaul was going. It would be un-nerving (trust me ... I know ... Ford had my Mustang for three weeks).What the players really want is just to know that a group of devs are working on the memory problem, that they are tasked specifically on that and that only, and that these guys are not working on Orc beer drinking animations. If they have not yet gotten any significant answers yet, we just want to know, we just want to get a little update on their progress.Then you can tell us ... oh and by the way the other groups are still working on Fae beer drinking animations (and such) ... as they really have no expertise in memory problems ... so there is little reason for them to stop work on their current issues.And they have a hot fix coming today for xyz.

Dasein

10-01-2009, 05:54 PM

<cite>Jimako wrote:</cite><blockquote><cite>Rothgar wrote:</cite><blockquote><cite>Jimako wrote:</cite><blockquote>This is absurd.So let me understand this:A bug that affects everyone. That uses up to 2/3's of a users total memory, rendering the game unplayable, resulting in crashing/lagging/stuttering and frustration is ignored while another "hotfix" is released today.Apparently this is not a high enough priority for SOE devs to fix.</blockquote>We *do* have multiple people on team and while someone was working on the memory issue, other people were fixing other things. The complexity of the changes that led to the memory issue took more time to fix, and more time to QA. The memory problem was a result of something that we have been working on for months. Its not as easy as going in and flipping a switch to fix it.We've been converting the game engine to load many objects asynchronously and use the resource manager (which is multi-threaded) more heavily for other objects. This will allow us to increase performance of the game as well as support the new streaming client. I assure you that issues of this magnitude have our top priority. You just can't make assumptions based on a hotfix schedule as to what is really going on behind the scenes.</blockquote>Im not really concerned with what goes on behind the scenes. As mentioned previously, im a developer myself and I support my customer base just like every one else. I also know that my clients would not put up with something like this and nor should they. It should be a #1 priority to resolve and fix. Hotfixes and other such things should be put on hold. The fact that a hotfix was released today, without memory issue resolved, looks bad.Perception is reality and the perception to me is, you guys dont really seem to be to concerned about this issue.</blockquote>How much would an itemization guy or an encounter designer be able to contribute to debugging a memory issue? Why should their work be put on hold because of an unrelated issue? The people who do things like item design and encounter scripting are not your programmers, they are developers, and so what you are proposing is akin to your entire company shutting down operations while one department sorts out an issue. Would you expect your accounting department to stop paying and collecting accounts because HR is having an issue?The reality is that different issues wil lbe resolved at different times, and there's no sense in delaying a fix ready for release because another issue is not fixed yet. This is doubly true when the fixes are coming from very different departments.

EQAditu

10-01-2009, 05:55 PM

<cite>Koava wrote:</cite><blockquote>{...}Then you can tell us ... oh and by the way the other groups are still working on Fae beer drinking animations (and such) ... as they really have no expertise in memory problems ... so there is little reason for them to stop work on their current issues.{...}</blockquote><cite>Jimako wrote:</cite><blockquote>Im not really concerned with what goes on behind the scenes. As mentioned previously, im a developer myself and I support my customer base just like every one else. I also know that my clients would not put up with something like this and nor should they. It should be a #1 priority to resolve and fix. Hotfixes and other such things should be put on hold. The fact that a hotfix was released today, without memory issue resolved, looks bad.Perception is reality and the perception to me is, you guys dont really seem to be to concerned about this issue.</blockquote>I think it should almost go without saying at this point that different developers have different abilities and they cannot help eachother just because one issue is more important or one dev has less to do.Personally I think perception should be damned if it's going to hold back other fixes that also affect players. Just because it is a number one issue with a group of people does not mean it is the only problem that exists or that it affects everyone equally. I would personally be angry if I heard that a hotfix that is ready to be released(and delayed two days I understand) would be held back because it didn't fix one specific problem and no other reason.

Jimako

10-01-2009, 06:17 PM

<cite>EQAditu wrote:</cite><blockquote><cite>Koava wrote:</cite><blockquote>{...}Then you can tell us ... oh and by the way the other groups are still working on Fae beer drinking animations (and such) ... as they really have no expertise in memory problems ... so there is little reason for them to stop work on their current issues.{...}</blockquote><cite>Jimako wrote:</cite><blockquote>Im not really concerned with what goes on behind the scenes. As mentioned previously, im a developer myself and I support my customer base just like every one else. I also know that my clients would not put up with something like this and nor should they. It should be a #1 priority to resolve and fix. Hotfixes and other such things should be put on hold. The fact that a hotfix was released today, without memory issue resolved, looks bad.Perception is reality and the perception to me is, you guys dont really seem to be to concerned about this issue.</blockquote>I think it should almost go without saying at this point that different developers have different abilities and they cannot help eachother just because one issue is more important or one dev has less to do.Personally I think perception should be damned if it's going to hold back other fixes that also affect players. Just because it is a number one issue with a group of people does not mean it is the only problem that exists or that it affects everyone equally. I would personally be angry if I heard that a hotfix that is ready to be released(and delayed two days I understand) would be held back because it didn't fix one specific problem and no other reason.</blockquote><div>Way to play it down.It doesnt affect a "group of players". It affects everyone. The other threads in this forum and in General Tech Support confirm as much.So anyway, if you are fine with a bloated, memory hog of an client eating up all of your ram, lag, crashing, out of memory exceptions then thats fine. Enjoy your game.</div>

Tallisman

10-01-2009, 08:08 PM

OK, to add a bit of constructiveness to the thread, post the 5932L build, I've crashed again. This time, I'm on an alt, in his two bed inn room and trying to change from an "extreme performance" profile to an "extreme quality" one. I get oodles of disk thrashing then a crash - here's the log:SOEBuild=5932LSOEVersionString=2009/9/29 18:19:07EVERQUEST2 CRASH LOG=============================================== ================================================== =Unhandled exception EXCEPTION_ACCESS_VIOLATION at 0x4FE4B47CApplication was trying to read from 0x00000000 Region Begins At: 0x00000000 Region Ends At: 0x00010000 Region Size Is: 0x00010000 bytes Memory Protection: PAGE_NOACCESS (00000001) Memory State: MEM_FREE Memory Type: FreeGame Data: SOEBuild: SOEBuild=5932L SOEVersionString: SOEVersionString=2009/9/29 18:19:07 OS Version: 5.1.2600 Service Pack 2 VER_NT_WORKSTATION CPU: 2 x86 GenuineIntel 2938MHz RDTSC MSR CMPXCHG8 SSE SSE2 DirectX Version: 9.0c Video Card/Driver: [NVIDIA GeForce GTX 260] [nv4_disp.dll] 6.14.11.7813 {d7b71e3e-46a2-11cf-b76b-9b0300c2cb35} Time at crash: Thu Oct 01 23:58:42 2009 Login Server: none Performance: 7 Game Uptime: 4126 seconds Position last frame: -6.21, 1.80, -0.20 Zone name: qey_ph_1r01 Time in Zone: 154 seconds Previous Zone name: GameScene::ZR_NETWORKED_ZONE_CHANGE Multi-core support: disabled Low-Memory Mode: disabledLog: <ALERT> E:liveeq2frameworkrendersrcRenderContext.cpp(1777) : Error loading texture "cooked/characters/accessories/wieldable_items/weapons/talisman/wand/sourceimages/wand001_plain_tex.dds" <ALERT> E:liveeq2frameworkrendersrcRenderContext.cpp(1777) : Error loading texture "cooked/characters/creatures/mounts/rhino_mount/sourceimages/rhino_mount_armor_c.dds" <ALERT> E:liveeq2frameworkrendersrcRenderContext.cpp(1777) : Error loading texture "cooked/characters/creatures/mounts/rhino_mount/sourceimages/rhino_mount_armor_tint.dds" Failed to expand a clut <ALERT> E:liveeq2frameworkrendersrcRenderContext.cpp(1777) : Error loading texture "cooked/characters/accessories/wieldable_items/weapons/talisman/wand/sourceimages/wand001_plain_b.dds" <ALERT> E:liveeq2frameworkrendersrcRenderContext.cpp(1777) : Error loading texture "cooked/characters/accessories/wearable_items/cloak/exp06/sourceimages/cloak_arachnid_color.dds" Failed to expand a clut <ALERT> E:liveeq2frameworkrendersrcRenderContext.cpp(1777) : Error loading texture "cooked/characters/accessories/wearable_items/cloak/exp06/sourceimages/cloak_arachnid_spec.dds" <ALERT> E:liveeq2frameworkrendersrcRenderContext.cpp(1777) : Error loading texture "cooked/characters/accessories/wearable_items/cloak/exp06/sourceimages/cloak_arachnid_normal.dds" <MEMORY> E:liveeq2frameworkmemoryManagersrcsharedMemoryMana ger.cpp(2010): Application ran out of memory when requesting 2097184 bytes (limit: 1535 MB, current: 820 MB)Thread Data: Primary Thread Id: 3940 Current Thread Id: 3940 Current Thread Priority: 0Memory: AddressLimitMB: 2048 Load: 98% Total physical: 2146480128 Free physical: 37150720 Total pagefile: 4134952960 Free pagefile: 1553973248 Total virtual: 2147352576 Free virtual: 27820032Memory Manager: Allocations: 231994 Bytes Allocated: 551484768 Max Allocations: 377694 Max Bytes Allocated: 856123472 System Memory Allocated (MB): 820 Limit: 1535 Number of Allocate Calls: 9427189 Number of Free Calls: 9195195

Dasein

10-01-2009, 09:07 PM

<cite>Jimako wrote:</cite><blockquote><cite>EQAditu wrote:</cite><blockquote><cite>Koava wrote:</cite><blockquote>{...}Then you can tell us ... oh and by the way the other groups are still working on Fae beer drinking animations (and such) ... as they really have no expertise in memory problems ... so there is little reason for them to stop work on their current issues.{...}</blockquote><cite>Jimako wrote:</cite><blockquote>Im not really concerned with what goes on behind the scenes. As mentioned previously, im a developer myself and I support my customer base just like every one else. I also know that my clients would not put up with something like this and nor should they. It should be a #1 priority to resolve and fix. Hotfixes and other such things should be put on hold. The fact that a hotfix was released today, without memory issue resolved, looks bad.Perception is reality and the perception to me is, you guys dont really seem to be to concerned about this issue.</blockquote>I think it should almost go without saying at this point that different developers have different abilities and they cannot help eachother just because one issue is more important or one dev has less to do.Personally I think perception should be damned if it's going to hold back other fixes that also affect players. Just because it is a number one issue with a group of people does not mean it is the only problem that exists or that it affects everyone equally. I would personally be angry if I heard that a hotfix that is ready to be released(and delayed two days I understand) would be held back because it didn't fix one specific problem and no other reason.</blockquote><div>Way to play it down.It doesnt affect a "group of players". It affects everyone. The other threads in this forum and in General Tech Support confirm as much.So anyway, if you are fine with a bloated, memory hog of an client eating up all of your ram, lag, crashing, out of memory exceptions then thats fine. Enjoy your game.</div></blockquote>Of course I'm not hapy about it, but I am also aware that a non-programmer won't be of much help fixing this bug, but could still make useful updates to the game (like improving items for the new raid zone) and there's no sense in delaying a fix for one issue because fixes for another issue aren't ready yet.

EQAditu

10-01-2009, 09:18 PM

<cite>Jimako wrote:</cite><blockquote><cite>EQAditu wrote:</cite><blockquote>{...}Just because it is a number one issue with a group of people does not mean it is the only problem that exists or that it affects everyone equally.{...}</blockquote><div>Way to play it down.It doesnt affect a "group of players". It affects everyone.{...}</div></blockquote>I would ask that you do not reword my replys to mean something different just because you are angry. I said number one issue for a group a players and somehow you read that to mean something else. There are actually only a few in my guild that have a severe version of this problem, thus it may not be their number one issue.

Rothgar

10-01-2009, 11:10 PM

I wanted to give you an update on this issue so you know exactly where we are.We made some changes to the client a couple of days ago to reduce the memory requirements. Some of the changes were optimizations and some of them were re-thinking changes we made previously. A client that had previously been using about 1.3gb of RAM after zoning through about 6-8 zones was down to using only 800mb. We also tested this in a fully loaded guild hall and saw similar results.We were not able to reproduce an out-of-memory crash on any of our QA machines though. Fortunately, a player PM'd me a DXDiag and options file from a computer where they could regularly crash after about 30 minutes. We had our compatibility lab build an identical machine based on his DXDiag and using his options file were finally able to reproduce the crash on another machine. When they tested our new changes with this machine, the crash went away, so it looks like our memory changes have addressed the problem. The downside is that we still only have one crash to measure this against, so there is always the possibility that problems could occur on other system configurations but hopefully not.During our QA testing, they noticed some rendering artifacts after lots of zoning with character textures rendering incorrectly. So this is when we come to a fork in the road where we have to decide if we are going to push the fix out to correct the crash but possibly introduce another bug, or hold the fix until we can find the rendering issue.QA is currently doing more testing to see if they can repro the rendering problem with regularity. If they can, we will look into it to see if we can fix the problem quickly. If not, I'm still tempted to push this fix out since the crash issue is much more major than a rare rendering problem. Unfortunately its hard to determine if something that is rare for us in the labs might not be more common for the entire playerbase.As it is now, we would not be able to hotfix until Tuesday at the earliest. This gives us another day to try to fix the rendering problem. If we cannot get a repro or fix for it in another day, we'll probably hotfix the memory issue on Tuesday anyway.We also plan on pushing this update to the test server today. In fact, it might already be done, I'll have to check with our build manager. So it will be nice to hear if the test community runs into any rendering problems over the weekend, and if the crash problem goes away for them.Thanks for being patient. It really is a top priority for us and we're working as fast as we can to resolve it.

Lortet

10-01-2009, 11:53 PM

Thx for the update Rothgar - you may have seen some threads in the General Problem tech forum in which it might be appropriate to post your information as well.The rendering issue - it would be good to know how this presents, as the work-around suggested by one poster to minimise eq2 every so often to remove the increased memory load will produce rendering issues on my PC - in that after a few times, NPC's don't render properly - appearing white until you get really near them. Certain tree models appear as huge white snowflakes as well - the larger trees near qeynos in Antonica being good examples. This might suggest that the rendering issue you have detected may actually be hiding within the current files anyway.

Rothgar

10-02-2009, 12:25 AM

<cite>Hykaree@Runnyeye wrote:</cite><blockquote>Thx for the update Rothgar - you may have seen some threads in the General Problem tech forum in which it might be appropriate to post your information as well.The rendering issue - it would be good to know how this presents, as the work-around suggested by one poster to minimise eq2 every so often to remove the increased memory load will produce rendering issues on my PC - in that after a few times, NPC's don't render properly - appearing white until you get really near them. Certain tree models appear as huge white snowflakes as well - the larger trees near qeynos in Antonica being good examples. This might suggest that the rendering issue you have detected may actually be hiding within the current files anyway.</blockquote>Yes, that's exactly what they are seeing, NPC's rendering as white. I guess the good news is if that's already in the game then we won't be introducing it with the memory fix. We'll begin looking into that problem as well.

Arianah

10-02-2009, 12:47 AM

<cite>EQAditu wrote:</cite><blockquote><cite>Jimako wrote:</cite><blockquote><cite>EQAditu wrote:</cite><blockquote>{...}Just because it is a number one issue with a group of people does not mean it is the only problem that exists or that it affects everyone equally.{...}</blockquote><div>Way to play it down.It doesnt affect a "group of players". It affects everyone.{...}</div></blockquote>I would ask that you do not reword my replys to mean something different just because you are angry. I said number one issue for a group a players and somehow you read that to mean something else. There are actually only a few in my guild that have a severe version of this problem, thus it may not be their number one issue.</blockquote>Ditto. I am the only one in my guild having this problem. None of my friends are having the problem either. Not that I don't want this to get fixed! My husband bought me another 2gb of memory, so now I can play on Very High Quality, once the memory issue is fixed <img src="/smilies/8a80c6485cd926be453217d59a84a888.gif" border="0" alt="SMILEY" /> <img src="/smilies/283a16da79f3aa23fe1025c96295f04f.gif" border="0" alt="SMILEY" />

Morghus

10-02-2009, 03:35 AM

Well, I gave the test client a whirl, it is currently labeled as 5935t. When I first booted up it was at a rather low 680 mb of memory used. However, that does nothing to alleviate issues from staying logged in and zoning repeatedly. Each time I zoned it would still accumulate more memory (slightly less than live I suppose) but in the end it still fails to release the memory when I leave a zone, and character models, even low detail character models continue to remain loaded into the game's memory after zoning.Just as on live, as long as you confine yourself to one zone the memory usage will not likely be too great and will more or less remain somewhat static with slight drops every now and then but once you start zoning or moving towards more players/objects again the memory simply accumulates and fails to release, and the memory loaded by seeing characters/objects inside of a zone also fails to release even after they or yourself have long since left the general area.Zoning from one zone, and then quickly zoning back into the previous zone for example keeps the new zone's data loaded and open, the good thing though is the data usage does not appear to re-add itself to the memory from re-entering the same zone. However, the moment a new player enters the immediate vicinity they are added to the memory and dont tend to get released.The best thing I can think of is for an added setting to load only placeholder characters which would all use the same model thus only need to be loaded once, while at the same time lowering the minimum amount of low detail characters able to be displayed as those too eat memory when there are many of them.Also some form of compression for the textures overall if they are not already compressed would be good as well as perhaps skimping on un-needed polygons when designing objects could help. Fixing it so that characters/zone data and world objects are unloaded upon zoning though would also be a solution.Overall though, the memory usage will never return to the level it is at upon start-up and you will always eventually have to either re-load the game or crash. On test currently the process leading to crashing via memory overload seems to be greatly restrained, but the memory in-take is still there although somewhat smaller and can be noticed as zonign starts to take longer.It will be great for the main pc I play on which has rather few memory issues if ever, but my other pc has always appeared to have its memory eaten by eq2 much faster than the main one I use and the benefit to that computer may be questionable.Both computers are on windows xp sp3 2.66ghz duo core, Nvidia video cards both with 512 mb memory and 4gb of ddr2 ram. At this rate though, it will still take awhile for the game to ever run acceptably even on the recommended or minimum settings originally on the box.

Inferius

10-02-2009, 05:07 AM

Thanks for taking the time to update us Rothgar hopefully the fix will be a success.I cant wait to play my fave mmo again <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" />.

Akaran2

10-02-2009, 06:56 AM

Rothgar, I don't care what you do or how you do it. Patch something. If the npcs render as white, that's fine. If they render as pink flaming flamingos, it just gives me sometihng new to put my axe into.I went into some ugly debt upgrading to a system that should be able to play EQ2 at High Quality with two different clients going at once. I can play everything else I own without so much as a twitch. But EQ? It's bad enough that my Raedeon Sapphire 4850 doesn't like it and randomly pulls me into crashmode.But going LD 5-7 times a day? Just randomly getting maybe not just one, but three out of memory errors AT ONCE?I know I'm venting. I'm sorry. I know you're doing all you can do. But please mate, please oh please.I can PM DX Diag info. I can PM server info, account info, guild hall info (oh it so does not like my GH). Just tell me what you need and how you need it. For the record...Windows 7 RC.Raedeon Sapphire 4850 1g DDR33 gig ram (DDR 2 or 3, I forget)Quad Core.Fix me. <img src="/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" alt="SMILEY" />

Tro

10-02-2009, 08:14 AM

<cite>Talsmar@Crushbone wrote:</cite><blockquote>I don't seem to have any memory issues.. I raided last night for 4 hours and all went well. No game errors.When I played a couple years ago I read on these boards about a setting you can change that helps with memory leaks.It is a simple change and may help until things get fixed.. here it is (Win XP Sp-2):Start/My comp/right click-properties/advanced tabUnder "performance" select Settings/Advanced tabUnder Memory usage select "System Cache" vice "Programs"Give it a whirl.. If it doesn't help then just set it back to programs..</blockquote>Has anyone tried this? To add to this, My client has never received a memory crash with GU 53. I always keep the setting above even when I reload the OS I still set this to System Cache. My wife and I both have essentially the same system (Different video cards and PSU but everything else is the same) and she has not had a memory crash since Gu 53 came out either.The above setting is just a suggestion but again we have not had a memory crash with GU 53.

Ebarel

10-02-2009, 09:06 AM

<cite>Rothgar wrote:</cite><blockquote>I wanted to give you an update on this issue so you know exactly where we are.We made some changes to the client a couple of days ago to reduce the memory requirements. Some of the changes were optimizations and some of them were re-thinking changes we made previously. A client that had previously been using about 1.3gb of RAM after zoning through about 6-8 zones was down to using only 800mb. We also tested this in a fully loaded guild hall and saw similar results.We were not able to reproduce an out-of-memory crash on any of our QA machines though. Fortunately, a player PM'd me a DXDiag and options file from a computer where they could regularly crash after about 30 minutes. We had our compatibility lab build an identical machine based on his DXDiag and using his options file were finally able to reproduce the crash on another machine. When they tested our new changes with this machine, the crash went away, so it looks like our memory changes have addressed the problem. The downside is that we still only have one crash to measure this against, so there is always the possibility that problems could occur on other system configurations but hopefully not.During our QA testing, they noticed some rendering artifacts after lots of zoning with character textures rendering incorrectly. So this is when we come to a fork in the road where we have to decide if we are going to push the fix out to correct the crash but possibly introduce another bug, or hold the fix until we can find the rendering issue.QA is currently doing more testing to see if they can repro the rendering problem with regularity. If they can, we will look into it to see if we can fix the problem quickly. If not, I'm still tempted to push this fix out since the crash issue is much more major than a rare rendering problem. Unfortunately its hard to determine if something that is rare for us in the labs might not be more common for the entire playerbase.As it is now, we would not be able to hotfix until Tuesday at the earliest. This gives us another day to try to fix the rendering problem. If we cannot get a repro or fix for it in another day, we'll probably hotfix the memory issue on Tuesday anyway.We also plan on pushing this update to the test server today. In fact, it might already be done, I'll have to check with our build manager. So it will be nice to hear if the test community runs into any rendering problems over the weekend, and if the crash problem goes away for them.Thanks for being patient. It really is a top priority for us and we're working as fast as we can to resolve it.</blockquote>First of all, really thanks for your feedback in this thread. It may not be the solution to the crash problem but at least - and that is highly appreciated - you are talking to us, updating, giving specific replies (not the usual: we are looking into it). This is (for me) some of the best examples for communication/information on an otherwise annoying issue in a while.1) this issue is really annoying most of the playerbase, especially after an GU when you want to raid new content and now half of the raidforce has crit error issues. after every zoning you lose 6/24 players, during almost every longer/boss fight at least 1-2 people crash (if its MT or MT Healer, just try again after rezz...). So even if only half or bit less of the players are directly affected, it hurts the other ones just as well2) this is not a GU53 only issue. it got worse (as you can see from the 100 page thread) GU after GU. I myself never had any crash issue until iirc GU 50 or 51. after that things got worse. with every GU things go worse for more players.3) if you need infos, just let us know (but that 100page thread doesnt seem to be effective) just let us know what you need. i will fedex my main PC (or any of the 4, at your choice) from Europe to you if that helps to fix that stuff. i will send logs, files, images, whatever you need to fix it, just let us know what you need. you can log into my acc anytime during a raid (or zoning there) to try yourself.4) what looks obvious to me is that almost every crash log showsLog: E:liveeq2frameworkrendersrcRenderContext.cpp(1777) : Error loading texture "cooked/characters/accessories/wieldable_items/weapons/talisman/wand/sourceimages/wand001_plain_tex.dds" E:liveeq2frameworkrendersrcRenderContext.cpp(1777) : Error loading texture "cooked/characters/creatures/mounts/rhino_mount/sourceimages/rhino_mount_armor_c.dds" E:liveeq2frameworkrendersrcRenderContext.cpp(1777) : Error loading texture "cooked/characters/creatures/mounts/rhino_mount/sourceimages/rhino_mount_armor_tint.dds" Failed to expand a clut E:liveeq2frameworkrendersrcRenderContext.cpp(1777) : Error loading texture "cooked/characters/accessories/wieldable_items/weapons/talisman/wand/sourceimages/wand001_plain_b.dds" E:liveeq2frameworkrendersrcRenderContext.cpp(1777) : Error loading texture "cooked/characters/accessories/wearable_items/cloak/exp06/sourceimages/cloak_arachnid_color.dds" Failed to expand a clut E:liveeq2frameworkrendersrcRenderContext.cpp(1777) : Error loading texture "cooked/characters/accessories/wearable_items/cloak/exp06/sourceimages/cloak_arachnid_spec.dds" E:liveeq2frameworkrendersrcRenderContext.cpp(1777) : Error loading texture "cooked/characters/accessories/wearable_items/cloak/exp06/sourceimages/cloak_arachnid_normal.dds" E:liveeq2frameworkmemoryManagersrcsharedMemoryMana ger.cpp(2010): Application ran out of memory when requesting 2097184 bytes (limit: 1535 MB, current: 820 MB)a link to E:live...... for me this is my DVD-Rom drive. that path doesnt exist. for some that may be a HD or even not a valid drive at all. is the game accessing something that just doesnt exist and that causes the crash? the path mentioned there just doesnt exist. i have no clue wheather that is the cause or the result of the crit error but maybe take a look at that.*sorry for errors, English is not my native language*

Galldora

10-02-2009, 09:36 AM

Rothgar, I really appreciate your detailed explanation about what is being done to fix this most vexing problem. Thanks for keeping us informed! /smooch<cite>Talsmar@Crushbone wrote:</cite><blockquote><cite>Talsmar@Crushbone wrote:</cite><blockquote>I don't seem to have any memory issues.. I raided last night for 4 hours and all went well. No game errors.When I played a couple years ago I read on these boards about a setting you can change that helps with memory leaks.It is a simple change and may help until things get fixed.. here it is (Win XP Sp-2):Start/My comp/right click-properties/advanced tabUnder "performance" select Settings/Advanced tabUnder Memory usage select "System Cache" vice "Programs"Give it a whirl.. If it doesn't help then just set it back to programs..</blockquote>Has anyone tried this? To add to this, My client has never received a memory crash with GU 53. I always keep the setting above even when I reload the OS I still set this to System Cache. My wife and I both have essentially the same system (Different video cards and PSU but everything else is the same) and she has not had a memory crash since Gu 53 came out either.The above setting is just a suggestion but again we have not had a memory crash with GU 53.</blockquote>Talsmar, I've tried your suggestion, and yes, this does seem to work for me. Thanks!! /smooch for you, too! (must be in a kissy mood today <img src="/eq2/images/smilies/8a80c6485cd926be453217d59a84a888.gif" border="0" /> )I just changed my settings to favor system, then watched memory usage while a character zoned in and out of our fully-loaded guild hall several times. What I saw happening, which I hadn't seen before, is that the numbers will climb pretty high, but they drop periodically as well, preventing a crash. I'm going to make this change on my other machine, too. Funny thing is, I looked at that setting the other day and thought about changing it, but then thought it was better to favor programs than system cache -- backward thinking there!I haven't been having crashes as long as I remember to minimize frequently -- and I haven't noticed rendering problems popping up when doing this either, but apparently others haven't been so lucky using that little workaround -- but I'd sure rather not have to bother with it.

cr0wangel

10-02-2009, 11:12 AM

Thank you for giving us news, I will look forward for the fix Tuesday... Anyone playing on Test this weekend to confirm if the fix remove the bug for them?

Koava

10-02-2009, 12:12 PM

Rothgar !!!!Thank you so much for the update. This is exactly what you guys said at Gamefaire would be the norm ... an open dialog with the players ... and here we are. Just a little communication from the guys at SoE goes such a long way towards soothing the players, they really do love your world and when their favorite Avatar can't easily navigate its pathways they (myself included) get very frustrated.When I get home later today I will PM you my and my wifes system DXDialong info. I have a duel care box and she has a higher mghz single core box. Oddly, she can have two clients open and duel box EQ2, though I play with lass lag. We both run XP SP3 and both have the same GeForce 9800 video cards. We have both been seeing the same "stutter lag mem crash" problems.The other odd thing for me is that minimizing to windowed mode does not fix my memory problems. More often then not just swapping to windows mode increases the mem usage and drives me faster to a "crash to desktop" so I try to avoid swapping in and out and I have no programs running in the background.We play on Crushbone (where our whole guild has stopped raiding due to mem problems) Grimmond / Neleah.Thanks

Rageincarnate

10-02-2009, 01:17 PM

i admit i didnt read much of any of this thread but is this going to fix the no pants mobs too? lol, really wish i took screenshots.

Ebarel

10-02-2009, 01:38 PM

one more thing i can see on my system monitor.sitting in the GH doing nothing at all you can watch the used memory just go up - sometimes slower, sometimes quicker. it goes up in steps of 4/8/12/20 kb most of the time. sometimes big jumps in the thousands. it never goes down though, except when you send window to taskbar and back. that should explain why there are frequent oom errors on people just doing nothing. the only change i can see is chat. no people logging in or moving in the visible area, still slowly going up. from start of this post to now something around 30.000k from 498.000k to 530.000k now at the end.try opening task manager, watch memory usage in processes creep up slowly until you crash.

Tro

10-02-2009, 03:21 PM

<cite>Galldora wrote:</cite><blockquote>Rothgar, I really appreciate your detailed explanation about what is being done to fix this most vexing problem. Thanks for keeping us informed! /smooch<cite>Talsmar@Crushbone wrote:</cite><blockquote><cite>Talsmar@Crushbone wrote:</cite><blockquote>I don't seem to have any memory issues.. I raided last night for 4 hours and all went well. No game errors.When I played a couple years ago I read on these boards about a setting you can change that helps with memory leaks.It is a simple change and may help until things get fixed.. here it is (Win XP Sp-2):Start/My comp/right click-properties/advanced tabUnder "performance" select Settings/Advanced tabUnder Memory usage select "System Cache" vice "Programs"Give it a whirl.. If it doesn't help then just set it back to programs..</blockquote>Has anyone tried this? To add to this, My client has never received a memory crash with GU 53. I always keep the setting above even when I reload the OS I still set this to System Cache. My wife and I both have essentially the same system (Different video cards and PSU but everything else is the same) and she has not had a memory crash since Gu 53 came out either.The above setting is just a suggestion but again we have not had a memory crash with GU 53.</blockquote>Talsmar, I've tried your suggestion, and yes, this does seem to work for me. Thanks!! /smooch for you, too! (must be in a kissy mood today <img src="/eq2/images/smilies/8a80c6485cd926be453217d59a84a888.gif" border="0" /> )I just changed my settings to favor system, then watched memory usage while a character zoned in and out of our fully-loaded guild hall several times. What I saw happening, which I hadn't seen before, is that the numbers will climb pretty high, but they drop periodically as well, preventing a crash. I'm going to make this change on my other machine, too. Funny thing is, I looked at that setting the other day and thought about changing it, but then thought it was better to favor programs than system cache -- backward thinking there!I haven't been having crashes as long as I remember to minimize frequently -- and I haven't noticed rendering problems popping up when doing this either, but apparently others haven't been so lucky using that little workaround -- but I'd sure rather not have to bother with it.</blockquote>No Problem.. Glad it helped. <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" />

Kegofbud

10-02-2009, 05:56 PM

<cite>Talsmar@Crushbone wrote:</cite><blockquote><cite>Galldora wrote:</cite><blockquote>Rothgar, I really appreciate your detailed explanation about what is being done to fix this most vexing problem. Thanks for keeping us informed! /smooch<cite>Talsmar@Crushbone wrote:</cite><blockquote><cite>Talsmar@Crushbone wrote:</cite><blockquote>I don't seem to have any memory issues.. I raided last night for 4 hours and all went well. No game errors.When I played a couple years ago I read on these boards about a setting you can change that helps with memory leaks.It is a simple change and may help until things get fixed.. here it is (Win XP Sp-2):Start/My comp/right click-properties/advanced tabUnder "performance" select Settings/Advanced tabUnder Memory usage select "System Cache" vice "Programs"Give it a whirl.. If it doesn't help then just set it back to programs..</blockquote>Has anyone tried this? To add to this, My client has never received a memory crash with GU 53. I always keep the setting above even when I reload the OS I still set this to System Cache. My wife and I both have essentially the same system (Different video cards and PSU but everything else is the same) and she has not had a memory crash since Gu 53 came out either.The above setting is just a suggestion but again we have not had a memory crash with GU 53.</blockquote>Talsmar, I've tried your suggestion, and yes, this does seem to work for me. Thanks!! /smooch for you, too! (must be in a kissy mood today <img src="/eq2/images/smilies/8a80c6485cd926be453217d59a84a888.gif" border="0" /> )I just changed my settings to favor system, then watched memory usage while a character zoned in and out of our fully-loaded guild hall several times. What I saw happening, which I hadn't seen before, is that the numbers will climb pretty high, but they drop periodically as well, preventing a crash. I'm going to make this change on my other machine, too. Funny thing is, I looked at that setting the other day and thought about changing it, but then thought it was better to favor programs than system cache -- backward thinking there!I haven't been having crashes as long as I remember to minimize frequently -- and I haven't noticed rendering problems popping up when doing this either, but apparently others haven't been so lucky using that little workaround -- but I'd sure rather not have to bother with it.</blockquote>No Problem.. Glad it helped. <img src="/eq2/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" /></blockquote>Typically, for many programs, this isn't really a good change to make. It may help with the issues you are having in this game, but it's something that would seem to be an unintended help. It won't cause any real harm and most people will be able to toggle back and forth to try it out, but they should read up more on the setting. Changing this setting to try to help this game issue can negatively effect performace of several other things.<a rel="nofollow" href="http://support.microsoft.com/kb/895932" target="_blank">http://support.microsoft.com/kb/895932</a>

Rothgar

10-02-2009, 10:34 PM

Status Update:Unfortunately the last round of memory changes we made did not fix the problem. It may keep the problem from occuring on many of your systems by reducing memory usage, so in that respect, its still a good change. However, we've still been able to reproduce the crash under certain settings.So, our plan is to continue to push the memory changes we've made to live and hopefully that will fix or mitigate the problem for many of you. But we are still continuing to look into the crash issue.

Faymar

10-02-2009, 10:54 PM

<cite>Rothgar wrote:</cite><blockquote>Status Update:Unfortunately the last round of memory changes we made did not fix the problem. It may keep the problem from occuring on many of your systems by reducing memory usage, so in that respect, its still a good change. However, we've still been able to reproduce the crash under certain settings.So, our plan is to continue to push the memory changes we've made to live and hopefully that will fix or mitigate the problem for many of you. But we are still continuing to look into the crash issue. </blockquote>I just crashed on Windows 7 with apparently 3 gig of memory usage. To be fair, it was the first crash I've seen since I upgraded my OS. If you are still chasing this down, I'm happy to send in DX logs or whatever helps.

dgray81

10-02-2009, 11:02 PM

My wifes computer is running Windows 7 and it's crashing aswell. The game is using about 2.5gb of ram as soon as she logs in. I hope this gets fixed soon because she JUST started playing EQ2 and frequent crashing isnt likely to help her decide to stick with it.

Soldancer

10-03-2009, 12:36 AM

<cite>Talsmar@Crushbone wrote:</cite><blockquote>I don't seem to have any memory issues.. I raided last night for 4 hours and all went well. No game errors.When I played a couple years ago I read on these boards about a setting you can change that helps with memory leaks.It is a simple change and may help until things get fixed.. here it is (Win XP Sp-2):Start/My comp/right click-properties/advanced tabUnder "performance" select Settings/Advanced tabUnder Memory usage select "System Cache" vice "Programs"Give it a whirl.. If it doesn't help then just set it back to programs..</blockquote>I tried this setting and at the beginning it looked liked it would work great (loading option settings, switching between fullscreen/window mode and zoning times were as fast as before LU53). But after a longer play session with visiting many different zones it became as worse as before. Anyway a good workaround which helps if you restart the programm more often.

Aera

10-03-2009, 12:11 PM

Windows XP user here with a computer more than capable of running EQ2 at high settings and still getting the out of memory crash error about every hour or so of play. <img src="/eq2/images/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" />

Sunlei

10-03-2009, 02:54 PM

CRASH CRASH CRASH random zones , same DX error !! DX9 error I have dx9.0C and newest driver.started with last update, crash about once a hour! usually runs fine, now this sucks!heres the error message file."build="SOEBuild=5932L" version="SOEVersionString=2009/9/29 18:19:07" build_type="USER OPTIMIZED" ls_address="none" zone="exp03_dun_mistmoore_catacombs" loc="-133.70 -84.73 176.51" performance="5" verify="E:liveeq2frameworkcoredevicessrcDirectX9RenderDevi ce.cpp(2895): DirectX Error. (D3DERR_NOTAVAILABLE) 009c7163 009ca32d"

Rothgar

10-03-2009, 09:22 PM

<cite>Sunlei wrote:</cite><blockquote>CRASH CRASH CRASH random zones , same DX error !! DX9 error I have dx9.0C and newest driver.started with last update, crash about once a hour! usually runs fine, now this sucks!heres the error message file."build="SOEBuild=5932L" version="SOEVersionString=2009/9/29 18:19:07" build_type="USER OPTIMIZED" ls_address="none" zone="exp03_dun_mistmoore_catacombs" loc="-133.70 -84.73 176.51" performance="5" verify="E:liveeq2frameworkcoredevicessrcDirectX9RenderDevi ce.cpp(2895): DirectX Error. (D3DERR_NOTAVAILABLE) 009c7163 009ca32d"</blockquote>This is a different problem and not related to the memory allocation crash. Some people have reported problems with the latest video driver. You could try installing an older version. Just make sure you do a full uninstall of the old driver first. Tech Support might have more ideas on fixing your D3D error.

vochore

10-03-2009, 11:11 PM

just as an update to my last post...i have since done some upgrades to my system which is shown in my sig....2 raptor hardrives.8 gig,s of memory now and vista 64 bit.pagefile after 50 mins was at 4355.74 and system memory was at 4101.13if i could figure out how to i would post the rivatuner file for you to see.edited for spelling...lol

Isilsisial

10-05-2009, 06:07 AM

Don't know if its relevant, but our internet connection has software that allows us to see our overall MB/bandwidth usage and I have been seeing some insanely huge amounts since the update. Before the update to GU#53 it used to be after a couple of hours we'd have sent and recieved somewhere between 7.5 to 28 MBs, now when we crash every couple hours, we see 100- 400 MBs used everytime... seems an odd coincidence to me, that it is happening while we are crashing with an "out of memory" error.

Tro

10-05-2009, 07:50 AM

<cite>Choatley@Mistmoore wrote:</cite><blockquote><cite>Talsmar@Crushbone wrote:</cite><blockquote><cite>Galldora wrote:</cite><blockquote>Rothgar, I really appreciate your detailed explanation about what is being done to fix this most vexing problem. Thanks for keeping us informed! /smooch<cite>Talsmar@Crushbone wrote:</cite><blockquote><cite>Talsmar@Crushbone wrote:</cite><blockquote>I don't seem to have any memory issues.. I raided last night for 4 hours and all went well. No game errors.When I played a couple years ago I read on these boards about a setting you can change that helps with memory leaks.It is a simple change and may help until things get fixed.. here it is (Win XP Sp-2):Start/My comp/right click-properties/advanced tabUnder "performance" select Settings/Advanced tabUnder Memory usage select "System Cache" vice "Programs"Give it a whirl.. If it doesn't help then just set it back to programs..</blockquote>Has anyone tried this? To add to this, My client has never received a memory crash with GU 53. I always keep the setting above even when I reload the OS I still set this to System Cache. My wife and I both have essentially the same system (Different video cards and PSU but everything else is the same) and she has not had a memory crash since Gu 53 came out either.The above setting is just a suggestion but again we have not had a memory crash with GU 53.</blockquote>Talsmar, I've tried your suggestion, and yes, this does seem to work for me. Thanks!! /smooch for you, too! (must be in a kissy mood today <img src="/eq2/images/smilies/8a80c6485cd926be453217d59a84a888.gif" border="0" /> )I just changed my settings to favor system, then watched memory usage while a character zoned in and out of our fully-loaded guild hall several times. What I saw happening, which I hadn't seen before, is that the numbers will climb pretty high, but they drop periodically as well, preventing a crash. I'm going to make this change on my other machine, too. Funny thing is, I looked at that setting the other day and thought about changing it, but then thought it was better to favor programs than system cache -- backward thinking there!I haven't been having crashes as long as I remember to minimize frequently -- and I haven't noticed rendering problems popping up when doing this either, but apparently others haven't been so lucky using that little workaround -- but I'd sure rather not have to bother with it.</blockquote>No Problem.. Glad it helped. <img src="/eq2/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" /></blockquote>Typically, for many programs, this isn't really a good change to make. It may help with the issues you are having in this game, but it's something that would seem to be an unintended help. It won't cause any real harm and most people will be able to toggle back and forth to try it out, but they should read up more on the setting. Changing this setting to try to help this game issue can negatively effect performace of several other things.<a rel="nofollow" href="http://support.microsoft.com/kb/895932" target="_blank">http://support.microsoft.com/kb/895932</a></blockquote>It seems to help me with 2GB ram as I am not having these memory issues I am reading about here. . I read about this setting change on theses boards back when I first started playing back in 2005. That was when EQ2 had a known memory leak. I have never had a memory problem so I figured it was worth a shot. Like I said if it does not help they can always put it back to "Programs". Hopefully they will get it the client working correctly sooner than later..

Guy De Alsace

10-05-2009, 09:17 AM

I got an out of memory crash about 1 min after doing the minimize/maximise thing, flying from Terens to Highton. So it doesnt work in every instance.

Enever

10-05-2009, 11:33 AM

The Primary crash that happens to me, is when i'm zoning into a guildhall or from a guildhall. It may still occur as I zone. Last night I had an Out of Memory error when zoning into guk 2. I play the game at High quality without shadows.Not sure if this will help, but it was my most recent crash.

Collin_Rowanstaff

10-05-2009, 12:55 PM

<cite>Talsmar@Crushbone wrote:</cite><blockquote><cite>Choatley@Mistmoore wrote:</cite><blockquote><cite>Talsmar@Crushbone wrote:</cite><blockquote><cite>Galldora wrote:</cite><blockquote>Rothgar, I really appreciate your detailed explanation about what is being done to fix this most vexing problem. Thanks for keeping us informed! /smooch<cite>Talsmar@Crushbone wrote:</cite><blockquote><cite>Talsmar@Crushbone wrote:</cite><blockquote>I don't seem to have any memory issues.. I raided last night for 4 hours and all went well. No game errors.When I played a couple years ago I read on these boards about a setting you can change that helps with memory leaks.It is a simple change and may help until things get fixed.. here it is (Win XP Sp-2):Start/My comp/right click-properties/advanced tabUnder "performance" select Settings/Advanced tabUnder Memory usage select "System Cache" vice "Programs"Give it a whirl.. If it doesn't help then just set it back to programs..</blockquote>Has anyone tried this? To add to this, My client has never received a memory crash with GU 53. I always keep the setting above even when I reload the OS I still set this to System Cache. My wife and I both have essentially the same system (Different video cards and PSU but everything else is the same) and she has not had a memory crash since Gu 53 came out either.The above setting is just a suggestion but again we have not had a memory crash with GU 53.</blockquote>Talsmar, I've tried your suggestion, and yes, this does seem to work for me. Thanks!! /smooch for you, too! (must be in a kissy mood today <img src="/eq2/images/smilies/8a80c6485cd926be453217d59a84a888.gif" border="0" /> )I just changed my settings to favor system, then watched memory usage while a character zoned in and out of our fully-loaded guild hall several times. What I saw happening, which I hadn't seen before, is that the numbers will climb pretty high, but they drop periodically as well, preventing a crash. I'm going to make this change on my other machine, too. Funny thing is, I looked at that setting the other day and thought about changing it, but then thought it was better to favor programs than system cache -- backward thinking there!I haven't been having crashes as long as I remember to minimize frequently -- and I haven't noticed rendering problems popping up when doing this either, but apparently others haven't been so lucky using that little workaround -- but I'd sure rather not have to bother with it.</blockquote>No Problem.. Glad it helped. <img src="/eq2/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" /></blockquote>Typically, for many programs, this isn't really a good change to make. It may help with the issues you are having in this game, but it's something that would seem to be an unintended help. It won't cause any real harm and most people will be able to toggle back and forth to try it out, but they should read up more on the setting. Changing this setting to try to help this game issue can negatively effect performace of several other things.<a rel="nofollow" href="http://support.microsoft.com/kb/895932" target="_blank">http://support.microsoft.com/kb/895932</a></blockquote>It seems to help me with 2GB ram as I am not having these memory issues I am reading about here. . I read about this setting change on theses boards back when I first started playing back in 2005. That was when EQ2 had a known memory leak. I have never had a memory problem so I figured it was worth a shot. Like I said if it does not help they can always put it back to "Programs". Hopefully they will get it the client working correctly sooner than later..</blockquote>I tried this. I still crashed when zoning into GH or large Kunark zones. NM, back to normal seetings.<img src="/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" alt="SMILEY" />

Ven

10-05-2009, 03:00 PM

New player here, and I've experienced a number of memory issues since I started. I've only recieved the out of memory crash once, but I've noticed that while I'm playing EQ2's memory usage continues to spike no matter what I'm doing, to the point that I have to close out the game and restart just to get back to having smooth gameplay. My computer can more than handle this game and I'd really like to be able to play it, but if a fix isn't released sometime soon I can't see myself sticking around much longer.

Zebrat

10-05-2009, 03:57 PM

Been playing for years and I've worked in IT for longer so I kinda know what I'm talking about (I hope)All your changes are put through a Release Management process with a regression plan? Simple fact is that whatever you did to gameplay in last update, regardless of whatever QA testing you do, has broken the game for lots of ppl to the point where they might stop being your customers. So regress the changes, problem goes away from customers, gives you time to figure out what you have broken before you release the hopefully fixed changes again.Please don't tell me you can't regress changes... feel free to take all the extra content from last update if necessary while you sort it out btw, would swap all of that to have the game back in the state it was before.

Rothgar

10-05-2009, 06:46 PM

<cite>Zebrat@Runnyeye wrote:</cite><blockquote>Been playing for years and I've worked in IT for longer so I kinda know what I'm talking about (I hope)All your changes are put through a Release Management process with a regression plan? Simple fact is that whatever you did to gameplay in last update, regardless of whatever QA testing you do, has broken the game for lots of ppl to the point where they might stop being your customers. So regress the changes, problem goes away from customers, gives you time to figure out what you have broken before you release the hopefully fixed changes again.Please don't tell me you can't regress changes... feel free to take all the extra content from last update if necessary while you sort it out btw, would swap all of that to have the game back in the state it was before.</blockquote>As several people have mentioned in this thread, the crash has been around for awhile. Due to some changes in 53 that caused more memory to be allocated, the crash became more frequent. I don't suppose you read my message where I said the next hotfix will reduce the memory requirements. We're not planning on reverting any changes. Character versions and lots of data serialization changed with GU53 and it would require additional code to make both old and new character versions deserialize without problems. That time is better spent working on the fix. I'm hoping the hotfix (due on Wednesday) will solve the problem for most people. We have a schedule to release a streaming client into beta very soon and the changes we made are integral to keeping that schedule. We have a repro case in-house now, so the problem will be solved.

Guy De Alsace

10-06-2009, 04:14 AM

*does a happy dance*The problem is bad but nowhere near enough to unsubscribe <img src="/eq2/images/smilies/2786c5c8e1a8be796fb2f726cca5a0fe.gif" border="0" /> (other unrelated issues notwithstanding of course)

Tallisman

10-06-2009, 06:44 AM

I understand there's a fix due (yay!) but I thought this may also be helpful - I'd just clicked the bell in Antonica to travel to TS when I crashed (the game wanted 1.5GB of data when my card was only willing to give it 892MB <img src="/smilies/283a16da79f3aa23fe1025c96295f04f.gif" border="0" alt="SMILEY" /> ):SOEBuild=5932LSOEVersionString=2009/9/29 18:19:07EVERQUEST2 CRASH LOG=============================================== ================================================== =Unhandled exception EXCEPTION_ACCESS_VIOLATION at 0x00B3CD1FApplication was trying to write to 0x00000002 Region Begins At: 0x00000000 Region Ends At: 0x00010000 Region Size Is: 0x00010000 bytes Memory Protection: PAGE_NOACCESS (00000001) Memory State: MEM_FREE Memory Type: FreeGame Data: SOEBuild: SOEBuild=5932L SOEVersionString: SOEVersionString=2009/9/29 18:19:07 OS Version: 5.1.2600 Service Pack 2 VER_NT_WORKSTATION CPU: 2 x86 GenuineIntel 2938MHz RDTSC MSR CMPXCHG8 SSE SSE2 DirectX Version: 9.0c Video Card/Driver: [NVIDIA GeForce GTX 260] [nv4_disp.dll] 6.14.11.7813 {d7b71e3e-46a2-11cf-b76b-9b0300c2cb35} Time at crash: Tue Oct 06 10:30:56 2009 Login Server: none Performance: 7 Game Uptime: 1964 seconds Position last frame: -550.52, -20.00, -403.17 Zone name: steppes Time in Zone: 11 seconds Previous Zone name: GameScene::ZR_NETWORKED_ZONE_CHANGE Multi-core support: disabled Low-Memory Mode: disabledLog: WARNING - Duplicate cached nodes found for composed/ui_fx/fx/systems/spells/simple/trace_prism.voc (not caching). WARNING - Duplicate cached nodes found for composed/ui_fx/fx/systems/spells/classbase/nothing.voc (not caching). WARNING - Duplicate cached nodes found for composed/ui_fx/fx/systems/spell_pieces/distort.voc (not caching). WARNING - Duplicate cached nodes found for composed/characters/accessories/wieldable_items/weapons/exp04/1h_crush/exp04_1hc_the_impact_of_the_sacrosanct.voc (not caching). WARNING - Duplicate cached nodes found for composed/ui_fx/fx/systems/spells/simple/gold_sparkletrace.voc (not caching). WARNING - Duplicate cached nodes found for composed/interiors/scenes/objects_race/dp_objects/holiday_objects/dpo_snowflake01.voc (not caching). WARNING - Duplicate cached nodes found for composed/characters/accessories/wieldable_items/weapons/exp04/1h_crush/exp04_1hc_cudgel_of_obviation.voc (not caching). [0.00s] cached app nodes [0.00s] VeRoomItemNodeLUT loaded E:liveeq2frameworkmemoryManagersrcsharedMemoryMana ger.cpp(2010): Application ran out of memory when requesting 4194336 bytes (limit: 1535 MB, current: 760 MB)Thread Data: Primary Thread Id: 2840 Current Thread Id: 2840 Current Thread Priority: 0Memory: AddressLimitMB: 2048 Load: 96% Total physical: 2146480128 Free physical: 80211968 Total pagefile: 4134952960 Free pagefile: 1589084160 Total virtual: 2147352576 Free virtual: 78729216Memory Manager: Allocations: 291860 Bytes Allocated: 624911824 Max Allocations: 322164 Max Bytes Allocated: 786641616 System Memory Allocated (MB): 760 Limit: 1535 Number of Allocate Calls: 3614976 Number of Free Calls: 3323116Registers:EAX 0x00000001 EBX 0x7C91056D ECX 0x7CDE0001 EDX 0x008D46B3 ESI 0x7C859EF8 EDI 0x00400020 GS 0x00000000FS 0x0000003B ES 0x00000023 DS 0x00000023 EBP 0x0013F238ESP 0x0013E9D8 EIP 0x00B3CD1F FLAGS 0x00010246 CS 0x0000001B SS 0x00000023FPU Registers: CW 0xFFFF027F SW 0xFFFF4220 TW 0xFFFFFFFFFPU Rounding Mode: NearestCall Stack: 0x00B3CD1F: MemoryManager::allocate+302f 0x008D46B3 in C:eq2EverQuest2.exe 0x00944420 in C:eq2EverQuest2.exeEnd of Call StackStack Scan: 0x0013E9D8: 0x00000000 0x0013E9DC: 0x6C707041 0x0013E9E0: 0x74616369 0x0013E9E4: 0x206E6F69 0x0013E9E8: 0x206E6172 0x0013E9EC: 0x2074756F 0x0013E9F0: 0x6D20666F 0x0013E9F4: 0x726F6D65 0x0013E9F8: 0x68772079 0x0013E9FC: 0x72206E65 0x0013EA00: 0x65757165 0x0013EA04: 0x6E697473 0x0013EA08: 0x31342067 0x0013EA0C: 0x33333439 0x0013EA10: 0x79622036 0x0013EA14: 0x20736574 0x0013EA18: 0x6D696C28 0x0013EA1C: 0x203A7469 0x0013EA20: 0x35333531 0x0013EA24: 0x2C424D20 0x0013EA28: 0x72756320 0x0013EA2C: 0x746E6572 0x0013EA30: 0x3637203A 0x0013EA34: 0x424D2030 0x0013EA38: 0x00000029 0x0013EA3C: 0x00000000 0x0013EA40: 0x3F800000 0x0013EA44: 0x3F800000 0x0013EA48: 0x00000000 0x0013EA4C: 0x00000000 0x0013EA50: 0x00000000 0x0013EA54: 0x00000000 0x0013EA58: 0xBF800000 0x0013EA5C: 0x00000000 0x0013EA60: 0x00000000 0x0013EA64: 0x00000000 0x0013EA68: 0x00000000 0x0013EA6C: 0x3F800000 0x0013EA70: 0x00000000 0x0013EA74: 0xC4700000 0x0013EA78: 0x44160000 0x0013EA7C: 0x00000000 0x0013EA80: 0x3F800000 0x0013EA84: 0x45BB8000 0x0013EA88: 0x80000000 0x0013EA8C: 0x80000000 0x0013EA90: 0x00000000 0x0013EA94: 0x00000000 0x0013EA98: 0xC5BB8000 0x0013EA9C: 0x00000000 0x0013EAA0: 0x00000000 0x0013EAA4: 0x80000000 0x0013EAA8: 0x00000000 0x0013EAAC: 0x45BB8000 0x0013EAB0: 0x00000000 0x0013EAB4: 0x00000000 0x0013EAB8: 0x00000000 0x0013EABC: 0x00000000 0x0013EAC0: 0x3F800000 0x0013EAC4: 0x3F800000 0x0013EAC8: 0x44160000 0x0013EACC: 0x00000000 0x0013EAD0: 0x3F800000 0x0013EAD4: 0x80000000 0x0013EAD8: 0x80000000 0x0013EADC: 0x44160000 0x0013EAE0: 0x80000000 0x0013EAE4: 0x44700000 0x0013EAE8: 0x00000000 0x0013EAEC: 0x00000000 0x0013EAF0: 0x00000000 0x0013EAF4: 0x80000000 0x0013EAF8: 0x0013EB24 0x0013EAFC: 0x009FD35C, in C:eq2EverQuest2.exe (0x00400000) 0x0013EB00: 0x44BBD4A0 0x0013EB04: 0x44BBD4A0 0x0013EB08: 0x31F993A0 0x0013EB0C: 0x0013EC58 0x0013EB10: 0x0013EC54 0x0013EB14: 0x44BBD4A0 0x0013EB18: 0x0013EBB8 0x0013EB1C: 0x00000000 0x0013EB20: 0xFFFFFFFF 0x0013EB24: 0x0013EB98 0x0013EB28: 0x00A65278, in C:eq2EverQuest2.exe (0x00400000) 0x0013EB2C: 0x00A65281, in C:eq2EverQuest2.exe (0x00400000) 0x0013EB30: 0x0E3BBE80 0x0013EB34: 0x0013EC54 0x0013EB38: 0x44BBC2C0 0x0013EB3C: 0x80000000 0x0013EB40: 0x00C5E0B0, in C:eq2EverQuest2.exe (0x00400000) 0x0013EB44: 0x012178EC, in C:eq2EverQuest2.exe (0x00400000) 0x0013EB48: 0x0013EB74 0x0013EB4C: 0x0013EC58 0x0013EB50: 0x44BBD4A0 0x0013EB54: 0x44BBD4A0 0x0013EB58: 0x31F99320 0x0013EB5C: 0x0013EC14 0x0013EB60: 0x0013EC10 0x0013EB64: 0x44BBD4A0 0x0013EB68: 0x0013EFA0 0x0013EB6C: 0x00000000 0x0013EB70: 0xFFFFFFFF 0x0013EB74: 0x00000004 0x0013EB78: 0x00000004 0x0013EB7C: 0x0095B964, in C:eq2EverQuest2.exe (0x00400000) 0x0013EB80: 0x00000000 0x0013EB84: 0x00000000 0x0013EB88: 0x00000000 0x0013EB8C: 0x3F800000 0x0013EB90: 0x0013EC00 0x0013EB94: 0x0095B8D2, in C:eq2EverQuest2.exe (0x00400000) 0x0013EB98: 0x0013EBC4 0x0013EB9C: 0x009FD35C, in C:eq2EverQuest2.exe (0x00400000) 0x0013EBA0: 0x44BBC2C0 0x0013EBA4: 0x44BBC2C0 0x0013EBA8: 0x31F99320 0x0013EBAC: 0x0013EC58 0x0013EBB0: 0x0013EC54 0x0013EBB4: 0x44BBC2C0 0x0013EBB8: 0x0013EFE4 0x0013EBBC: 0x00000000 0x0013EBC0: 0xFFFFFFFF 0x0013EBC4: 0x0013EC30 0x0013EBC8: 0x00C5E0B0, in C:eq2EverQuest2.exe (0x00400000) 0x0013EBCC: 0x012178EC, in C:eq2EverQuest2.exe (0x00400000) 0x0013EBD0: 0x00000001 0x0013EBD4: 0x00C5F681, in C:eq2EverQuest2.exe (0x00400000) 0x0013EBD8: 0x012178EC, in C:eq2EverQuest2.exe (0x00400000) 0x0013EBDC: 0x00000001 0x0013EBE0: 0x00000001 0x0013EBE4: 0x00000001 0x0013EBE8: 0x0013EC18 0x0013EBEC: 0x0013EC58 0x0013EBF0: 0x012178EC, in C:eq2EverQuest2.exe (0x00400000) 0x0013EBF4: 0x0013EC10 0x0013EBF8: 0x00C60406, in C:eq2EverQuest2.exe (0x00400000) 0x0013EBFC: 0x012178EC, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC00: 0x00C60C51, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC04: 0x00C60BE1, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC08: 0x00C60BE1, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC0C: 0x01217860, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC10: 0x0013EFF0 0x0013EC14: 0x0042CEA8, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC18: 0x123BB408 0x0013EC1C: 0x00000014 0x0013EC20: 0x0013EC58 0x0013EC24: 0x0013EFD8 0x0013EC28: 0x0013EC40 0x0013EC2C: 0x00E147A8, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC30: 0xFFFFFFFF, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC34: 0x0042DD7B, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC38: 0x00ECEB40, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC3C: 0x0013EC58 0x0013EC40: 0x0013EFE4 0x0013EC44: 0x00E148D2, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC48: 0x00000002 0x0013EC4C: 0x009FED01, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC50: 0x00000000 0x0013EC54: 0x00ECEB40, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC58: 0x00EC945C, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC5C: 0x00000000 0x0013EC60: 0x00070001 0x0013EC64: 0x00000000 0x0013EC68: 0x01010101, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC6C: 0x012178EC, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC70: 0x00000001 0x0013EC74: 0x0013EC8C 0x0013EC78: 0x00A040DB, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC7C: 0x0013EC84 0x0013EC80: 0x6A639E08 0x0013EC84: 0x6A639E08 0x0013EC88: 0x0013ECB8 0x0013EC8C: 0x00C60406, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC90: 0x012178EC, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC94: 0x00C60BE1, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC98: 0x00A079CF, in C:eq2EverQuest2.exe (0x00400000) 0x0013EC9C: 0x6A2EFBD0 0x0013ECA0: 0x57840620 0x0013ECA4: 0x6A2EFBD0 0x0013ECA8: 0x01217860, in C:eq2EverQuest2.exe (0x00400000) 0x0013ECAC: 0x0013ED74 0x0013ECB0: 0x00E931A8, in C:eq2EverQuest2.exe (0x00400000) 0x0013ECB4: 0xFFFFFFFF, in C:eq2EverQuest2.exe (0x00400000) 0x0013ECB8: 0x0013ECD8 0x0013ECBC: 0x0013ECD8 0x0013ECC0: 0x00A4F7B8, in C:eq2EverQuest2.exe (0x00400000) 0x0013ECC4: 0x6A2EFBD0 0x0013ECC8: 0x01B993AC 0x0013ECCC: 0x11351790 0x0013ECD0: 0x00000000 0x0013ECD4: 0x011B7FB8, in C:eq2EverQuest2.exe (0x00400000) 0x0013ECD8: 0x0013ED00 0x0013ECDC: 0x00A4F9E3, in C:eq2EverQuest2.exe (0x00400000) 0x0013ECE0: 0x0013ED0C 0x0013ECE4: 0x01B993D8 0x0013ECE8: 0x00A4F5A6, in C:eq2EverQuest2.exe (0x00400000) 0x0013ECEC: 0x00000000 0x0013ECF0: 0x011B8018, in C:eq2EverQuest2.exe (0x00400000) 0x0013ECF4: 0x00000001 0x0013ECF8: 0x011B8018, in C:eq2EverQuest2.exe (0x00400000) 0x0013ECFC: 0x0013ED1C 0x0013ED00: 0x00A4FC18, in C:eq2EverQuest2.exe (0x00400000) 0x0013ED04: 0x01B993D8 0x0013ED08: 0x01B993D8 0x0013ED0C: 0x00000000 0x0013ED10: 0x57840620 0x0013ED14: 0x01B993D8 0x0013ED18: 0x01B993D8 0x0013ED1C: 0x0013ED3C 0x0013ED20: 0x00A500CD, in C:eq2EverQuest2.exe (0x00400000) 0x0013ED24: 0x0013ED4C 0x0013ED28: 0x0013F050 0x0013ED2C: 0x57840620 0x0013ED30: 0x00C60BE1, in C:eq2EverQuest2.exe (0x00400000) 0x0013ED34: 0x6A2EFBD0 0x0013ED38: 0x00C60401, in C:eq2EverQuest2.exe (0x00400000) 0x0013ED3C: 0x0013ED80 0x0013ED40: 0x00A0B729, in C:eq2EverQuest2.exe (0x00400000) 0x0013ED44: 0x00000000 0x0013ED48: 0x00000001 0x0013ED4C: 0x57840620 0x0013ED50: 0x0E3BC770 0x0013ED54: 0x0013F050 0x0013ED58: 0x009FD35C, in C:eq2EverQuest2.exe (0x00400000) 0x0013ED5C: 0x57840620 0x0013ED60: 0x0E3BC770 0x0013ED64: 0x0013F050 0x0013ED68: 0x1ABA1DA0 0x0013ED6C: 0x0013F050 0x0013ED70: 0x0000002C 0x0013ED74: 0x0000002C 0x0013ED78: 0x008BC77C, in C:eq2EverQuest2.exe (0x00400000) 0x0013ED7C: 0x00B3CC87, in C:eq2EverQuest2.exe (0x00400000) 0x0013ED80: 0x01209DC8, in C:eq2EverQuest2.exe (0x00400000) 0x0013ED84: 0x00B39D67, in C:eq2EverQuest2.exe (0x00400000) 0x0013ED88: 0x0000002C 0x0013ED8C: 0x0013EDEC 0x0013ED90: 0x0000001E 0x0013ED94: 0x1ABA1DA0 0x0013ED98: 0x0013F050 0x0013ED9C: 0x1ABA1DA0 0x0013EDA0: 0x0013EED8 0x0013EDA4: 0x0013F3A0 0x0013EDA8: 0x00E86C22, in C:eq2EverQuest2.exe (0x00400000) 0x0013EDAC: 0x0013EDEC 0x0013EDB0: 0x0000002C 0x0013EDB4: 0x0013F3C4 0x0013EDB8: 0x008BC794, in C:eq2EverQuest2.exe (0x00400000) 0x0013EDBC: 0x237A4D50 0x0013EDC0: 0x237A3250 0x0013EDC4: 0x0000001E 0x0013EDC8: 0x0000002C 0x0013EDCC: 0x0013F3C4 0x0013EDD0: 0x57775D9C 0x0013EDD4: 0x0013EDF8End of Stack ScanEND OF LOG

Ebarel

10-06-2009, 10:49 AM

<cite>Tallisman wrote:</cite><blockquote>================================================== ================================================ E:liveeq2frameworkmemoryManagersrcsharedMemoryMana ger.cpp(2010): Application ran out of memory when requesting 4194336 bytes (limit: 1535 MB, current: 760 MB)</blockquote>again, in (iirc) every crash log i see it is directing to a path that doesnt exist. You are sure that this isnt part of the problem?

Jeeshman

10-06-2009, 11:35 AM

<cite>Ebarel wrote:</cite><blockquote><cite>Tallisman wrote:</cite><blockquote>================================================== ================================================ E:liveeq2frameworkmemoryManagersrcsharedMemoryMana ger.cpp(2010): Application ran out of memory when requesting 4194336 bytes (limit: 1535 MB, current: 760 MB)</blockquote>again, in (iirc) every crash log i see it is directing to a path that doesnt exist. You are sure that this isnt part of the problem?</blockquote>Quoted For Huge Giant Incredibly Important Emphasis... every time I experience the crash, the crash log indicates the same path as mentioned above, which does not exist as it's my CD drive.

Lantis

10-06-2009, 11:54 AM

<cite>Shaydu@Everfrost wrote:</cite><blockquote><cite>Ebarel wrote:</cite><blockquote><cite>Tallisman wrote:</cite><blockquote>================================================== ================================================ E:liveeq2frameworkmemoryManagersrcsharedMemoryMana ger.cpp(2010): Application ran out of memory when requesting 4194336 bytes (limit: 1535 MB, current: 760 MB)</blockquote>again, in (iirc) every crash log i see it is directing to a path that doesnt exist. You are sure that this isnt part of the problem?</blockquote>Quoted For Huge Giant Incredibly Important Emphasis... every time I experience the crash, the crash log indicates the same path as mentioned above, which does not exist as it's my CD drive.</blockquote>This is debug information. The path you see refers to the source code on SOE's side - it doesn't reflect the file on your computer where the crash occured. This is perfectly normal, and isn't the cause of the crash - it's just information for programmers.

Tro

10-06-2009, 02:19 PM

<cite>Rothgar wrote:</cite><blockquote><cite>Zebrat@Runnyeye wrote:</cite><blockquote>Been playing for years and I've worked in IT for longer so I kinda know what I'm talking about (I hope)All your changes are put through a Release Management process with a regression plan? Simple fact is that whatever you did to gameplay in last update, regardless of whatever QA testing you do, has broken the game for lots of ppl to the point where they might stop being your customers. So regress the changes, problem goes away from customers, gives you time to figure out what you have broken before you release the hopefully fixed changes again.Please don't tell me you can't regress changes... feel free to take all the extra content from last update if necessary while you sort it out btw, would swap all of that to have the game back in the state it was before.</blockquote>As several people have mentioned in this thread, the crash has been around for awhile. Due to some changes in 53 that caused more memory to be allocated, the crash became more frequent. I don't suppose you read my message where I said the next hotfix will reduce the memory requirements. We're not planning on reverting any changes. Character versions and lots of data serialization changed with GU53 and it would require additional code to make both old and new character versions deserialize without problems. That time is better spent working on the fix. I'm hoping the hotfix (due on Wednesday) will solve the problem for most people.We have a schedule to release a streaming client into beta very soon and the changes we made are integral to keeping that schedule. We have a repro case in-house now, so the problem will be solved.</blockquote>What is this "Streaming Client" you speak of? Is the idea to provide smoother game play?Just curious..Thanks

TSR-DanielH

10-06-2009, 03:03 PM

<cite>Lantis@Antonia Bayle wrote:</cite><blockquote>This is debug information. The path you see refers to the source code on SOE's side - it doesn't reflect the file on your computer where the crash occured. This is perfectly normal, and isn't the cause of the crash - it's just information for programmers.</blockquote>That is correct. The file path listed is referring to the file on our system, not yours.

TSR-DanielH

10-06-2009, 03:09 PM

<cite>Talsmar@Crushbone wrote:</cite><blockquote><cite>Rothgar wrote:</cite><blockquote>We have a schedule to release a streaming client into beta very soon and the changes we made are integral to keeping that schedule. We have a repro case in-house now, so the problem will be solved.</blockquote>What is this "Streaming Client" you speak of? Is the idea to provide smoother game play?Just curious..Thanks</blockquote>If you've played Free Realms then you might be familiar with the system. A streaming client will make it so that you don't need to download the entire 11GB of game files to start playing. Instead it would download files as needed and allow people to start playing faster.

Tro

10-06-2009, 03:45 PM

<cite>TSR-DanielH wrote:</cite><blockquote><cite>Talsmar@Crushbone wrote:</cite><blockquote><cite>Rothgar wrote:</cite><blockquote>We have a schedule to release a streaming client into beta very soon and the changes we made are integral to keeping that schedule. We have a repro case in-house now, so the problem will be solved.</blockquote>What is this "Streaming Client" you speak of? Is the idea to provide smoother game play?Just curious..Thanks</blockquote>If you've played Free Realms then you might be familiar with the system. A streaming client will make it so that you don't need to download the entire 11GB of game files to start playing. Instead it would download files as needed and allow people to start playing faster.</blockquote>Wow.. good deal.. Very nice..

Tallisman

10-06-2009, 06:15 PM

Just a question. In my log I see this:(limit: 1535 MB, current: 760 MB)However, my GTX260 has 896MB RAM on board. Where did the remaining 136MB go?

TSR-DanielH

10-06-2009, 06:23 PM

<cite>Tallisman wrote:</cite><blockquote>Just a question. In my log I see this:(limit: 1535 MB, current: 760 MB)However, my GTX260 has 896MB RAM on board. Where did the remaining 136MB go?</blockquote>I think you're getting the numbers mixed up there. Here is the error message you're referring to:"Application ran out of memory when requesting 4194336 bytes (limit: 1535 MB, current: 760 MB)"According to that error message your system was using 760MB when the game requested 4194336 bytes. That went over the 1535 limit and crashed.

Ebarel

10-07-2009, 05:11 AM

<cite>TSR-DanielH wrote:</cite><blockquote><cite>Tallisman wrote:</cite><blockquote>Just a question. In my log I see this:(limit: 1535 MB, current: 760 MB)However, my GTX260 has 896MB RAM on board. Where did the remaining 136MB go?</blockquote>I think you're getting the numbers mixed up there. Here is the error message you're referring to:"Application ran out of memory when requesting 4194336 bytes (limit: 1535 MB, current: 760 MB)"According to that error message your system was using 760MB when the game requested 4194336 bytes. That went over the 1535 limit and crashed.</blockquote>funny thing is, 4.194.336 bytes = 4 MB - why dont they fit into the 800MB free space between tha current and the limit? most times i crash the requested numbers are minimal in comparison to what should be free. there are only few cases when it requests huge amounts

cr0wangel

10-07-2009, 10:59 AM

Do the hotfix for the memory bug was pushed live today?

kellycoo

10-07-2009, 01:31 PM

Ha, if hotfix was done this morning before 12:30 est, it's even worse now than before. I had memory crash before 3 of my characters were even able to zone, one other before he even fully loaded into the zone....

Nicadeem

10-07-2009, 01:31 PM

If they did then it didn't work. I've just had the out of memory crash not 5 minutes ago while trying to finish DFC.

BK613

10-07-2009, 02:05 PM

So no word on when then?First it was to be hotfixed Mon and then Wed and apparently it didn't happen today...

Rothgar

10-07-2009, 02:55 PM

<cite>BK613 wrote:</cite><blockquote>So no word on when then?First it was to be hotfixed Mon and then Wed and apparently it didn't happen today...</blockquote>As I posted a couple of pages back, we confirmed that the memory crash still existed after our initial round of changes. The hotfix today did make some changes to our memory management that should have reduced the "footprint" of the client by a bit, but we knew it wouldn't eliminate the crash. We're still actively working on the issue as fast as we can.

BK613

10-07-2009, 04:54 PM

<cite>Rothgar wrote:</cite><blockquote><cite>BK613 wrote:</cite><blockquote>So no word on when then?First it was to be hotfixed Mon and then Wed and apparently it didn't happen today...</blockquote>As I posted a couple of pages back, we confirmed that the memory crash still existed after our initial round of changes. The hotfix today did make some changes to our memory management that should have reduced the "footprint" of the client by a bit, but we knew it wouldn't eliminate the crash. We're still actively working on the issue as fast as we can.</blockquote>Didn't mean for that to come across so snarky, just that there was nothing in the hotfix notes about it.And........------------------------------------------after the patch-------------------------------------------------------------------SOEBuild=5949LSOEVersionString=2009/10/6 16:21:34EVERQUEST2 CRASH LOG=============================================== ================================================== =Unhandled exception EXCEPTION_ACCESS_VIOLATION at 0x00B3CA5FApplication was trying to write to 0x00000002 Region Begins At: 0x00000000 Region Ends At: 0x00010000 Region Size Is: 0x00010000 bytes Memory Protection: PAGE_NOACCESS (00000001) Memory State: MEM_FREE Memory Type: FreeGame Data: SOEBuild: SOEBuild=5949L SOEVersionString: SOEVersionString=2009/10/6 16:21:34 OS Version: 5.1.2600 Service Pack 2 VER_SUITE_PERSONAL VER_NT_WORKSTATION CPU: 2 x86 GenuineIntel 2794MHz RDTSC MSR CMPXCHG8 SSE SSE2 DirectX Version: 9.0c Video Card/Driver: [NVIDIA GeForce 6800 GS] [nv4_disp.dll] 6.14.11.8618 {d7b71e3e-4307-11cf-745b-0f2300c2cb35} Time at crash: Wed Oct 07 14:37:30 2009 Login Server: none Performance: 7 Game Uptime: 8950 seconds Position last frame: 1074.67, 142.09, -27.06 Zone name: exp04_rgn_kylong_plains Time in Zone: 5665 seconds Previous Zone name: GameScene::ZR_NETWORKED_ZONE_CHANGE Multi-core support: disabled Low-Memory Mode: disabledLog: Not VF_AUTO Not VF_AUTO Not VF_AUTO Not VF_AUTO Not VF_AUTO s(1680,990) i_left=71 i_right=1144 i_top=944 i_bottom=12 b_vert=false s(1680,990) i_left=1141 i_right=432 i_top=914 i_bottom=12 b_vert=false s(1680,990) i_left=1312 i_right=10 i_top=912 i_bottom=10 b_vert=false Not VF_AUTO Not VF_AUTOThread Data: Primary Thread Id: 1472 Current Thread Id: 2896 Current Thread Priority: 0Memory: AddressLimitMB: 2048 Load: 91% Total physical: 2145103872 Free physical: 188719104 Total pagefile: 4294967295 Free pagefile: 3184828416 Total virtual: 2147352576 Free virtual: 123531264Memory Manager: Allocations: 307702 Bytes Allocated: 686660048 Max Allocations: 355541 Max Bytes Allocated: 837706624 System Memory Allocated (MB): 800 Limit: 1534 Number of Allocate Calls: 6062079 Number of Free Calls: 5754377Registers: EAX 0x00000001 EBX 0x7C91005D ECX 0x6D380003 EDX 0x008CD55A ESI 0x7C859F08 EDI 0x001F31F0 GS 0x00000000 FS 0x0000003B ES 0x00000023 DS 0x00000023 EBP 0x0255FB88 ESP 0x0255F1CC EIP 0x00B3CA5F FLAGS 0x00010246 CS 0x0000001B SS 0x00000023FPU Registers: CW 0xFFFF027F SW 0xFFFF4000 TW 0xFFFFFFFFFPU Rounding Mode: NearestCall Stack: 0x00B3CA5F: MemoryManager::allocate+302f 0x008D1342 in e:SonyEverQuest IIEverQuest2.exe 0x008D17EA in e:SonyEverQuest IIEverQuest2.exe 0x008C1C71 in e:SonyEverQuest IIEverQuest2.exe 0x00D3FB46: MemoryManager::allocate+206116 0x0094748C in e:SonyEverQuest IIEverQuest2.exe 0x00B27656 in e:SonyEverQuest IIEverQuest2.exe 0x008D7DA5 in e:SonyEverQuest IIEverQuest2.exe 0x7C80B699: GetModuleFileNameA+1baEnd of Call Stack

BK613

10-07-2009, 04:54 PM

part 2-------------------------------------------------------------------------Stack Scan: 0x0255F1CC: 0x00000000 0x0255F1D0: 0x6C707041 0x0255F1D4: 0x74616369 0x0255F1D8: 0x206E6F69 0x0255F1DC: 0x206E6172 0x0255F1E0: 0x2074756F 0x0255F1E4: 0x6D20666F 0x0255F1E8: 0x726F6D65 0x0255F1EC: 0x68772079 0x0255F1F0: 0x72206E65 0x0255F1F4: 0x65757165 0x0255F1F8: 0x6E697473 0x0255F1FC: 0x30322067 0x0255F200: 0x30343434 0x0255F204: 0x79622030 0x0255F208: 0x20736574 0x0255F20C: 0x6D696C28 0x0255F210: 0x203A7469 0x0255F214: 0x34333531 0x0255F218: 0x2C424D20 0x0255F21C: 0x72756320 0x0255F220: 0x746E6572 0x0255F224: 0x3038203A 0x0255F228: 0x424D2030 0x0255F22C: 0x02550029 0x0255F230: 0x0255F238 0x0255F234: 0x0255F468 0x0255F238: 0x6E756F73 0x0255F23C: 0x612F7364 0x0255F240: 0x6569626D 0x0255F244: 0x5F2F746E 0x0255F248: 0x65746177 0x0255F24C: 0x61772F72 0x0255F250: 0x66726574 0x0255F254: 0x5F6C6C61 0x0255F258: 0x6772616C 0x0255F25C: 0x305F7265 0x0255F260: 0x6C5F3130 0x0255F264: 0x2E64756F 0x0255F268: 0x00766177, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F26C: 0x008CBBA8, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F270: 0x0255F3A0 0x0255F274: 0x0000002A 0x0255F278: 0x0255F3A0 0x0255F27C: 0x68428F6C 0x0255F280: 0x0255F3A0 0x0255F284: 0x011A5220, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F288: 0x00000000 0x0255F28C: 0x0208004C 0x0255F290: 0x00000045 0x0255F294: 0xCF2F7FCF 0x0255F298: 0x00000022 0x0255F29C: 0x00000015 0x0255F2A0: 0x00000003 0x0255F2A4: 0x0255F3B8 0x0255F2A8: 0x0000002A 0x0255F2AC: 0x017F7F7F 0x0255F2B0: 0x0255F36C 0x0255F2B4: 0x7F7F7F7F 0x0255F2B8: 0x0208002A 0x0255F2BC: 0x00020290 0x0255F2C0: 0x7FFD8C22 0x0255F2C4: 0x7C910435, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0255F2C8: 0x7C91043E, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0255F2CC: 0x0000D524 0x0255F2D0: 0x0255F244 0x0255F2D4: 0x0255F5F0 0x0255F2D8: 0x0255F584 0x0255F2DC: 0x7C90E920, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0255F2E0: 0x0255F618 0x0255F2E4: 0x00000008 0x0255F2E8: 0x00000008 0x0255F2EC: 0x00020024 0x0255F2F0: 0x0255F5F0 0x0255F2F4: 0x0255F594 0x0255F2F8: 0x7C910460, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0255F2FC: 0x7C980600, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0255F300: 0x7C913BDF, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0255F304: 0x7C913BA7, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0255F308: 0x00000000 0x0255F30C: 0x7FFD8C00 0x0255F310: 0x1E9979F5 0x0255F314: 0x008D82CA, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F318: 0x6C454FFF 0x0255F31C: 0x1E9979F5 0x0255F320: 0x000001B3 0x0255F324: 0x00000100 0x0255F328: 0x00000002 0x0255F32C: 0x0255F468 0x0255F330: 0x00000011 0x0255F334: 0x008CBBA8, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F338: 0x0255F468 0x0255F33C: 0x00000033 0x0255F340: 0x0255F468 0x0255F344: 0x55DBBC76 0x0255F348: 0x0255F468 0x0255F34C: 0x011A5220, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F350: 0x9127C92F, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F354: 0x02D00030 0x0255F358: 0x0350FAB4 0x0255F35C: 0x00000009 0x0255F360: 0xD3E6418A 0x0255F364: 0x9127C92F 0x0255F368: 0x0255F384 0x0255F36C: 0x008CFC15, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F370: 0x02D00030 0x0255F374: 0x00000000 0x0255F378: 0x0255F38C 0x0255F37C: 0x00000002 0x0255F380: 0x011A5220, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F384: 0x0255F4C4 0x0255F388: 0x008D0F59, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F38C: 0xD3E6418A, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F390: 0x9127C92F, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F394: 0x00000000 0x0255F398: 0x00000000 0x0255F39C: 0x0255F868 0x0255F3A0: 0x64616873 0x0255F3A4: 0x2F737265 0x0255F3A8: 0x706D6574 0x0255F3AC: 0x6574616C 0x0255F3B0: 0x31742F73 0x0255F3B4: 0x706D625F 0x0255F3B8: 0x6F6E5F31 0x0255F3BC: 0x6C6C7563 0x0255F3C0: 0x706C615F 0x0255F3C4: 0x762E3868 0x0255F3C8: 0x00006C64 0x0255F3CC: 0x00000000 0x0255F3D0: 0x00000000 0x0255F3D4: 0x00000000 0x0255F3D8: 0x00000000 0x0255F3DC: 0x00000002 0x0255F3E0: 0x008C09E5, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F3E4: 0x0255F620 0x0255F3E8: 0x0255F3F0 0x0255F3EC: 0x0255F620 0x0255F3F0: 0x64616873 0x0255F3F4: 0x2F737265 0x0255F3F8: 0x72616863 0x0255F3FC: 0x65746361 0x0255F400: 0x632F7372 0x0255F404: 0x74616572 0x0255F408: 0x73657275 0x0255F40C: 0x6E6F6D2F 0x0255F410: 0x008CC70A, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F414: 0xF9C6EE4D, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F418: 0x441A3B06 0x0255F41C: 0x02D00030 0x0255F420: 0x0350FAB4 0x0255F424: 0x00000011 0x0255F428: 0xF9C6EE4D 0x0255F42C: 0x441A3B06 0x0255F430: 0x0255F44C 0x0255F434: 0x008CFC15, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F438: 0x02D00030 0x0255F43C: 0x00000000 0x0255F440: 0x0255F454 0x0255F444: 0x00000002 0x0255F448: 0x011A5220, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F44C: 0x0255F58C 0x0255F450: 0x008D0F59, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F454: 0xF9C6EE4D, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F458: 0x441A3B06 0x0255F45C: 0x00000000 0x0255F460: 0x00000000 0x0255F464: 0x0255F930 0x0255F468: 0x6E756F73 0x0255F46C: 0x612F7364 0x0255F470: 0x6569626D 0x0255F474: 0x5F2F746E 0x0255F478: 0x65746177 0x0255F47C: 0x61772F72 0x0255F480: 0x66726574 0x0255F484: 0x5F6C6C61 0x0255F488: 0x6772616C 0x0255F48C: 0x305F7265 0x0255F490: 0x6C5F3130 0x0255F494: 0x2E64756F 0x0255F498: 0x00766177, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F49C: 0x0013000E 0x0255F4A0: 0x001F0011 0x0255F4A4: 0x002A0025 0x0255F4A8: 0x000A002E 0x0255F4AC: 0x0013000E 0x0255F4B0: 0x001F0011 0x0255F4B4: 0x0000001F 0x0255F4B8: 0x0000003F 0x0255F4BC: 0x00000003 0x0255F4C0: 0x00000005 0x0255F4C4: 0x2E827CF0 0x0255F4C8: 0x00000015 0x0255F4CC: 0x00000033 0x0255F4D0: 0x22813F4F 0x0255F4D4: 0x0000003F 0x0255F4D8: 0x000001FF 0x0255F4DC: 0x22817EA1 0x0255F4E0: 0x0E5D3E24 0x0255F4E4: 0x0B39BEB0 0x0255F4E8: 0x00008000 0x0255F4EC: 0x2E827CF0 0x0255F4F0: 0x0255F678 0x0255F4F4: 0x0255F514 0x0255F4F8: 0x009E15A7, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F4FC: 0x0B39BEE3 0x0255F500: 0x22817FA3 0x0255F504: 0x00000000 0x0255F508: 0x2E827CF0 0x0255F50C: 0x00000000 0x0255F510: 0x2E8298A0 0x0255F514: 0x2E827CE0 0x0255F518: 0x0255F6C0 0x0255F51C: 0x00B3C9C7, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F520: 0x01209DC8, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F524: 0x0E5D3E30 0x0255F528: 0x0E5D3880 0x0255F52C: 0x00000002 0x0255F530: 0x00000000 0x0255F534: 0x513E1770 0x0255F538: 0x00000002 0x0255F53C: 0x00000003 0x0255F540: 0x513E1770 0x0255F544: 0x00000006 0x0255F548: 0x00000010 0x0255F54C: 0x00040002 0x0255F550: 0x00080005 0x0255F554: 0x000E000E 0x0255F558: 0x000E000E 0x0255F55C: 0x000E000E 0x0255F560: 0x000E000E 0x0255F564: 0x000E000E 0x0255F568: 0x00000010 0x0255F56C: 0x00000000 0x0255F570: 0x00000000 0x0255F574: 0x00000000 0x0255F578: 0x00000000 0x0255F57C: 0x00000000 0x0255F580: 0x00000000 0x0255F584: 0x00000000 0x0255F588: 0x00000003 0x0255F58C: 0x513E1770 0x0255F590: 0x00000006 0x0255F594: 0x0000003C 0x0255F598: 0x68B189CF 0x0255F59C: 0x0000003F 0x0255F5A0: 0x000001FF 0x0255F5A4: 0x68B4B564 0x0255F5A8: 0x676B5BB0 0x0255F5AC: 0x0B39BEB0 0x0255F5B0: 0x00008000 0x0255F5B4: 0x513E1770 0x0255F5B8: 0x0255F740 0x0255F5BC: 0x0255F5DC 0x0255F5C0: 0x009E15A7, in e:SonyEverQuest IIEverQuest2.exe (0x00400000) 0x0255F5C4: 0x0B39BEEC 0x0255F5C8: 0x68B4B666 End of Stack Scan END OF LOG

Pharaooh

10-07-2009, 05:49 PM

As a lot of others, I have been crashing due to the memory issue as well. However, I found a temporary fix which is working fine for me: haven't crashed since. The fix is to run a program called FreeRAM XP Pro (am running 32 bit Vista so don't let the name fool you). You can get it at: <a href="http://www.yourwaresolutions.com/software.html#framxpro">http://www.yourwaresolutions.com/so...e.html#framxpro</a>. Make sure you set the following:MenuSettingsConfigure settingsProgram: check the option "Free RAM when starting windows"MenuSettingsConfigure settingsMemory: Automatically free if memory goes below 1000MB (in my case).While running this program I have experienced some delays when it is freeing memory, but hey, I prefer a small delay for a few secs then crashing <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" />Couldn't find any spyware, virusses or whatever in this program, but don't blame me if there is <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" />Hope this can temporarily help other players until SOE can fix the issue properly.

Yarginis

10-07-2009, 08:56 PM

1st impressions since patch; There is deffinatly an improvement based off of how it was yesterday. However it still appears to be slightly worse than pre-lu53. (not nessisarily in overall useage as measured my task manager, but in how much free memory the system has overall)I still saw the system peg 99% RAM usage in the GH today after applying the fix, however EQ2 was down to between 2.3 and 2.4gb (from 2.7-3gb pre-patch) EQ2 so far hasn't passed 2.4gb usage, so that is positive news on the front of the out of memory crash I was seeing at 3gb used, however it still seems to drag the rest of the system (web, etc) down far more than pre-lu53 even if it's memory useage is back in check due to the game leaving the system with still significatly less memory free overall somehow.I'm testing on my lower spec'd system right now to see if the memory use cuts improved it's performance at all, but so far it seems about the same...Lower system seems to be showing minor improvements, but is overall still exceedingly slow at zoning considering all setting are at minimum. (EQ2 still uses 900mb on absolutle lowest settings across the board, which hurts a system with 1.5gb RAM badly)So system with 4gb RAM on max settings is using ~2.4gb RAM after patch, 7 system with 1.5gb RAM on min settings is using ~900mb. (Both running win7 x64) Both are functioning better than yesterday, but not quite back to pre-53 lvls.

Rothgar

10-07-2009, 10:03 PM

<cite>Alexiiya@Nektulos wrote:</cite><blockquote>1st impressions since patch; There is deffinatly an improvement based off of how it was yesterday. However it still appears to be slightly worse than pre-lu53. (not nessisarily in overall useage as measured my task manager, but in how much free memory the system has overall)I still saw the system peg 99% RAM usage in the GH today after applying the fix, however EQ2 was down to between 2.3 and 2.4gb (from 2.7-3gb pre-patch) EQ2 so far hasn't passed 2.4gb usage, so that is positive news on the front of the out of memory crash I was seeing at 3gb used, however it still seems to drag the rest of the system (web, etc) down far more than pre-lu53 even if it's memory useage is back in check due to the game leaving the system with still significatly less memory free overall somehow.I'm testing on my lower spec'd system right now to see if the memory use cuts improved it's performance at all, but so far it seems about the same...Lower system seems to be showing minor improvements, but is overall still exceedingly slow at zoning considering all setting are at minimum. (EQ2 still uses 900mb on absolutle lowest settings across the board, which hurts a system with 1.5gb RAM badly)So system with 4gb RAM on max settings is using ~2.4gb RAM after patch, 7 system with 1.5gb RAM on min settings is using ~900mb. (Both running win7 x64) Both are functioning better than yesterday, but not quite back to pre-53 lvls.</blockquote>Thanks for posting your details. This matches about what we expected to see after our testing. We were able to lower the memory usage, but the crash still exists. Hopefully we will have the issue nailed down shortly.As someone suggested, a memory defragger could give some relief if you feel like running one. It sounds to me like we have an issue with garbage collection due to the resource manager loading and unloading resources so quickly. I'll keep you posted on our progress.

Foolsfolly

10-08-2009, 02:03 AM

I was able to play all day today without any crashes or even slowdown, for the first time since the last GU. Thankyou SoE.

Yarginis

10-08-2009, 02:27 AM

<cite>Rothgar wrote:</cite><blockquote>Thanks for posting your details. This matches about what we expected to see after our testing. We were able to lower the memory usage, but the crash still exists. Hopefully we will have the issue nailed down shortly.As someone suggested, a memory defragger could give some relief if you feel like running one. It sounds to me like we have an issue with garbage collection due to the resource manager loading and unloading resources so quickly. I'll keep you posted on our progress.</blockquote>This is exactly what it looked like to me the first day after GU53. The threshold at which EQ starts to free memory seems much higher than pre-lu. Before lu53 EQ always seemed to try and leave the system with (at least on my 4gb system) a couple hundred megs free RAM. Post LU it felt like EQ wasn't trying to free memory until it ran the system dry, resulting is huge slowdowns and even temprary freezes as it suddenly attempted to shift data to the page file when the space was suddenly needed instead of having room to gracefully do so.Post update today it still doesn't feel like EQ is back to pre-53 in terms of leaving itself 'wiggle room' so to speak, it just has a lower maximum threshold so u can circumvent the problem if you have enough memory to reach EQ's maximum before you run out of RAM. (As I stated earlier it seems to cap itself ~2.5gb now where before it didn't seem 2 cap at all that I could tell, or at least the cap was higher than the 3gb hardwall I was crashing at)When trying to diagnose the long-term problem I would based of what I saw tracking my RAM useage (G15 so I could watch it realtime as i zoned, ran around, etc) Look toward having EQ attempt to leave a minimum of 10% of RAM free at all times so not only will it have some space to load a new area, and then unload the old one (instead of having to freeze, unload the old, then load the new before unfreezing) .This will also hopefully solve the biggest issue that still seems present to me post-today. Even though EQ is much better, trying to launch say firefox (for example) after EQ is running still causes a massive slowdown compared to pre-lu as the game has not left enough RAM free to do so, forcing the system to have lag while it attempts a speedy purge.Exact specs on the system I am experiancing this on is; Core 2 duo e6700 (@ 3.2ghz), 4gb DDR2 800 (@960), gtx260 - 216 896mb, Win7 64.Thx for you're continued support. <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" />

Guy De Alsace

10-08-2009, 05:30 AM

I blame the Illuminati...and hamsters.

Guy De Alsace

10-08-2009, 05:36 AM

Oh - dont know if u saw this thread either Rothgar <a href="http://forums.station.sony.com/eq2/posts/list.m?topic_id=460276">http://forums.station.sony.com/eq2/...topic_id=460276</a>

cr0wangel

10-08-2009, 12:20 PM

Here my feedback after the new .exe...The memory has been reduced, I have put my graphics and textures to maximum again and I could zone to different zones, to my house, etc. It's an improvement. The memory still seems high but I can zone without crashing. The guild hall (teir2) is still a no no, if I enter my guild hall I will crash. Though zoning around and in houses seem ok now. I will need to test it more longer to see if I zone over and over what happen, I see an improvement, that's for sure but it's a pity that the guild hall are very much still bugged. Something need to be done about those.

Alienor

10-08-2009, 12:20 PM

Hmm. Did Runnyeye already got the patch? I got a new everquest2.exe today but the footprint of the game is still 1.4G. Just from the memory consumption I cannot notice any difference (playing on extreme performance). Having "only" 2GB of RAM, well....

Enever

10-08-2009, 01:05 PM

Now i'm getting nothing but Fatal Errors that are related to out of memory. I need to screenshot the error when it happens again.

Lortet

10-09-2009, 09:03 AM

I am seeing a change, but if anything it has made it worse -On loading I am seeing even larger memory use, but if left to it's own devices it crashes less than beofre - but previously I could minimise eq2 while zoning and prevent most of the crashes, and not crash while the game was minimised - now the memory loads up even when minimised and 4 crashes while zoning while minimised tonight.I have really tried it out as I have been doing the assassination quests in the betrayal so lots of zoning

Jeeshman

10-09-2009, 10:50 AM

Girlfriend's system (32 bit XP with 4G RAM) crashed last night when Xygoz was at 12%. As a result, she didn't get credit for the kill for the Trakanon access quest. She's still getting it approximately once every 30 minutes, which is the same rate she's experienced since GU53 went live.She's getting very frustrated.

MyleeSilverwings

10-09-2009, 03:54 PM

Just got the out of memory error for the first time since the 7th. This occurred when I was camping to a different character.

Lortet

10-09-2009, 07:59 PM

Further to my post above - the hotfix has definitely made it worse for me. Zoning in to any overland zone previously registered about 500K memory and our T3 guild hall about 7 - 800. Now Overland zones load up about 900K and the guild hall 1200 if I am downstairs in the transport hub or up to 1500K in the main area!Logging in to the character screen now loads up about 500K, previously less than half that.Minimising eq2 will drop overland zones instantly to about 20K then back to 200K when maximised again. Previously minimising when zoning (have to do it once the little box announcing which zone you are entering appears or you tend to get thrown out to the character screen) would have the same effect as the above minimising while in zone - ie down to 20 - 50K then up to 200K, but now there is little benefit - memory loads even when minimised - and so I get crashes while minimised and zoning now.Minimising still has some effect but needs to be used differently - need to minimise immediately before zoning, restore and click on the bell/door whatever before the current zone fully loads - once the zoning is completed, minimise/restore again and you seem to be left with one "zones worth" of memory loaded.A new problem is in that using griffons etc has become a real liability - been crashing while riding them about every second trip - trying to load new territory too fast?The rendering issues resulting from minimising and restoring appear to have been fixed however - although I would rather have the rendering issues remain and the memory issues fixed!Net effect of the hotfix - less crashes than previous if unmanaged, but far more (over double) compared to managing the zoning using minimising.

Rannc

10-09-2009, 10:17 PM

Whatever the most recent change was, on a system that never saw an out of memory error in my first 4 plus months of play, I am now crashing due to out of memory errors frequently today. I'm sorry I haven't bothered to time this but I have crashed due to out of memory errors, critical memory errors, etc. about four times this evening and so I came here to see what is going on.I read somebody's post referencing their IT experience and their request for a rollback to a stable version and the development response to this suggestion here. My experience is in software development with much of it in test engineering. I have some questions I hope one of the engineers on the project will respond to.Does EverQuest 2 have one or more known memory leaks you are working to fix now? Is that the problem here? Are you having difficulty isolating them or the circumstances that trigger them, make them worse, etc.? It certainly appears to me that the application is leaking memory like a sieve. I just watched it for about 10 minutes at idle in Windows XP task manager and observed it allocating 8k every few seconds and sometimes more, repeatedly, over and over and over. In this brief excercise I never saw the application release any memory or if it did, more was allocated within the same period of seconds in excess of whatever was freed such that total memory in use continued to rise. This 8k allocation did not appear to be consistent however as there were times I observed significantly larger memory allocations and again, never did I see memory in use decrease but always increase further. The entire brief period of time I observed this, the game was at idle and I was not interacting with it at all nor anything else on the system. I was simply watching task manager report more and more memory being allocated by an app at idle.I understand that is about as informal as testing gets but it does lend the appearance of a significant memory leak or leaks just the same. I get the impression this has nothing to do with whatever users might do in game per se other than various paths through the code will bring the ship down sooner than later. Otherwise however, if I let it sit idle long enough after logging in, I'd be willing to bet that on this system the ship will sink all by itself judging by what I just saw.I read the developer comment about how since the most recent GU the game now allocates more memory but that out of memory crashes were already a known issue. Was the known issue memory leak(s) or something else? Before the envelope was pushed here, was the garbage being taken out just often enough for users to never notice the app was having problems with memory management? Your reply made me wonder if that was the case.Testing MMO software must be among the most challenging of test scenarios there is because nowhere else have I ever seen so many broken releases go live and I am not picking just on the EQ2 team or SOE for that matter. You guys have plenty of company in this area. I often wonder just the same after a decade of testing software, how the heck some of this stuff ever makes it to release. How could something as basic as a memory error this catastrophic not have been detected during testing cycles? I really hope you guys are looking hard at how the software engineering process is breaking down repeatedly in cases like this one because clearly it is. I cannot believe that it is not humanly possible to do better than this. I think it is entirely possible. Remember the book, "Code Complete?" Has anyone written anything like it that is more current for today? If so, maybe start with buying a copy for every single engineer on this project and make it required reading and then take what is learned there into the engineering process this team operates within. If the problem is marketing driving management driving you, make them read it also.I realize that isn't easy to read but I am just measuring what I see in terms of results. The results are, once again after an update the MMO I was enjoying is broken to a point of being unplayable. I think better engineering process is possible and if marketing is driving this to ship before it is ready, then upper management needs to go back to college and learn to manage better than this, by listening to who is working for them and taking their expert opinions into account before deciding to release software that ain't ready for prime time. It has to be one or the other here. How else does one explain a decade of this?As Walter Cronkite used to say a long time ago, "That's the way it was."

Enever

10-09-2009, 10:23 PM

Received the out of Memory messages again, three of them under 2 hours. It's gotten worse.it always happens when I zone into the guildhall, or if I come from a rough lanfing from a cliff.

Lortet

10-09-2009, 10:28 PM

Done some experimenting with my crashing while on a griffon - while stationary no memory increase, riding my horse memory ticks up 1- 2 K every few seconds, riding a griffon 30 - 50K every few seconds - no wonder it crashes fast then.

Ebarel

10-10-2009, 08:18 AM

i wrote about that memory counting up (GH is worst imho) continously until you get a crit error few pages back. that hasnt changed due to the hotfixes.after setting the /3GB switch and minimizing before every zoning i can now at least reduce crashes to 1-2 per evening on my main machine. but there is a different "type" of crash now. shortly before the crash system starts slowing down very much and then suddenly freezes. moving the mose over eq2 window makes it disappear and sometimes killing the task makes the system respond (after minutes- really long time), sometimes only hard reset helps. it doesnt show an extreme memory usage during that time though.today i had also the first crash on my new "test" win 7 RC machine with crit error oom after start and logging char into guildhall after charselect. never had it happen that fast until now. that one is an empty win7 install with nothing except drivers and eq2.

MrWolfie

10-10-2009, 09:52 AM

One word for ya: Neriakbuild="SOEBuild=5949L" version="SOEVersionString=2009/10/6 16:21:34" build_type="USER OPTIMIZED" ls_address="none" zone="neriak" loc="-603.29 30.01 -22.54" performance="7" stack="00b3ca5f 009f5798 00a24fbe 00a0b3de 009fd42f 00a64fc3 00a6543a 00a4c1e3 00a4c484 00ad8a98 00572955 "

Sheira

10-10-2009, 04:21 PM

Never had a memory issue until a few days ago. Didn't have them before the hotfix, now I am getting them all the time.Is there an ETA when this is going to be fixed? It's almost impossible to play at this point.

Nicadeem

10-10-2009, 05:23 PM

Congratulations! You have now ruined the game. Whatever you have done has made this game unplayable. Four days on the trot I have been trying to complete Deathfist Citidel and four days on the trot it has crashed with an out of memory error.I cannot enter my guildhall, my house or any instance without it crashing. If I sit quietly in North Qeynos well away from anyone else then it appears stable but very, very boring.I have been playing this game since Beta and have never had this sort of crashing prior to GU53. It's a total joke.

Rothgar

10-10-2009, 06:38 PM

I would be interested to hear if running the following command:cl_force_sync_nodes 1makes a difference in your crashing problem.

tkia

10-10-2009, 07:33 PM

<cite>Rothgar wrote:</cite><blockquote>I would be interested to hear if running the following command:cl_force_sync_nodes 1makes a difference in your crashing problem.</blockquote>Since the last patch my out of memory errors have basically changed into DX out of memory errors but I'll happily test that setting if it's likely to be relevant to that sort of crash?

Lortet

10-11-2009, 07:00 PM

for the technologically inept, where do I run that command?

BroKenWingZ

10-11-2009, 09:45 PM

Before hotfix:<img src="http://www.eq2revelations.com/revftp/chidori/eq2leak.jpg" width="583" height="19" />After hotfix:<img src="http://www.eq2revelations.com/revftp/chidori/eq2leak2.jpg" />Both approx 15 hour sessions. (camping contested) I'm curious how high I can get the leak... I have 8GB to test it out. ^^I assume a better fix is in the works?edit: the image tag for this forum needs work.

Alienor

10-12-2009, 03:44 AM

<cite>Hykaree@Runnyeye wrote:</cite><blockquote>for the technologically inept, where do I run that command?</blockquote>Either put it in your eq2.ini or type in the chat /cl_force_sync_nodes 1. Remember the chat supports tab completion, ie. start with /cl_ and type the tab key to get all commands starting with that sequence

Draxknor

10-12-2009, 01:36 PM

<cite>Rothgar wrote:</cite><blockquote>I would be interested to hear if running the following command:cl_force_sync_nodes 1makes a difference in your crashing problem.</blockquote>I used it and I just crashed with 840mg left out of 2048

Enever

10-12-2009, 01:41 PM

Used the command, still had a memory leak upon zoning into a guildhall.Also this is what happened, it wasn't really a crash but it made the game unplayable.I zoned in to my guildhall from nek Castle, using my call, it finished loading it all up and then as my character apepared , the screen froze for a moment, the hotbars all transparent still transitioning from the zone. Game ran out of memory, however it didn't shut down, it made the game not fully render the UI and Models. I was able to turn and zone into South Qeynos from my guildhall and then clicked exit, due to the game not being playable. It then did an Illegal Operation, shutting the game down.I truely hope this gets fixed, the game was perfect before LU 53.

Arianah

10-12-2009, 01:58 PM

Since the memory crashes started, I've been playing on High Performance, and have been able to play from log in to log out without any crashes... until last night. Last night I crashed due to memory in my guild hall after a long day of raiding (was on High Performance all day) <img src="/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" alt="SMILEY" />

Jeeshman

10-12-2009, 04:32 PM

It's time to upgrade my emotions on this issue to "spitting mad." Girlfriend's /petition after the 'Out of Memory' error resulted in her 80 Dirge not getting a Trakanon quest update for killing Xygoz:"I was in a raid on October 8th, 2009 at approximately 10 PM CST and a minute before the raid killed Xygoz I got the "memory leak" error and as a result of the crash, I did not receive quest credit for the kill for "Taking on Trakanon." If you can, please give me credit for the kill."Aaaand here's SOE's response:"Unfortunately, connectivity is not a valid form of justification that GM's are able to use in order to update a quest for a player. If you are not present or otherwise fulfill all of the requirements to receive credit for a kill, no further assistance is available. If you believe that the mechanics should be changed, I suggest filing a /feedback on the matter and posting on the EQ II forums."Connectivity!? It wasn't "connectivity" that caused her to fail to get the quest update--she was in the fight, a minute or so before Xygoz went down she got the "Out of Memory Error" which crashed her game client. Obviously, SOE can't control sudden internet connection problems. BUT IT CAN CONTROL WHETHER IT BREAKS ITS CLIENT BY INTRODUCING CODE THAT CRASHES IT ALL THE TIME.P L E A S E F I X Y O U R B R O K E N G A M E, S O N Y.

Qaeowin

10-12-2009, 04:37 PM

I too am having these problems and cannot play. I pay for 4 accounts and if they don't fix this soon, will be cancelling them.FIX IT, SOE!!!!!!!!

EQAditu

10-12-2009, 10:45 PM

<cite>Rothgar wrote:</cite><blockquote>I would be interested to hear if running the following command:cl_force_sync_nodes 1makes a difference in your crashing problem.</blockquote>If it's a question of the setting stopping my error, the answer is no.It's hard to create a test case as it only seems to work with a lot of people around. So I zone like a dozen times by myself with no trouble... but if I follow my guild to two different raid zones... it will probably try crashing midway through the second.

Lortet

10-13-2009, 07:23 AM

Sick of this - crashing even more often and now more crashes probably due to the new nvidia drivers - almost unplayable now - LU53 hasn't been much of an experience!

Rannc

10-13-2009, 10:30 AM

My most recent crash this morning was a DirectX error which was something new.I had tried someone's suggestion to reduce textures to medium and of course, that allowed me to play longer before the game would eventually run out of memory.I thought you said you had a reproducible test case in house. If you do, why do you need end users to test for you?How hard is it on a reproducible case to live in a hardware debugger until you isolate this, and then you can correct it? You guys do have a hardware debugger and someone who knows how to use it I hope? lolIt blows my mind you'd even mention a streaming edition of EQ2, ala Free Realms, in this thread when you currently have a game so broken some users are unable to play it. Can you please fix what is and has been broken for some time before working on anything else, including game updates, streaming launchers, and expansions for that matter and then test each of those releases a lot better than you did this one? Is that really too much to ask?

Evil Gandhi

10-13-2009, 11:51 AM

Just adding my name to the list of disgruntled customers... GU53 has decimated my game enjoyment because of this memory issue. I signed up at launch and have never been close to being dissatisfied with the game until now. I've crashed in the Kurn's suit and ruined an Ione pull. I've routinely crashed at crunch times in dang near every raid zone. I crash soloing. I crash doing nothing. I've crashed more since 53 than in all my previous time online up to then. Seeing another patch go in today with no fix is killing me. This can't wait for the "weekly" updates either.Please fix this. Sooner rather than later.Thanks.

Kizaxia

10-13-2009, 12:14 PM

I consider myself a loyal customer to SoE and what use to be Verant after playing EverQuest for 6 years and then EQ2 for 4 years.Not once in the 4 years of playintg EQ2 have i ever ever had a Client Crash until GU53. After crashing 5 to 6 times a night andespecially when it counts during a raid I have almost but given up playing this game. Its to frustrating to try and play when you crashall the time. I have even gotten the out of memory error doing absolutley nothing. Logged in, already in our guild hall and just standingthere chatting and browsing the broker, 20 minutes in game and crash out of memory error. There is no special codition that I haveseen that triggers this eror, its solo, its grouping , its Raiding , its zoning, its doing ABSOLUTLEY NOTHING !!! that this happens.I havnt logged in for almost 11 days now and since then have picked up Aion. This game at least isnt crashing and is fun to play.Since i'm not going to pay for 2 EQ2 accounts for me and my wife and 2 Aion accounts for me and my wife I hope this gets fixed soonso I can figure out whos getting my Money !!SystemGigabyte MA790GP-UD4H MotherboardAMD Phenom 9950 Quad Core CPU4 X 1 gig Corsair XMS2 PC 6400 ram sticksPNY Nvidia 9800 GTX w/ 1 gig DDR3 RamWindows XP OS

Tro

10-13-2009, 12:51 PM

The hotfix was supposed to go out this morning at 9am EST and was wondering if it actually went live and if so has that fixed the memory crash issue..Anyone?

Gaige

10-13-2009, 01:10 PM

Last night within 1 hour of logging in my EQ2 client was using over 3GB of ram. It was amazing.

Evil Gandhi

10-13-2009, 02:02 PM

<cite>Talsmar@Crushbone wrote:</cite><blockquote>The hotfix was supposed to go out this morning at 9am EST and was wondering if it actually went live and if so has that fixed the memory crash issue..Anyone?</blockquote>No. It is not fixed.

Jimako

10-13-2009, 03:10 PM

I havent checked here for a while, well because i got fed up weeks ago and stopped playing. I got flamed when i said all hotfixes and such should be put on hold while this is resolved *correctly*. Each day more and more upset users are posting here. I still stand by what i said. This issue is huge and wont get any better if more and more hotfixes are pushed out while this is ignored.The only workaround i know of is to reduce your performance to that of High Performance or less. This will significantly reduce your memory footprint, at the expense of eye-candy. For those people (myself included) who like to have dedicated gamer systems this is a slap in the face. For those people who want to buy a dedicated PC just for EQ2 - dont. Until this is resolved you will be extremely disappointed trust me.

Serian

10-13-2009, 05:21 PM

<cite>Jimako wrote:</cite><blockquote>For those people (myself included) who like to have dedicated gamer systems this is a slap in the face.</blockquote>LOL on a off note Slap in the face card... /failOn to reality, While this is annoying almost to the extreme to me (I 3box on one comp, atm can only run one char at a time) Im dealing with it and so should you Jimako. Im keeping informed as you should but coming on here and ranting helps no one, rants are for eq2flames so head there IMHO. Anyways I, as all do, hope this is resolved soon, and no the fix for the issue did not go in this morning, Im still using 2.5 gigs of memory to run a single instance. Seri~

Collin_Rowanstaff

10-13-2009, 05:29 PM

For me running in windowed mode on low settings has solved this problem. Yay for crappy graphics and a blue border. But I can at least play.For my family's other 3 accounts (wife and kids) this bug has become beyond a problem. it has comepletely quashed all their game time. This is ludicrous. Allow me to explain.My wife and I run nearly identical systems. XP, 3 gig of ram, Nvidia 8500 GT with 512 RAM, dual core 3.0 ghz Pentium Duo processors running at 1333, intel motherboards, ASUS Xonar DX sound cards, Logitech 5.1 speakers. The only real difference is she uses her older EIDE hard drives; I use newer SATA drives. So we should be comparable performance, right?XWrong answer!I started getting crashes in any overland, highly populated, or item heavy (read house or guild hall) zones. So did she. I turned down my settings and went into windowed mode. Problem solved. She did likewise. Now she crashes at startup. When she doesn't she plays and, no matter what zone she is in, her framerate slows to a crawl (3-10 fps) after 1 to 5 minutes. Her system frame lags beyond all playability. Her memory usage for EQ2 jumps from 500,000k to over 1.3 million k. It may crash, it may not, at some point after that, but it doesn't matter.Ditto her results for my kids, whose computer is a generation behind hers and mine.Her game is unplayable. Her and I have been playing this game with great settings, in full screen since I upgraded our rigs in February. This update has ended that. I can't play with my wife and kids.BTW, she ran a support ticket and went through a lot of hoops for the customer support department to hope against hoep that something would solve this. In the end the CS rep blamed HER for her frame issues. She didn't doa clean boot (she did), she doesn't have a decent system (she does), she didn't turn down her settings enough (to bare minimum, I helped her do it), so it's not CS's problem. She is really upset at your CS department and has started talking about canceling all of our accounts and going to "the competition." I've told her to wait a bit longer, give SOE a chance to address what is a growing issue.She and I have both played EQ2 since its release. She was in beta. Neither of us wants to leave. However, we must have a game we can play together or it's not the game we want. C'mon SOE, help us stay your loyal fans. Fix this.

Draxknor

10-13-2009, 11:56 PM

I tried your new command line... still crashes, as much as before.Now I'm using the FreeRam program listed on page 11... and now I crash a lot less,.. but I still do sometimes.Sometimes the RAM goes down so quickly that the program cant keep up and I crash...On idle with almost nothing open, I have 2047 Mg free... when I play EQ, I have about 1300 to 1100 Mg... and I crash when i get around 850 to 900 MgI've been playing on the same setting for months now... I uses RAID settings, normal GROUP settings and high quality settings... and I crash in every one of them.

Tro

10-14-2009, 08:23 AM

<cite>Jimako wrote:</cite><blockquote>I havent checked here for a while, well because i got fed up weeks ago and stopped playing. I got flamed when i said all hotfixes and such should be put on hold while this is resolved *correctly*. Each day more and more upset users are posting here. I still stand by what i said. This issue is huge and wont get any better if more and more hotfixes are pushed out while this is ignored.The only workaround i know of is to reduce your performance to that of High Performance or less. This will significantly reduce your memory footprint, at the expense of eye-candy. For those people (myself included) who like to have dedicated gamer systems this is a slap in the face. For those people who want to buy a dedicated PC just for EQ2 - dont. Until this is resolved you will be extremely disappointed trust me.</blockquote>I am 100% sure this problem is not being ignored.. as frustrating as it is, all we can do is wait. Just be patient and I am sure they will get it fixed..I would think SoE would at the very least provide some sort of compensation back to folks that are severely impacted by this GU. Why should they pay if they can't play I mean this is not a 1 or 2 day problem.. It has been quite some time now.Anyway hopefully the fix will be sooner than later..

MrWolfie

10-14-2009, 11:23 AM

I have 2 installations of EQ2. One runs in full screen high quality, 1920x1200 - the other, windowed in extreme performance 1440x800. That's the absolute minimum graphically, no shaders, no shadows, no particle effects at all. Normally, I use this instance of EQ2 to run two accounts simultaneously.I was running the extreme performance installation earlier today, only one instance of it, and Windows popped an alert in the taskbar tray today that it was going to increase the paging file because, for the first time in as long as I've been running this PC, a 2gb paging file wasn't enough!Yup, EQ2 was using nearly 3gb of paging file.What monumental task must I have been doing?I was crafting in my guild hall.

Dawnya

10-14-2009, 08:19 PM

Yeah still gettin the crash too... runnin at 72% of my 3 gigs right now... only thing open.. EQ2 and this browser window <img src="/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" alt="SMILEY" />

Lortet

10-14-2009, 11:17 PM

Did something undisclosed sneak through on yesterdays hotfix? - played for several hours multiple zoning and no crash, memory use did not climb as it has done since LU53. The day before I would have crashed 5 - 6 times even if minimising every 10 minutes, yesterday no minimising needed.

Inferius

10-15-2009, 05:57 AM

I just transfered from Nektulos to splitpaw and noticed the performance improved immensly first i thought maybe Splitpaw server was in better shape than Nek but maybe something did change.I am loading faster and getting no hitching at all hardly.Either way i say "YAY!!!" because I had fun playing eq2 last night for the first time since gu53 went live. Also another trick I just read about on another forum thread here was to disable Font smoothing,options>user interface>game windows>uncheck font smooth box, This upped my frame rate by at least 20 even after i upped my texture detail.Basically it sets your game text to old school eq2 type which is a bit thin and can be hard to read sometimes but hey 20 fps is 20 fps.

Siddartha

10-15-2009, 11:20 AM

tap tap tap, is this thing on?Is there anyone out there that can give an update on the fix to this memory issue?I'm waiting... ohhINC cut and paste answer that is SoE, if we get an answer at all =/

Collin_Rowanstaff

10-15-2009, 06:49 PM

UPDATE: I fixed my wife's computer. It runs EQ2 again.The fan on her video card was going bad, it was causing her vid card to stop running smoothly. I instlalled my old ATI Radeon 2600 XT and now she can play again. Not in super awesome mode, but we can play together. YAY!

Lortet

10-15-2009, 08:55 PM

Thought it was totally better but the T3 guild hall got me - memory shot up and crash. Had zoned probably 12 - 15 times before that without problem.I'm now getting another crash - if I leave my PC at the character log in EQ2 promptly crashes with a Windows "sorry we had to close" message. This one seemingly since downloading the new NVidia drivers for my 8800GT card, but there have also been two quite large XP updates since then as well.

Thronk

10-15-2009, 09:23 PM

After GU53 I was crashing about every 3 hours, after the most recent patch I crash about every 3 minutes. Nice job SOE! <img src="/eq2/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" />

Yarginis

10-16-2009, 07:01 AM

Issue seems to be getting much worse again slowly. Although I'm not getting the crash anymore, EQ2 is back to using more memory than ever before.Here's a screenshot taken earlier today standing around Jarsath Wastes docks. This was after being in raid for 3+ hours, probably 5 hours or so total time logged in.<img src="http://www.yargnit.com/download/eq23gb+.jpg" width="415" height="463" />As you can see, I've got EQ2 up to 3.125gb there, and it was actually at 3.15 but dropped 25mb before I could get screenshot off.While it's good news that it's not crashing at 3gb anymore, the fact that it's actually useing over 3gb now (and practically freezing any other programs that may be running due to starving them of memory) is certianly not good.Please take another look at this memory leak compared to pre-gu53 and try to sort out what changed so drastically, a 5yr old game chewing through this much memory is crazy, and almost certain to drive people with lower end systems away if it continues.Thx again Roth. <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" />

Foolsfolly

10-16-2009, 07:31 PM

I got a Blue Screen of Death after playing for about 10 minutes today.Immediately after I logged in I started running the trick-or-treat event. As I went around North Qeynos hailing NPC's, I quickly started to notice them failing to render properly, then suddenly everything went blue.I've run this quest dozens of times every previous year. Now I'm sad that I'll have to avoid it this year =[Edit: Finished my first day of Nights of the Dead with 2 blue-screens, 3 out-of-memory crashes. Much worse than any day I've had since the last attempted fix went in.

MrWolfie

10-17-2009, 10:23 AM

Logged in direct to NQ, Haunted House, NQ, Guild Hall, SF, LP, Haunted House, LP, Haunted House, GH, Nek, Hollow Hedge.As I was zoning into Hollow Hedge, the graphics on the loading screen were blank.I checked my task manager. EQ was using 1.4gb of ram and 2.2gb of paging file. I minimised EQ2 and waited a few seconds, I then went to maximise EQ2 and it crashed to desktop. Crashlog follows:SOEBuild=5968LSOEVersionString=2009/10/12 19:03:56EVERQUEST2 CRASH LOG=============================================== ================================================== =Unhandled exception EXCEPTION_ACCESS_VIOLATION at 0x4FE4B48CApplication was trying to read from 0x00000000 Region Begins At: 0x00000000 Region Ends At: 0x00010000 Region Size Is: 0x00010000 bytes Memory Protection: PAGE_NOACCESS (00000001) Memory State: MEM_FREE Memory Type: FreeGame Data: SOEBuild: SOEBuild=5968L SOEVersionString: SOEVersionString=2009/10/12 19:03:56 OS Version: 5.1.2600 Service Pack 3 VER_NT_WORKSTATION CPU: 2 x86 GenuineIntel 2400MHz RDTSC MSR CMPXCHG8 SSE SSE2 DirectX Version: 9.0c Video Card/Driver: [NVIDIA GeForce GTX 260] [nv4_disp.dll] 6.14.11.9038 {d7b71e3e-46a2-11cf-2050-852600c2cb35} Time at crash: Sat Oct 17 14:14:49 2009 Login Server: none Performance: 7 Game Uptime: 2939 seconds Position last frame: 884.63, 8.56, -473.94 Zone name: live_haunted_cauldroncove Time in Zone: 57 seconds Previous Zone name: GameScene::ZR_NETWORKED_ZONE_CHANGE Multi-core support: enabled Low-Memory Mode: disabledLog: Received chat channel update msg... Received chat channel update msg... Received chat channel update msg... Received chat channel update msg... Received chat channel update msg... Received chat channel update msg... Received chat channel update msg... Received chat channel update msg... Received chat channel update msg... Received chat channel update msg...Thread Data: Primary Thread Id: 1604 Current Thread Id: 1604 Current Thread Priority: 0Memory: AddressLimitMB: 2048 Load: 90% Total physical: 2145890304 Free physical: 197115904 Total pagefile: 4294967295 Free pagefile: 2821816320 Total virtual: 2147352576 Free virtual: 48611328Memory Manager: Allocations: 318430 Bytes Allocated: 612418128 Max Allocations: 368252 Max Bytes Allocated: 864054304 System Memory Allocated (MB): 828 Limit: 1534 Number of Allocate Calls: 3915136 Number of Free Calls: 3596706Registers: EAX 0x0013F574 EBX 0x00000000 ECX 0x001B5584 EDX 0x001B5584 ESI 0x001B5580 EDI 0x00000000 GS 0x00000000 FS 0x0000003B ES 0x00000023 DS 0x00000023 EBP 0x0013F55C ESP 0x0013F554 EIP 0x4FE4B48C FLAGS 0x00010246 CS 0x0000001B SS 0x00000023FPU Registers: CW 0xFFFF027F SW 0xFFFF0000 TW 0xFFFFFFFFFPU Rounding Mode: NearestCall Stack: 0x4FE4B48C: Direct3DShaderValidatorCreate9+1badc 0x4FE62173: Direct3DShaderValidatorCreate9+327c3 0x009D6380 in E:EverQuest IIEverQuest2.exe 0x009D63FA in E:EverQuest IIEverQuest2.exe 0x0040EB0D in E:EverQuest IIEverQuest2.exeEnd of Call StackStack Scan: 0x0013F554: 0x00000000 0x0013F558: 0x001B5580 0x0013F55C: 0x0013F5A4 0x0013F560: 0x4FE62173, in C:WINDOWSsystem32d3d9.dll (0x4fdd0000) 0x0013F564: 0x0013F574 0x0013F568: 0x00000000 0x0013F56C: 0x01D9AE80 0x0013F570: 0x8007000E 0x0013F574: 0x00000000 0x0013F578: 0x00000000 0x0013F57C: 0x001B5580 0x0013F580: 0x00000000 0x0013F584: 0x00010000 0x0013F588: 0x00000000 0x0013F58C: 0x001B5584 0x0013F590: 0x00000000 0x0013F594: 0x0013F568 0x0013F598: 0x0013F690 0x0013F59C: 0x4FF51B28, in C:WINDOWSsystem32d3d9.dll (0x4fdd0000) 0x0013F5A0: 0x00000000 0x0013F5A4: 0x0013F69C 0x0013F5A8: 0x009D6380, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F5AC: 0x001B5584 0x0013F5B0: 0x00000000 0x0013F5B4: 0x01D9BC18 0x0013F5B8: 0x00000000 0x0013F5BC: 0x000000E3 0x0013F5C0: 0x00000000 0x0013F5C4: 0x01D9BC18 0x0013F5C8: 0x0013F5D8 0x0013F5CC: 0x0D8B4EA0 0x0013F5D0: 0x00000005 0x0013F5D4: 0x0013F62C 0x0013F5D8: 0x4FE18D81, in C:WINDOWSsystem32d3d9.dll (0x4fdd0000) 0x0013F5DC: 0x00000018 0x0013F5E0: 0x0013E14C 0x0013F5E4: 0x00000006 0x0013F5E8: 0x00000001 0x0013F5EC: 0x0000001C 0x0013F5F0: 0x08000001 0x0013F5F4: 0x0013E14C 0x0013F5F8: 0x00000006 0x0013F5FC: 0x00000006 0x0013F600: 0x00000000 0x0013F604: 0x00000018 0x0013F608: 0x0013F624 0x0013F60C: 0x001B5580 0x0013F610: 0x001B5584 0x0013F614: 0x00000001 0x0013F618: 0x00000001 0x0013F61C: 0x00000015 0x0013F620: 0x00000000 0x0013F624: 0x00000000 0x0013F628: 0x08000001 0x0013F62C: 0x0013F660 0x0013F630: 0x4FE11E20, in C:WINDOWSsystem32d3d9.dll (0x4fdd0000) 0x0013F634: 0x001B5580 0x0013F638: 0x00000100 0x0013F63C: 0x00000001 0x0013F640: 0x4FDF5E25, in C:WINDOWSsystem32d3d9.dll (0x4fdd0000) 0x0013F644: 0x001B5584 0x0013F648: 0x00000000 0x0013F64C: 0x4FE11E2D, in C:WINDOWSsystem32d3d9.dll (0x4fdd0000) 0x0013F650: 0x01D3A818 0x0013F654: 0x3DA03250 0x0013F658: 0x3DA03485 0x0013F65C: 0x3DA03486 0x0013F660: 0x00000000 0x0013F664: 0x00353176, in E:EverQuest IIjs3250.dll (0x00340000) 0x0013F668: 0x00000000 0x0013F66C: 0x00000000 0x0013F670: 0x50199570 0x0013F674: 0x501997A5 0x0013F678: 0x501997A6 0x0013F67C: 0x00000000 0x0013F680: 0x01D9AE86 0x0013F684: 0x00000000 0x0013F688: 0x00B2F040, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F68C: 0x00000010 0x0013F690: 0x0013F7A4 0x0013F694: 0x00E73F16, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F698: 0xFFFFFFFF, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F69C: 0x0013F6D4 0x0013F6A0: 0x009D63FA, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F6A4: 0x01B2F040 0x0013F6A8: 0x029E5140 0x0013F6AC: 0x009DB289, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F6B0: 0x04770780 0x0013F6B4: 0x029E0090 0x0013F6B8: 0x00000000 0x0013F6BC: 0x009DB3C7, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F6C0: 0x029E0090 0x0013F6C4: 0x01B238F0 0x0013F6C8: 0x00000002 0x0013F6CC: 0x00000780 0x0013F6D0: 0x00000477 0x0013F6D4: 0x00000005 0x0013F6D8: 0x0040EB0D, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F6DC: 0x00000001 0x0013F6E0: 0x00000477 0x0013F6E4: 0x00000001 0x0013F6E8: 0x00150132 0x0013F6EC: 0x00000002 0x0013F6F0: 0x00417BA5, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F6F4: 0x00417FD3, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F6F8: 0x0013F788 0x0013F6FC: 0x00417A80, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F700: 0x0013F74C 0x0013F704: 0x00000000 0x0013F708: 0x00000001 0x0013F70C: 0x0000001E 0x0013F710: 0x00000007 0x0013F714: 0x00000004 0x0013F718: 0x0013F7CC 0x0013F71C: 0x0013F7E8 0x0013F720: 0x00000043 0x0013F724: 0x7E418734, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F728: 0x00150132 0x0013F72C: 0x00000005 0x0013F730: 0x00000002 0x0013F734: 0x04770700 0x0013F738: 0x00417A80, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F73C: 0xDCBAABCD, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F740: 0x00000000 0x0013F744: 0x0013F788 0x0013F748: 0x00417A80, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F74C: 0x0013F7B4 0x0013F750: 0x7E418816, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F754: 0x00417A80, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F758: 0x00150132 0x0013F75C: 0x00000005 0x0013F760: 0x00000002 0x0013F764: 0x04770780 0x0013F768: 0x00000000 0x0013F76C: 0x00150132 0x0013F770: 0x04770780 0x0013F774: 0x00000014 0x0013F778: 0x00000001 0x0013F77C: 0x00000000 0x0013F780: 0x00000000 0x0013F784: 0x00000010 0x0013F788: 0x00000000 0x0013F78C: 0x7E42B401, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F790: 0x00000000 0x0013F794: 0x00000000 0x0013F798: 0x00000000 0x0013F79C: 0x0013F768 0x0013F7A0: 0x0013F178 0x0013F7A4: 0x0013F7F8 0x0013F7A8: 0x7E44048F, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F7AC: 0x7E418830, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F7B0: 0x00000000 0x0013F7B4: 0x0013F808 0x0013F7B8: 0x7E428EA0, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F7BC: 0x00000000 0x0013F7C0: 0x00417A80, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F7C4: 0x00150132 0x0013F7C8: 0x00000005 0x0013F7CC: 0x00000002 0x0013F7D0: 0x04770780 0x0013F7D4: 0x0157F17C 0x0013F7D8: 0x00000001 0x0013F7DC: 0x00000002 0x0013F7E0: 0x0157F168 0x0013F7E4: 0x04770780 0x0013F7E8: 0x00000000 0x0013F7EC: 0x00000000 0x0013F7F0: 0x0013F7DC 0x0013F7F4: 0x0013F178 0x0013F7F8: 0x0013F8FC 0x0013F7FC: 0x7E44048F, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F800: 0x7E428EB0, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F804: 0xFFFFFFFF, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F808: 0x0013F830 0x0013F80C: 0x7E428EEC, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F810: 0x0157F168 0x0013F814: 0x00000005 0x0013F818: 0x00000002 0x0013F81C: 0x04770780 0x0013F820: 0x00417A80, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F824: 0x00000000 0x0013F828: 0x00000000 0x0013F82C: 0x00000000 0x0013F830: 0x0013F8A8 0x0013F834: 0x7C90E473, in C:WINDOWSsystem32ntdll.dll (0x7c900000) 0x0013F838: 0x0013F840 0x0013F83C: 0x00000018 0x0013F840: 0x0157F168 0x0013F844: 0x00000005 0x0013F848: 0x00000002 0x0013F84C: 0x04770780 0x0013F850: 0x00417A80, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F854: 0x7E428E53, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F858: 0x7E4194BE, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F85C: 0x7E42F5C6, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F860: 0x00150132 0x0013F864: 0x00000005 0x0013F868: 0x00000002 0x0013F86C: 0x04770780 0x0013F870: 0x00000000 0x0013F874: 0x000002B0 0x0013F878: 0x00000001 0x0013F87C: 0x0013FA78 0x0013F880: 0x00150132 0x0013F884: 0x00000000 0x0013F888: 0x00000000 0x0013F88C: 0x00000000 0x0013F890: 0x00000000 0x0013F894: 0x00000780 0x0013F898: 0x00000477 0x0013F89C: 0x0B01079F 0x0013F8A0: 0x00000001 0x0013F8A4: 0x7E42C1E9, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F8A8: 0x0013F8C4 0x0013F8AC: 0x7E42C228, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F8B0: 0x00150132 0x0013F8B4: 0x00000047 0x0013F8B8: 0x00150132 0x0013F8BC: 0x00000002 0x0013F8C0: 0x00000001 0x0013F8C4: 0x0013F90C 0x0013F8C8: 0x7E42C1D5, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F8CC: 0x00150132 0x0013F8D0: 0x00000047 0x0013F8D4: 0x00000000 0x0013F8D8: 0x0013FA78 0x0013F8DC: 0x0013FA78 0x0013F8E0: 0x00150132 0x0013F8E4: 0x00000000 0x0013F8E8: 0x00000000 0x0013F8EC: 0x00000000 0x0013F8F0: 0x7E42C1E9, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F8F4: 0x0013F8DC 0x0013F8F8: 0x0013F178 0x0013F8FC: 0x0013F9D0 0x0013F900: 0x7E44048F, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F904: 0x7E42C1F0, in C:WINDOWSsystem32USER32.dll (0x7e410000) 0x0013F908: 0x00000000 0x0013F90C: 0x00000047 0x0013F910: 0x00417FA4, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F914: 0x00150132 0x0013F918: 0x00000047 0x0013F91C: 0x00000000 0x0013F920: 0x0013FA78 0x0013F924: 0x0013F9B4 0x0013F928: 0x00417A80, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F92C: 0x0013F978 0x0013F930: 0x00000000 0x0013F934: 0x00000001 0x0013F938: 0x00000000 0x0013F93C: 0x0013F9CC 0x0013F940: 0x00417A80, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F944: 0x00417A80, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F948: 0x00000000 0x0013F94C: 0x00000000 0x0013F950: 0x7E418734, in C:WINDOWSsystem32USER32.dll (0x7e410000)End of Stack ScanEND OF LOG

MurFalad

10-17-2009, 04:35 PM

I've just had my first memory error crash, oddly enough the only thing I've added recently to EQ2 was DragonWolfs auto attack timer (today) which makes me suspicious as until today I've never run with a custom UI of any kind. Although I find it hard to believe that it could add up to that serious an amount of memory.The crash was as follows<img src="http://i950.photobucket.com/albums/ad345/EddieLomax/EQ2Crash.jpg?t=1255807695" width="1024" height="768" />I'm running Windows 7 RC 64 bit (not patches or anything added), and the error occured probably after about 3-4 hours of running, swapping characters a few times. No raiding and only grouped up once with one person to tradeskill something for them. As you can see from the process manager that was pretty much what I was running at the time (minus paint which I used just for the screenshot, screen shot looks weird because I've got a paint behind it that I wanted to redo with the process manager in the picture properly).Settings on EQ2 are all on extreme with GPU shadows turned on and water reflections set to one per a frame.Hardware is a PhenonII X4 955 @3.2Ghz and 4Gb ram with a ATI Radeon 4870 1Gb graphics card.The crash log to follow (I've exceeded the maximum posting size <img src="/eq2/images/smilies/8a80c6485cd926be453217d59a84a888.gif" border="0" /> )

MurFalad

10-17-2009, 04:36 PM

---------------------------------------SOEBuild=5968LSOEVersionString=2009/10/12 19:03:56EVERQUEST2 CRASH LOG=============================================== ================================================== =Unhandled exception EXCEPTION_ACCESS_VIOLATION at 0x00B3CB0FApplication was trying to write to 0x00000002 Region Begins At: 0x00000000 Region Ends At: 0x00010000 Region Size Is: 0x00010000 bytes Memory Protection: PAGE_NOACCESS (00000001) Memory State: MEM_FREE Memory Type: FreeGame Data: SOEBuild: SOEBuild=5968L SOEVersionString: SOEVersionString=2009/10/12 19:03:56 OS Version: 6.1.7100 VER_NT_WORKSTATION CPU: 4 x86 AuthenticAMD 3MHz RDTSC MSR CMPXCHG8 SSE SSE2 DirectX Version: 10.0 Video Card/Driver: [ATI Radeon HD 4800 Series ] [atiumdag.dll] 8.14.10.678 {d7b71ee2-d700-11cf-5d76-1ec1a1c2c535} Time at crash: Sat Oct 17 20:21:12 2009 Login Server: none Performance: 7 Game Uptime: 21445 seconds Position last frame: -2056.12, -38.28, 389.47 Zone name: antonica Time in Zone: 1950 seconds Previous Zone name: GameScene::ZR_NETWORKED_ZONE_CHANGE Multi-core support: enabled Low-Memory Mode: disabledLog: E:liveeq2frameworkrendersrcRenderContext.cpp(1777) : Error loading texture "*MEM TEXTURE*" Received chat channel update msg... Received chat channel update msg... Received chat channel update msg... Received chat channel update msg... Received chat channel update msg... E:liveeq2frameworkrendersrcMemTexture.cpp(114): Cannot retrieve mipmaps: no CPU copy Received chat channel update msg... Received chat channel update msg... E:liveeq2frameworkmemoryManagersrcsharedMemoryMana ger.cpp(2010): Application ran out of memory when requesting 7680016 bytes (limit: 3069 MB, current: 896 MB)Thread Data: Primary Thread Id: 2848 Current Thread Id: 2848 Current Thread Priority: 0Memory: AddressLimitMB: 4095 Load: 78% Total physical: 4292075520 Free physical: 907427840 Total pagefile: 4294967295 Free pagefile: 3034669056 Total virtual: 4294836224 Free virtual: 521420800Memory Manager: Allocations: 304150 Bytes Allocated: 737871120 Max Allocations: 364599 Max Bytes Allocated: 923421664 System Memory Allocated (MB): 896 Limit: 3069 Number of Allocate Calls: 12261491 Number of Free Calls: 11957341Registers: EAX 0x00000001 EBX 0x000005C5 ECX 0x000005C4 EDX 0x0040EC41 ESI 0x75F8FAD6 EDI 0x00753010 GS 0x0000002B FS 0x00000053 ES 0x0000002B DS 0x0000002B EBP 0x00000000 ESP 0x0018F3C4 EIP 0x00B3CB0F FLAGS 0x00010246 CS 0x00000023 SS 0x0000002BFPU Registers: CW 0x0000027F SW 0x0000403F TW 0x0000FFFFFPU Rounding Mode: NearestCall Stack:Frame 0: Invalid stack frame: Can't be readEnd of Call StackStack Scan: 0x0018F3C4: 0x00000000 0x0018F3C8: 0x6C707041 0x0018F3CC: 0x74616369 0x0018F3D0: 0x206E6F69 0x0018F3D4: 0x206E6172 0x0018F3D8: 0x2074756F 0x0018F3DC: 0x6D20666F, in C:WindowsAppPatchAcGenral.DLL (0x6d0a0000) 0x0018F3E0: 0x726F6D65, in C:WindowsSysWOW64dxdiagn.dll (0x726d0000) 0x0018F3E4: 0x68772079 0x0018F3E8: 0x72206E65 0x0018F3EC: 0x65757165 0x0018F3F0: 0x6E697473 0x0018F3F4: 0x36372067 0x0018F3F8: 0x31303038 0x0018F3FC: 0x79622036 0x0018F400: 0x20736574 0x0018F404: 0x6D696C28 0x0018F408: 0x203A7469 0x0018F40C: 0x39363033 0x0018F410: 0x2C424D20 0x0018F414: 0x72756320 0x0018F418: 0x746E6572 0x0018F41C: 0x3938203A 0x0018F420: 0x424D2036, in C:Windowssystem32MacromedFlashNPSWF32.dll (0x424d0000) 0x0018F424: 0x6AFE0029, in C:Windowssystem32d3d9.dll (0x6afe0000) 0x0018F428: 0x0018F438 0x0018F42C: 0x3C4DED80 0x0018F430: 0x6AFE678A, in C:Windowssystem32d3d9.dll (0x6afe0000) 0x0018F434: 0x04F66180 0x0018F438: 0x3C4DECE0 0x0018F43C: 0x3C4DECE0 0x0018F440: 0x00000000 0x0018F444: 0x00000000 0x0018F448: 0x04F68AE8 0x0018F44C: 0x04F68EEC 0x0018F450: 0x000004B0 0x0018F454: 0x3C4DED80 0x0018F458: 0x04F66184 0x0018F45C: 0x0018F494 0x0018F460: 0x00000000 0x0018F464: 0x00000000 0x0018F468: 0x00000640 0x0018F46C: 0x000004B0 0x0018F470: 0x00000000 0x0018F474: 0x00000000 0x0018F478: 0x00000640 0x0018F47C: 0x000004B0 0x0018F480: 0x00000015 0x0018F484: 0x00000001 0x0018F488: 0x08000001 0x0018F48C: 0x00000004 0x0018F490: 0x00000000 0x0018F494: 0x00000000 0x0018F498: 0x00000640 0x0018F49C: 0x000004B0 0x0018F4A0: 0x00000015 0x0018F4A4: 0x00000001 0x0018F4A8: 0x00000001 0x0018F4AC: 0x00000000 0x0018F4B0: 0x00000000 0x0018F4B4: 0x00000000 0x0018F4B8: 0x00000640 0x0018F4BC: 0x0018027F 0x0018F4C0: 0x0018F4E8 0x0018F4C4: 0x009B9617, in D:ProgramsEQ2EverQuest2.exe (0x00400000) 0x0018F4C8: 0x44160000 0x0018F4CC: 0x011989D4, in D:ProgramsEQ2EverQuest2.exe (0x00400000) 0x0018F4D0: 0x0018F584 0x0018F4D4: 0x01198974, in D:ProgramsEQ2EverQuest2.exe (0x00400000) 0x0018F4D8: 0x00000001 0x0018F4DC: 0x00000000 0x0018F4E0: 0x00000000 0x0018F4E4: 0x00000000 0x0018F4E8: 0x00000640 0x0018F4EC: 0x000004B0 0x0018F4F0: 0x0018F504 0x0018F4F4: 0x6AFE6BC5, in C:Windowssystem32d3d9.dll (0x6afe0000) 0x0018F4F8: 0x04F661B4 0x0018F4FC: 0x00000000 0x0018F500: 0x3A03141C 0x0018F504: 0x04F661B4 0x0018F508: 0x3F61C598 0x0018F50C: 0x3EF15AEA 0x0018F510: 0xBF800000 0x0018F514: 0x00000000 0x0018F518: 0x00000000 0x0018F51C: 0x3F61C598 0x0018F520: 0x3EF15AEA 0x0018F524: 0x00000000 0x0018F528: 0x00000000 0x0018F52C: 0xBF61C598 0x0018F530: 0x3EF15AEA 0x0018F534: 0x00000000 0x0018F538: 0x42160000 0x0018F53C: 0xBF4B1934 0x0018F540: 0x00000000 0x0018F544: 0x3F1BD7CA 0x0018F548: 0x05035980 0x0018F54C: 0x00000000 0x0018F550: 0xBF61C598 0x0018F554: 0x3EF15AEA 0x0018F558: 0x3EF15AEA 0x0018F55C: 0x0018F598 0x0018F560: 0x009B9769, in D:ProgramsEQ2EverQuest2.exe (0x00400000) 0x0018F564: 0xC1E10000 0x0018F568: 0x0018F624 0x0018F56C: 0x01198A28, in D:ProgramsEQ2EverQuest2.exe (0x00400000) 0x0018F570: 0x011989E8, in D:ProgramsEQ2EverQuest2.exe (0x00400000) 0x0018F574: 0x00000000 0x0018F578: 0x00000000 0x0018F57C: 0xBF800000 0x0018F580: 0xC4FA0000 0x0018F584: 0x00000000 0x0018F588: 0x77A7F861, in C:WindowsSysWOW64ntdll.dll (0x77a60000) 0x0018F58C: 0x7666E974, in C:Windowssyswow64KERNELBASE.dll (0x76660000) 0x0018F590: 0x00000460 0x0018F594: 0x00000000 0x0018F598: 0x7666E9A7, in C:Windowssyswow64KERNELBASE.dll (0x76660000) 0x0018F59C: 0xB8F3CF82 0x0018F5A0: 0x0018F660 0x0018F5A4: 0x00000460 0x0018F5A8: 0x12704E6C 0x0018F5AC: 0x00000024 0x0018F5B0: 0x00000001 0x0018F5B4: 0x00000000 0x0018F5B8: 0x00000000 0x0018F5BC: 0x00000000 0x0018F5C0: 0x00000000 0x0018F5C4: 0x00000000 0x0018F5C8: 0x00000000 0x0018F5CC: 0x00000000 0x0018F5D0: 0x3ECDECBA 0x0018F5D4: 0x3C1B9E36 0x0018F5D8: 0x00000000 0x0018F5DC: 0x0018F59C 0x0018F5E0: 0xBECDDE06 0x0018F5E4: 0x0018F954 0x0018F5E8: 0x76694000, in C:Windowssyswow64KERNELBASE.dll (0x76660000) 0x0018F5EC: 0xCE8262FE 0x0018F5F0: 0xFFFFFFFE 0x0018F5F4: 0x7666E9A7, in C:Windowssyswow64KERNELBASE.dll (0x76660000) 0x0018F5F8: 0x75F81169, in C:Windowssyswow64kernel32.dll (0x75f70000) 0x0018F5FC: 0x00000460 0x0018F600: 0xFFFFFFFF 0x0018F604: 0x00000000 0x0018F608: 0x03F05980 0x0018F60C: 0x0018F620 0x0018F610: 0x75F81190, in C:Windowssyswow64kernel32.dll (0x75f70000) 0x0018F614: 0x00000460 0x0018F618: 0xFFFFFFFF 0x0018F61C: 0x77A7FB31, in C:WindowsSysWOW64ntdll.dll (0x77a60000) 0x0018F620: 0x7666E479, in C:Windowssyswow64KERNELBASE.dll (0x76660000) 0x0018F624: 0x00000460 0x0018F628: 0x00000000 0x0018F62C: 0x0018F660 0x0018F630: 0x2111D981, in D:ProgramsEQ2mss32.dll (0x21100000) 0x0018F634: 0x00000460 0x0018F638: 0x00B45767, in D:ProgramsEQ2EverQuest2.exe (0x00400000) 0x0018F63C: 0x03F05980 0x0018F640: 0x0058E44B, in D:ProgramsEQ2EverQuest2.exe (0x00400000) 0x0018F644: 0x051DE114 0x0018F648: 0x011B2738, in D:ProgramsEQ2EverQuest2.exe (0x00400000) 0x0018F64C: 0xC850D9A7 0x0018F650: 0x50FA09F0 0x0018F654: 0x12704E6C 0x0018F658: 0x00598E9C, in D:ProgramsEQ2EverQuest2.exe (0x00400000) 0x0018F65C: 0x0018F724 0x0018F660: 0x0018F718 0x0018F664: 0x00598EBC, in D:ProgramsEQ2EverQuest2.exe (0x00400000) 0x0018F668: 0x00598EF4, in D:ProgramsEQ2EverQuest2.exe (0x00400000) 0x0018F66C: 0x00000000 0x0018F670: 0x50FA09F0 0x0018F674: 0x05247F30 0x0018F678: 0x00000000 0x0018F67C: 0xC500A528 0x0018F680: 0xC21AAE5E 0x0018F684: 0x43C53E65 0x0018F688: 0x0000F738 0x0018F68C: 0xA272C350 0x0018F690: 0xA272C350 0x0018F694: 0x3C1B9E37 0x0018F698: 0x3F7FEDB9 0x0018F69C: 0xBCB11F7E 0x0018F6A0: 0xBF6A61B3 0x0018F6A4: 0x3098FEB6 0x0018F6A8: 0xBECDECBA 0x0018F6AC: 0x00000640 0x0018F6B0: 0x000004B0 0x0018F6B4: 0x9809E940 0x0018F6B8: 0x97A57C90 0x0018F6BC: 0x00000008 0x0018F6C0: 0x00000008 0x0018F6C4: 0x00000001 0x0018F6C8: 0x00000020 0x0018F6CC: 0x00000000 0x0018F6D0: 0x00000000 0x0018F6D4: 0x00000000 0x0018F6D8: 0x0018F7A4 0x0018F6DC: 0x00008910 0x0018F6E0: 0x009CC61F, in D:ProgramsEQ2EverQuest2.exe (0x00400000) 0x0018F6E4: 0x05136FA0 0x0018F6E8: 0x0018F764 0x0018F6EC: 0x00000010 0x0018F6F0: 0x0018F7A4 0x0018F6F4: 0x0018F838 0x0018F6F8: 0x0018F7F8 0x0018F6FC: 0x0540A110 0x0018F700: 0x008EE0ED, in D:ProgramsEQ2EverQuest2.exe (0x00400000) 0x0018F704: 0x00000000 0x0018F708: 0x0018027F 0x0018F70C: 0x0018F734 0x0018F710: 0x009B9617, in D:ProgramsEQ2EverQuest2.exe (0x00400000) 0x0018F714: 0x44160000 0x0018F718: 0x0018F8D8 0x0018F71C: 0x0018F7D0 0x0018F720: 0x0018F878 0x0018F724: 0xBF800000 0x0018F728: 0x80000000 0x0018F72C: 0x00000000 0x0018F730: 0xBF800000 0x0018F734: 0x00000000 0x0018F738: 0xBF800000 0x0018F73C: 0x00000000 0x0018F740: 0x3F800000 0x0018F744: 0x44480000 0x0018F748: 0x00000000 0x0018F74C: 0x3F800000 0x0018F750: 0x00000000 0x0018F754: 0xBF800000 0x0018F758: 0x3F800000 0x0018F75C: 0xBF800000 0x0018F760: 0x00000000 0x0018F764: 0x3F800000 0x0018F768: 0x3F800000 0x0018F76C: 0x00000000 0x0018F770: 0x00000000 0x0018F774: 0x00000000 0x0018F778: 0xBF800000 0x0018F77C: 0x00000000 0x0018F780: 0xC4160000 0x0018F784: 0x3F800000 0x0018F788: 0x3F800000 0x0018F78C: 0x00000000 0x0018F790: 0x00000000 0x0018F794: 0xC4480000 0x0018F798: 0x00000000 0x0018F79C: 0xBF800000 0x0018F7A0: 0x0545FA14 0x0018F7A4: 0x00008890 0x0018F7A8: 0x009CC581, in D:ProgramsEQ2EverQuest2.exe (0x00400000) 0x0018F7AC: 0x05136F20 0x0018F7B0: 0x0018F92C 0x0018F7B4: 0x00000010 0x0018F7B8: 0x0545FA14 0x0018F7BC: 0x0018F96C 0x0018F7C0: 0x0018F92CEnd of Stack ScanEND OF LOG---------------------------------------------------------It does seem like a memory leak somewhere I guess then.

Lortet

10-17-2009, 09:42 PM

<cite>MurFalad wrote:</cite><blockquote> It does seem like a memory leak somewhere I guess then. </blockquote>Yes - just like the titanic had a leakI thought things had got better, but this weekend it is worse than ever. Throw in a repeatable instnat crash every time I attempt the haunted house quest (start of the dance routine) with a memory crash every time I foget to minimise when zoning...................................

Enever

10-17-2009, 11:43 PM

its' gotten EVEN worse, I'm crashing every hour.

betatester7

10-17-2009, 11:59 PM

yes, also i'm having 100% using of processor (p4 3.2 HT) and crashing at random moments!

Rannc

10-18-2009, 07:54 AM

Status on the work being done to correct this issue please?

Lortet

10-18-2009, 08:13 AM

Wow - I've only just found out what the combination of this "leak" (read flood) has when traversing Kelethin, Neriak or Gorowyn - minimise every 60 seconds or crash - but then crash anyway sometimes. For those pushing for the old cities to be merged into one big zone - check out this mess.

Enever

10-18-2009, 02:15 PM

Happened again, but I restarted when the game wasn't rendering the map or Menu buttons. Thsi was after 5 zonings between Qeynos's zones, my house in SQ and then a guildhall to Steamfont then to Loping plains.Zoning is what is causing it to spike.

Rothgar

10-18-2009, 03:10 PM

<cite>Ranncor@Befallen wrote:</cite><blockquote>Status on the work being done to correct this issue please?</blockquote>We've been taking a lot of snapshots of memory allocations and comparing this data to the code from different times. We've gone back as far as June, rebuilt the code and compared these allocations to today's code. We have an understanding of what is happening and when. Unfortunately it's not as simple as rolling the code back to June because it would take a lot of other code with it. So we're working on a way to fix the problem correctly.There are actually two issues coming into play. There appears to be an issue with data not being cleared from the cache as aggressively as it should. This isn't really a memory leak, its just the client holdng on to things that it can probably get rid of, especially after zoning. Then there is also the issue of memory becoming fragmented which eventually causes the allocation error. Both should really be fixed if possible, but as soon as we have a fix for one or the other, we will get it out asap. Fixing either issue should keep the client from crashing as much as it is.I'll let you know when I have more info.

Yarginis

10-18-2009, 10:43 PM

<cite>Rothgar wrote:</cite><blockquote>There are actually two issues coming into play. There appears to be an issue with data not being cleared from the cache as aggressively as it should. This isn't really a memory leak, its just the client holdng on to things that it can probably get rid of, especially after zoning.</blockquote>This seems to follow what I've seen. Zoning back and forth between 2 zones over and over actually seems quicker. (Probably because it isn't clearing this data) but anything besides going back and forth between the same 2 zones is drastically slowed down.I am also getting the thing where your screen loads up the new zone, but doesn't actually place your character in yet. (Basically ou're just staring at a picture of where you'll end up but with your HP/Power bars blank for several seconds. I only used 2 ever see this on my old machine with 1.5gb RAM, but now even my newer machine (4gb) does this. I'd say that once I've been in game for at least 90 minutes my zoning time is probably 2x as long as it was pre-53 unless I am going back and forth between the same zones over and over. (I used 2 almost always zone in under 10s on my new machine unless it was to a full GH, now it can be as long as 25-30s after being in game for a long time)Thx again <img src="/smilies/283a16da79f3aa23fe1025c96295f04f.gif" border="0" alt="SMILEY" />

Guy De Alsace

10-19-2009, 04:47 AM

Is anything further forward with this? The game is a total mess at the moment. I happened across Xanadu raiding Avatar of Disease in Ant and their raid caused me to go out-of-memory and CTD'd.This only about 5 mins after the previous OOM crash. any fixes so far have not reduced the problem in any way at my end.

BDoodle

10-19-2009, 07:52 AM

Could telling windows to set aside more memory for caching help?

feldon30

10-19-2009, 09:24 AM

I don't think EQ2 can use more than 3 GB of RAM.

Araxes

10-19-2009, 10:27 AM

Is this only happening on systems with 3GB limits?Under Vista 64-bit, with 4GB, and playing in Windowed mode, I have never seen my memory usage go above 1.7GB.However I have had other, similar problems, which I mentioned in <a href="http://forums.station.sony.com/eq2/posts/list.m?topic_id=460822" target="_blank">another thread</a>. Mainly, textures don't seem to be swapping as quickly as they used to, and there is, overall, more waiting time when switching graphical settings from high-to-low or vice versa. It seems to me, based on what Rothgar posted about caching, that these could be intertwined issues.Good to know they are being addressed, in any case.Ara

Enever

10-19-2009, 11:22 AM

Thank you for the update Rothgar.

Rannc

10-19-2009, 01:01 PM

<cite>Rothgar wrote:</cite><blockquote><cite>Ranncor@Befallen wrote:</cite><blockquote>Status on the work being done to correct this issue please?</blockquote>We've been taking a lot of snapshots of memory allocations and comparing this data to the code from different times. We've gone back as far as June, rebuilt the code and compared these allocations to today's code. We have an understanding of what is happening and when. Unfortunately it's not as simple as rolling the code back to June because it would take a lot of other code with it. So we're working on a way to fix the problem correctly.There are actually two issues coming into play. There appears to be an issue with data not being cleared from the cache as aggressively as it should. This isn't really a memory leak, its just the client holdng on to things that it can probably get rid of, especially after zoning. Then there is also the issue of memory becoming fragmented which eventually causes the allocation error. Both should really be fixed if possible, but as soon as we have a fix for one or the other, we will get it out asap. Fixing either issue should keep the client from crashing as much as it is.I'll let you know when I have more info.</blockquote>

Rannc

10-19-2009, 01:05 PM

Sorry about that, pressed enter to get cursor in edit box I thought...Anyway, thank you very much for the update and news. I appreciate you taking the time to do that. I'll look forward to more news as it is possible.Meantime for me personally, the game has become playable for a couple hours at a time generally on a 2 gig memory XP SP3 system, by turning down textures to medium and while I am not sure this helps much also, I turned off font smoothing which to me was no big loss. The game still looks good and at least now I can play it again.When I notice hitching as I move around, I can tell it's time to log out and close EQ2 gracefully as it is consuming about 3.5 gigs with pagefile included and will soon fail. So I exit out, restart it and gtg for another couple hours or so. While not ideal, this works for now and so I thought I'd share it in case it helps anyone else to workaround this for now.Thanks again for the update.

Amphibia

10-19-2009, 04:24 PM

Can't even finish the Haunted mansion now without crashing...Tried turning down textures, cutting smooth fonts, turning off specular lighting etc. The game is still unplayable. Anything else I can do, besides turning it down to Amiga graphics?I have 4gb memory on my computer, and never crashed before GU53.Also, thanks to the devs for looking into this.

Wingrider01

10-19-2009, 06:12 PM

<cite>Amphibia wrote:</cite><blockquote>Can't even finish the Haunted mansion now without crashing...Tried turning down textures, cutting smooth fonts, turning off specular lighting etc. The game is still unplayable. Anything else I can do, besides turning it down to Amiga graphics?I have 4gb memory on my computer, and never crashed before GU53.Also, thanks to the devs for looking into this.</blockquote>try camping out to desktop right before you zone in and run in full screen, seems to fragment memory a lot less then in windowed mode

Foolsfolly

10-20-2009, 03:19 AM

4 more bluescreens and 3 more outofmemory crashes over the last 2 days.

Wingrider01

10-20-2009, 07:28 AM

<cite>Foolsfolly wrote:</cite><blockquote>4 more bluescreens and 3 more outofmemory crashes over the last 2 days.</blockquote>Blue screen is a driver out of date or corrupt issue, 95 percent chance it does not relate to the out of memory. Post the text of the blue screen in another thread.

Galldora

10-20-2009, 10:27 PM

Oh dear, this problem seems to have gotten worse for me again. I've tried many combinations of settings, etc., and minimizing every so often has turned out to be the best temporary work-around for me. Now, though, as of this afternoon, I'm getting the OOM problem again unless I minimize VERY frequently. Watching my task manager, it seems like the numbers are climbing faster now than they were. <img src="/eq2/images/smilies/136dd33cba83140c7ce38db096d05aed.gif" border="0" />

Hapa

10-21-2009, 08:57 PM

The game has now become unplayable for me. I know Sony's not really gonna miss my $14.99/month, but I've had to cancel my account until this is fixed. I am very sad now. <img src="/eq2/images/smilies/c30b4198e0907b23b8246bdd52aa1c3c.gif" border="0" />Please find a fix soon, Sony!

Denon

10-21-2009, 09:52 PM

If I try to do 'Trick or Treat' in Qeynos. Just running around in that zone - never zoning - I have not been able to get through it without the client crashing on me with the (2895) DirectXError (E_OutofMemory) error - Win XP SP3 2 Gigs Ram.

Jacquotte

10-22-2009, 08:12 AM

on my system, i have seen it easily eat up to 6gb+ of ram with just 1 instance of eq2 runningif you have little to no memory when running the game, you can always try:You can do this by adding the following line to your eq2.ini file in the same directory as eq2.exe:force_low_mem_mode true

MrWolfie

10-22-2009, 11:02 AM

Latest CTD, with a critical error message "out of memory". Today's rundown: guild hall, nek, Hedge, guild hall, SF, LP, Mansion, LP, GF - crashed while zoning in.SOEBuild=5981LSOEVersionString=2009/10/20 11:33:41EVERQUEST2 CRASH LOG=============================================== ================================================== =Unhandled exception EXCEPTION_ACCESS_VIOLATION at 0x00B3CD7FApplication was trying to write to 0x00000002 Region Begins At: 0x00000000 Region Ends At: 0x00010000 Region Size Is: 0x00010000 bytes Memory Protection: PAGE_NOACCESS (00000001) Memory State: MEM_FREE Memory Type: FreeGame Data: SOEBuild: SOEBuild=5981L SOEVersionString: SOEVersionString=2009/10/20 11:33:41 OS Version: 5.1.2600 Service Pack 3 VER_NT_WORKSTATION CPU: 2 x86 GenuineIntel 2400MHz RDTSC MSR CMPXCHG8 SSE SSE2 DirectX Version: 9.0c Video Card/Driver: [NVIDIA GeForce GTX 260] [nv4_disp.dll] 6.14.11.9038 {d7b71e3e-46a2-11cf-2050-852600c2cb35} Time at crash: Thu Oct 22 14:55:04 2009 Login Server: none Performance: 7 Game Uptime: 4288 seconds Position last frame: 95.27, 8.00, 748.63 Zone name: exp03_rgn_greater_faydark Time in Zone: 296 seconds Previous Zone name: GameScene::ZR_NETWORKED_ZONE_CHANGE Multi-core support: enabled Low-Memory Mode: disabledLog: Loading RoomItemNode: zones/exp03_rgn_greater_faydark/rooms/exp03_rgn_greater_faydark_gf_cave_rm06_rmobj_0.voc , tag 0xaeae0ead Loading RoomItemNode: zones/exp03_rgn_greater_faydark/rooms/exp03_rgn_greater_faydark_gf_kel_int_cleric_guild_ rm02_0.voc, tag 0xcaf8c62f Loading RoomItemNode: zones/exp03_rgn_greater_faydark/rooms/exp03_rgn_greater_faydark_gf_kel_int_elf_house01_r m01_1.voc, tag 0x6afcef60 Loading RoomItemNode: zones/exp03_rgn_greater_faydark/rooms/exp03_rgn_greater_faydark_gf_kel_int_elf_house07_r m01_1.voc, tag 0x56bf30ef Loading RoomItemNode: zones/exp03_rgn_greater_faydark/rooms/exp03_rgn_greater_faydark_gf_kel_int_mage_guild_rm 01_0.voc, tag 0xd6c93427 Loading RoomItemNode: zones/exp03_rgn_greater_faydark/rooms/exp03_rgn_greater_faydark_gf_ter_r07_rmobj_0.voc, tag 0x2e3712e3 Loading RoomItemNode: zones/exp03_rgn_greater_faydark/rooms/exp03_rgn_greater_faydark_gf_cave_rm07_rmobj_0.voc , tag 0x13ad5efd World bounds of (exp03_rgn_greater_faydark) are (-1887.134766 -164.501831 -2132.349609), (1146.195679 487.640594 1188.880859) (computed in 0.000s) [0.000s] VeZone loaded <MEMORY> E:liveeq2frameworkmemoryManagersrcsharedMemoryMana ger.cpp(2010): Application ran out of memory when requesting 5187552 bytes (limit: 1534 MB, current: 840 MB)Thread Data: Primary Thread Id: 2472 Current Thread Id: 2472 Current Thread Priority: 0Memory: AddressLimitMB: 2048 Load: 85% Total physical: 2145890304 Free physical: 312942592 Total pagefile: 4294967295 Free pagefile: 2736082944 Total virtual: 2147352576 Free virtual: 82808832Memory Manager: Allocations: 329004 Bytes Allocated: 655902320 Max Allocations: 377835 Max Bytes Allocated: 879560672 System Memory Allocated (MB): 840 Limit: 1534 Number of Allocate Calls: 4221768 Number of Free Calls: 3892764Registers: EAX 0x00000001 EBX 0x7C91005D ECX 0x5D340001 EDX 0x00C5E90A ESI 0x7C85AD4C EDI 0x004F27E0 GS 0x00000000 FS 0x0000003B ES 0x00000023 DS 0x00000023 EBP 0x0013F61C ESP 0x0013ED98 EIP 0x00B3CD7F FLAGS 0x00010246 CS 0x0000001B SS 0x00000023FPU Registers: CW 0xFFFF027F SW 0xFFFF0120 TW 0xFFFFFFFFFPU Rounding Mode: NearestCall Stack: 0x00B3CD7F: MemoryManager::allocate+302f 0x00C5F926: MemoryManager::allocate+125bd6 0x00C60C1B: MemoryManager::allocate+126ecb 0x009F6D81 in E:EverQuest IIEverQuest2.exe 0x009FA201 in E:EverQuest IIEverQuest2.exe 0x009FACF1 in E:EverQuest IIEverQuest2.exe 0x009FC6A6 in E:EverQuest IIEverQuest2.exe 0x009FCAD9 in E:EverQuest IIEverQuest2.exe 0x009FCB87 in E:EverQuest IIEverQuest2.exe 0x02AF99E0 in ???????? 0xBFF0BFF0 in ????????End of Call StackStack Scan: 0x0013ED98: 0x00000000 0x0013ED9C: 0x6C707041 0x0013EDA0: 0x74616369 0x0013EDA4: 0x206E6F69 0x0013EDA8: 0x206E6172 0x0013EDAC: 0x2074756F 0x0013EDB0: 0x6D20666F 0x0013EDB4: 0x726F6D65 0x0013EDB8: 0x68772079 0x0013EDBC: 0x72206E65 0x0013EDC0: 0x65757165 0x0013EDC4: 0x6E697473 0x0013EDC8: 0x31352067 0x0013EDCC: 0x35353738 0x0013EDD0: 0x79622032 0x0013EDD4: 0x20736574 0x0013EDD8: 0x6D696C28 0x0013EDDC: 0x203A7469 0x0013EDE0: 0x34333531 0x0013EDE4: 0x2C424D20 0x0013EDE8: 0x72756320 0x0013EDEC: 0x746E6572 0x0013EDF0: 0x3438203A 0x0013EDF4: 0x424D2030 0x0013EDF8: 0xFFFF0029 0x0013EDFC: 0x25CFDBB0 0x0013EE00: 0x00000004 0x0013EE04: 0x004280AA, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EE08: 0x00000000 0x0013EE0C: 0x00000000 0x0013EE10: 0x00000000 0x0013EE14: 0x00000000 0x0013EE18: 0x00000000 0x0013EE1C: 0x00EC945C, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EE20: 0x00000000 0x0013EE24: 0x00000000 0x0013EE28: 0x00000000 0x0013EE2C: 0x00000000 0x0013EE30: 0x3F800000 0x0013EE34: 0x3F800000 0x0013EE38: 0x00B3CCE7, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EE3C: 0x0B6508E0 0x0013EE40: 0x00000004 0x0013EE44: 0x009FDC31, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EE48: 0x00000000 0x0013EE4C: 0x00EC945C, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EE50: 0x00000000 0x0013EE54: 0x00000000 0x0013EE58: 0x00000000 0x0013EE5C: 0x00000000 0x0013EE60: 0x3F800000 0x0013EE64: 0x3F800000 0x0013EE68: 0x42FB2B20 0x0013EE6C: 0x422CA4D0 0x0013EE70: 0x00000008 0x0013EE74: 0x004280AA, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EE78: 0x00B3CCE7, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EE7C: 0x422CA4D0 0x0013EE80: 0x00000004 0x0013EE84: 0x009FDC31, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EE88: 0x00B3CCE7, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EE8C: 0x01209E48, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EE90: 0x00B39DC7, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EE94: 0x422CA4D0 0x0013EE98: 0x422CA4F0 0x0013EE9C: 0x4A4250A0 0x0013EEA0: 0x00000008 0x0013EEA4: 0x004280AA, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EEA8: 0x00B3CCE7, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EEAC: 0x42B3DDB0 0x0013EEB0: 0x00000004 0x0013EEB4: 0x009FDC31, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EEB8: 0x00B3CCE7, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EEBC: 0x01209E48, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EEC0: 0x00B39DC7, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EEC4: 0x42B3DDB0 0x0013EEC8: 0x42B3DDD0 0x0013EECC: 0x00000000 0x0013EED0: 0x461DA385 0x0013EED4: 0x9E3779B9 0x0013EED8: 0x0013EF58 0x0013EEDC: 0x008BD3CC, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EEE0: 0x0013EF54 0x0013EEE4: 0x00E86B72, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EEE8: 0xFFFFFFFF, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EEEC: 0x00B3A154, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EEF0: 0x00000004 0x0013EEF4: 0x009FDC48, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EEF8: 0x00000000 0x0013EEFC: 0x00000001 0x0013EF00: 0x42FB2240 0x0013EF04: 0x42FB2240 0x0013EF08: 0x00000000 0x0013EF0C: 0x00000002 0x0013EF10: 0x00000004 0x0013EF14: 0x00000001 0x0013EF18: 0x42B3DDB0 0x0013EF1C: 0x42B3DDD0 0x0013EF20: 0x00000000 0x0013EF24: 0x009FE069, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EF28: 0x42FB2240 0x0013EF2C: 0x0013EF68 0x0013EF30: 0x4A88B480 0x0013EF34: 0x009FE467, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EF38: 0x0013EF68 0x0013EF3C: 0x0013F30C 0x0013EF40: 0x42B3DDB0 0x0013EF44: 0x42B3DDE0 0x0013EF48: 0x42B3DDB0 0x0013EF4C: 0x26A72E3C 0x0013EF50: 0x009FE401, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EF54: 0x0013EF80 0x0013EF58: 0x00E754E0, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EF5C: 0xFFFFFFFF, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EF60: 0x0013EF8C 0x0013EF64: 0x00A7219F, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EF68: 0x4A88B480 0x0013EF6C: 0x42B3DDB0 0x0013EF70: 0x0013F308 0x0013EF74: 0x0013F308 0x0013EF78: 0x493B9810 0x0013EF7C: 0x00A72170, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EF80: 0x0013F11C 0x0013EF84: 0x00E7B413, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EF88: 0xFFFFFFFF, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EF8C: 0x0013F128 0x0013EF90: 0x00A523AC, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EF94: 0x26A72E3C 0x0013EF98: 0x00A732D9, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EF9C: 0x42B3DDB0 0x0013EFA0: 0x3F57B2F0 0x0013EFA4: 0x0013F308 0x0013EFA8: 0x6BE17890 0x0013EFAC: 0x0013EFD8 0x0013EFB0: 0x00E7543E, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EFB4: 0xFFFFFFFF, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EFB8: 0x0013EFE4 0x0013EFBC: 0x009FD745, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EFC0: 0x009FD745, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EFC4: 0x5D3D1650 0x0013EFC8: 0x3F4C3D50 0x0013EFCC: 0x0013F308 0x0013EFD0: 0x1450FB50 0x0013EFD4: 0x0013F308 0x0013EFD8: 0x5D3D1650 0x0013EFDC: 0x0013F008 0x0013EFE0: 0x00E7543E, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EFE4: 0xFFFFFFFF, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EFE8: 0x0013F014 0x0013EFEC: 0x009FD745, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013EFF0: 0x1450FB50 0x0013EFF4: 0x1450FB50 0x0013EFF8: 0x12DAF800 0x0013EFFC: 0x0013F30C 0x0013F000: 0x0013F308 0x0013F004: 0x1450FB50 0x0013F008: 0x0013F0A8 0x0013F00C: 0x00000000 0x0013F010: 0xFFFFFFFF 0x0013F014: 0x0013F088 0x0013F018: 0x00A652C3, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F01C: 0x00A652CC, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F020: 0x3F4C3D10 0x0013F024: 0x0013F308 0x0013F028: 0x1450FA80 0x0013F02C: 0x1450F5A0 0x0013F030: 0x3F289994 0x0013F034: 0x00000000 0x0013F038: 0xBF40A3C6 0x0013F03C: 0x0013F30C 0x0013F040: 0x00000000 0x0013F044: 0x3F800000 0x0013F048: 0x00000000 0x0013F04C: 0x00000000 0x0013F050: 0x3F40A3C6 0x0013F054: 0x00000000 0x0013F058: 0x3F289994 0x0013F05C: 0x00000000 0x0013F060: 0x009FD745, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F064: 0x5D3D2250 0x0013F068: 0x3F57B440 0x0013F06C: 0x0013F308 0x0013F070: 0xC2EEA252 0x0013F074: 0x415DEAE7 0x0013F078: 0xC2F8BA22 0x0013F07C: 0x3F800000 0x0013F080: 0x00E7543E, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F084: 0xFFFFFFFF, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F088: 0x0013F0B4 0x0013F08C: 0x009FD745, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F090: 0x1450FA80 0x0013F094: 0x1450FA80 0x0013F098: 0x12DAF780 0x0013F09C: 0x0013F30C 0x0013F0A0: 0x0013F308 0x0013F0A4: 0x1450FA80 0x0013F0A8: 0x0013F148 0x0013F0AC: 0x00000000 0x0013F0B0: 0xFFFFFFFF 0x0013F0B4: 0x0013F128 0x0013F0B8: 0x00A652C3, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F0BC: 0x00A652CC, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F0C0: 0x65398494 0x0013F0C4: 0x0013F308 0x0013F0C8: 0x1450F4D0 0x0013F0CC: 0x3F800000 0x0013F0D0: 0x009FD745, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F0D4: 0x62C05550 0x0013F0D8: 0x419512B0 0x0013F0DC: 0x0013F30C 0x0013F0E0: 0x0013F308 0x0013F0E4: 0x42B3DDB0 0x0013F0E8: 0x00ECE9E8, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F0EC: 0x00000000 0x0013F0F0: 0x00000000 0x0013F0F4: 0x00000000 0x0013F0F8: 0x00000000 0x0013F0FC: 0x3F800000 0x0013F100: 0x009FD745, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F104: 0x3E11BE60 0x0013F108: 0x3F4C3D90 0x0013F10C: 0x0013F308 0x0013F110: 0x1450FCF0 0x0013F114: 0x0013F308 0x0013F118: 0x3E11BE60 0x0013F11C: 0x0013F148 0x0013F120: 0x00E7543E, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F124: 0xFFFFFFFF, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F128: 0x0013F154 0x0013F12C: 0x009FD745, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F130: 0x1450FCF0 0x0013F134: 0x1450FCF0 0x0013F138: 0x12DAF700 0x0013F13C: 0x0013F30C 0x0013F140: 0x0013F308 0x0013F144: 0x1450FCF0 0x0013F148: 0x0013F1E8 0x0013F14C: 0x00000000 0x0013F150: 0xFFFFFFFF 0x0013F154: 0x0013F1C8 0x0013F158: 0x00A652C3, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F15C: 0x00A652CC, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F160: 0x3F4C3E28 0x0013F164: 0x0013F308 0x0013F168: 0x67B350D0 0x0013F16C: 0x009FD745, in E:EverQuest IIEverQuest2.exe (0x00400000) 0x0013F170: 0x10CAF990 0x0013F174: 0x10CAF990 0x0013F178: 0x12DAF700 0x0013F17C: 0x0013F30C 0x0013F180: 0x00000000 0x0013F184: 0x00000000 0x0013F188: 0x00000000 0x0013F18C: 0x3F800000 0x0013F190: 0x0013F1BC 0x0013F194: 0x009FD745, in E:EverQuest IIEverQuest2.exe (0x00400000)End of Stack ScanEND OF LOG

Tro

10-22-2009, 12:31 PM

<cite>Aemm@Splitpaw wrote:</cite><blockquote>Latest CTD, with a critical error message "out of memory". Today's rundown: guild hall, nek, Hedge, guild hall, SF, LP, Mansion, LP, GF - crashed while zoning in.SOEBuild=5981LSOEVersionString=2009/10/20 11:33:41EVERQUEST2 CRASH LOG=============================================== ================================================== =Unhandled exception EXCEPTION_ACCESS_VIOLATION at 0x00B3CD7FApplication was trying to write to 0x00000002 Region Begins At: 0x00000000 Region Ends At: 0x00010000 Region Size Is: 0x00010000 bytes Memory Protection: PAGE_NOACCESS (00000001) Memory State: MEM_FREE Memory Type: FreeGame Data: SOEBuild: SOEBuild=5981L SOEVersionString: SOEVersionString=2009/10/20 11:33:41 OS Version: 5.1.2600 Service Pack 3 VER_NT_WORKSTATION CPU: 2 x86 GenuineIntel 2400MHz RDTSC MSR CMPXCHG8 SSE SSE2 DirectX Version: 9.0c Video Card/Driver: [NVIDIA GeForce GTX 260] [nv4_disp.dll] 6.14.11.9038 {d7b71e3e-46a2-11cf-2050-852600c2cb35} Time at crash: Thu Oct 22 14:55:04 2009 Login Server: none Performance: 7 Game Uptime: 4288 seconds Position last frame: 95.27, 8.00, 748.63 Zone name: exp03_rgn_greater_faydark Time in Zone: 296 seconds Previous Zone name: GameScene::ZR_NETWORKED_ZONE_CHANGE Multi-core support: enabled Low-Memory Mode: disabledEND OF LOG</blockquote>I have notice on a few of these posts that the red highlighted is always "disabled".. Wonder if changing it to "Enabled" will help folks until the real fix comes out...Just a thought.

BDoodle

10-22-2009, 03:46 PM

I've been using a work around that seems to give me hours play time, rather than 15-20min as before.I play in windowed mode with task manager open, and pushed off the bottom of the desktop so I can just keep an eye on how much memory EQ2 is using. When EQ2 gets to about half the size of my physical memory, and when zoning, I minimize the EQ2 window for a few seconds.When minimized the program only takes a fraction of the memory, and when the window is restored and the program reinstated in to working memory it's size is greatly reduced.This has been working for me for the past 2 days without crashing, (though because I only have 1GB memory I still occasionally get momentary game freezes due to the system wanting to do something with my CPU time.)I hope this helps some of you get back into the game until the fix comes out, even if it does take a bit of stuffing about with window sizes and setup. Incidentally, this issue has continued for me even after I recieved the latest update last night. (the everquest2_delta... update.) So I'm still using the work around.

Morghus

10-23-2009, 05:44 AM

I am sorry if this comes as overly critical of me, but I have been silent on such issues for too long and with a new expansion coming I fear we will only see more of the issues we now have unless they are addressed by then.First, is this really even being worked on? There have been no real meaningful client updates for some time now that have affected my performance. I have two computers at home, and one of them which has been able to play eq2 flawlessly for several years is just now within this year starting to have various issues and crashes related to out of memory and directx.My other computer does not have as many issues, but the issues definately are still present and are....to say the least unacceptable. These kinds of issues should not be turning up in the first place, in fact overall game performance has almost always been underwhelming to say the least.The graphics are not cutting edge, they have barely even been so since I first started playing around five years ago. The overall performance and memory management of the game is something that should have been dealt with long ago, and the improvement of the engine in all its facets should be sitting near the highest of priorities if it isnt already.I had a guild member claim the other day that during a raid, under high performance settings they were still every now and then hitching at around 3 fps- 3FPS! Now granted their computer is not all that great, but come on now...it is obvious to anyone that is playing the game that the minimum and recommended requirements do not fit, in fact the recommended requirements are probably closer to the minimum nowdays.Heck, I'm not even sure if the crashing is doing even more damage to my computers over time. It would definately seem that way to me, I've gone through more hardware than usual playing eq2.Again, sorry if it comes off as overly negative. I'm just one of those people who are fed up with the engine's faults.

Guy De Alsace

10-23-2009, 06:08 AM

The graphics are still the best out there and have been since release - at least in MMO terms. Try playing one of Turbine's games if you want to compare - or WoW.But the one major and now very serious flaw is the memory usage which was always pretty bad - its now game breakingly bad.I can no longer run two instances of EQ2 on mine, its tough even doing one. Since GU53 that is. Clearly there is a major issue - since none of the "fixes" have worked I'm guessing its a tough one so it may be like this for a while sadly.It comes to something when my 6 and a half year old comp that has been upgraded has worse performance now than at release. <img src="/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" alt="SMILEY" />

Morghus

10-23-2009, 06:26 AM

<cite>Guy De Alsace wrote:</cite><blockquote>The graphics are still the best out there and have been since release - at least in MMO terms. Try playing one of Turbine's games if you want to compare - or WoW.But the one major and now very serious flaw is the memory usage which was always pretty bad - its now game breakingly bad.I can no longer run two instances of EQ2 on mine, its tough even doing one. Since GU53 that is. Clearly there is a major issue - since none of the "fixes" have worked I'm guessing its a tough one so it may be like this for a while sadly.It comes to something when my 6 and a half year old comp that has been upgraded has worse performance now than at release. <img src="/eq2/images/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" /></blockquote>Definately. Something has obviously gone wrong somewhere along the way, somewhere after or during the many game updates and expansions. I myself remember playing vanilla eq2 when it first came out and being able to play with fairly mid-level settings, particle effects, and being able to zone repeatedly without issue. Nowdays though, even on an upgraded PC I have to run with complex shaders at -1, particles at very low settings, lower texture settings etc.It may still be visually the best, at least technically speaking but overall it lacks in design I would say. Some things do indeed look nice, but we are playing a game here...it has to look good and play good. Just by pushing the most polygons and other sorts of thing for the sake of it is nonsense, in my opinion those in charge of such things should strive to do more, with less while still trying to achieve the same effect.

Alienor

10-23-2009, 07:44 AM

<cite>Guy De Alsace wrote:</cite><blockquote>The graphics are still the best out there and have been since release - at least in MMO terms. Try playing one of Turbine's games if you want to compare - or WoW.</blockquote>Not sure what you mean. Vanguard and Lotro have better graphics imo.

Todra_B

10-23-2009, 10:58 AM

I have an OLD machine. 3.0ghz Pentium 4 with 1gb ram and a 256 mb vid card. I run the game at extreme performance in window mode and get UP TO 18fps. Sometimes when I'm in my toons house I flip the settings to "balanced" just to see what it looks like. I can't play at that setting, 2-5 fps.My guild moved most of the amenities, Broker etc. , to the front courtyard to help us out. I can't enter the structure part of the guild hall without a memory error. I tried to go in last week for a raid and had to petition my toon out of the gh.I want to get a new PC but I want something that will play smoothly at the highest graphics. IS that even possible anymore? Does the game run well in Win7 with the new graphics cards? I really like the game and want to stay but how much do I need to spend to run the game while looking the way the devs intended?

Hapa

10-23-2009, 11:34 AM

<cite>Corvena@Venekor wrote:</cite><blockquote>on my system, i have seen it easily eat up to 6gb+ of ram with just 1 instance of eq2 runningif you have little to no memory when running the game, you can always try:You can do this by adding the following line to your eq2.ini file in the same directory as eq2.exe:force_low_mem_mode true</blockquote>Thank you! This seems to be working for now. Was able to group and raid last night, no problems.My account's still open for a couple of weeks, so if this holds, I'll probably keep it open. /crosses fingersBig help, thank you again. <img src="/eq2/images/smilies/283a16da79f3aa23fe1025c96295f04f.gif" border="0" />

TalanRM

10-23-2009, 11:59 AM

Any news on a fix yet, as the game is literally unplayable since GU53. Strip out any features you like, just please make the game run for more than 30 mins without crashing. Letting a game update totally break gameplay just to hit a dead-line is bad form.Alternatively, how about setting up a server people can transfer to, which does not include the bulk of GU53 and some of the other database breaking features?

RafaelSmith

10-23-2009, 12:58 PM

I have heard from several people in game about these memory issues. However, I have yet to experience any issues myself and I have 3 different system that I can play EQ2 on....2 desktops and 1 laptop. Desktop 1: Q6600 C2Q, 8GB DDR2, 8800GT, Vista 64Desktop 2: Q9550 C2Q, 8GB DDR2, 8800GTX, Win 7 64Laptop: T9300 C2D, 4gb DDR2, 8800m GTS, Win 7 64All 3 never have any of these memory issues. I can even run 2 instances of EQ2 on those systems without any of these memory issues.Wish I knew what it was about my computers so I could help friends that are having issues.Guess I count myself lucky <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" />If SOE would like I can provide more info about my configurations, DX, etc if they think it would help.

Tro

10-23-2009, 02:45 PM

For what it's worth, I recently built two new identical systems for my wife and I. Our old HP systems we had for about 4 years (HP Pavilion modified for gaming). We had no memory issues on the old systems or the new ones.The HP Pavilion systems were: 2GB DC ram, ATI X800XL cards, 2.4 GHZ AMD single core CPU, 520w OCZ PSU and no clue what Motherboard they used.We are now running:GIGABYTE GA-EP45T-UD3LR LGA 775 Intel P45 ATX Intel MBCorsair ATX12V/ESP12V 750 Watt PSUMSI N260GTX-T2D896-OCv3 GeForce GTX 260 896MBIntel Core 2 Duo E8400 Wolfdale 3.0GHz 6MB L2 Cache LGA 775 65W Dual-Core ProcessorMushkin HP 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) Dual Channel KitWestern Digital Caviar Blue WD3200AAKS 320GB 7200 RPM 16MB Cache SATA 3.0Gb/s RaidMax Smilodon ATX-612WESP CaseThe only issue I have (And it really isn't a problem) is when I launch the game and before getting in, I get the client crash window even though I don't actually crash. I just move it down to the bottom of my DT and all is good. If I click "Send report or "Close" I get kicked out so I just don't mess with it.This has been confirmed to be an Nvidia driver issue.

Kitsune

10-23-2009, 03:32 PM

I wonder if it is a 64 bit OS feature that stops the problems, whearas our 24 bit OS (mine is XP Pro running SP3 with 4 gig ram, Nvidia 8600 GT 512 ram vid card, 182.xx driver for the moment, will move to 186.xx today) are handling the coding errors badly.I run windowed, but I fill the screen except for the task bar. I used to be able to run MSN in the back, and Eudora for mail, ev en my clipboard extender Smartboard Pro, and of course, AVG free, but not now. <img src="/eq2/images/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" /> I turn off everything but AVG, which I suppose I don't really need but I like using a browser outside the game so I can still play and look at Quest info.I think using FreeRam XP Pro program someone here suggested IS helping, though.

Jeeshman

10-23-2009, 04:11 PM

<cite>Gaylon@Mistmoore wrote:</cite><blockquote>I have heard from several people in game about these memory issues. However, I have yet to experience any issues myself and I have 3 different system that I can play EQ2 on....2 desktops and 1 laptop. Desktop 1: Q6600 C2Q, 8GB DDR2, 8800GT, Vista 64Desktop 2: Q9550 C2Q, 8GB DDR2, 8800GTX, Win 7 64Laptop: T9300 C2D, 4gb DDR2, 8800m GTS, Win 7 64All 3 never have any of these memory issues. I can even run 2 instances of EQ2 on those systems without any of these memory issues.Wish I knew what it was about my computers so I could help friends that are having issues.</blockquote>You answered your own question, lol... they're all running 64-bit versions of their respective OS's. As I said in my original post, I'm not having the problem with my 64-bit version of Vista, but my girlfriend was experiencing it and she uses (32-bit) XP. Yep, I said "was." Since last week, she hasn't gotten a single out-of-memory crash. Whatever changes were made last week to the executable fixed it for her. Thank you!