memory hole gone?...don't think so...

[linkmaster]

Go from Khal , through the 2 porters to NT

Turn to face the buildings....Bam...


[02/22/07 19:55:46] ERROR: Error: VirtualAlloc FAILED for 262144 bytes
[02/22/07 19:55:46] FATAL: Critical: Ran out of virtual memory. This condition may be caused by a lack of available space on your hard-drive.
[02/22/07 19:55:46] FATAL: Critical: Windows GetLastError: The system cannot find the path specified. (3)
[02/22/07 19:55:46] FATAL: Exit: Executing UObject::StaticShutdownAfterError
[02/22/07 19:55:46] FATAL: Exit: Executing UWindowsClient::ShutdownAfterError
[02/22/07 19:55:46] FATAL: Exit: OpenAL Audio subsystem shut down.
[02/22/07 19:55:46] FATAL: Critical: FMallocWindows::Malloc
[02/22/07 19:55:46] FATAL: Critical: FMallocWindows::Realloc
[02/22/07 19:55:46] FATAL: Critical: 00000000 262144 FArray
[02/22/07 19:55:46] FATAL: Critical: FArray::Realloc
[02/22/07 19:55:46] FATAL: Critical: 262144*1
[02/22/07 19:55:46] FATAL: Critical: TLazyArray::Load
[02/22/07 19:55:46] FATAL: Critical: TLazyArray::ASyncFileRead
[02/22/07 19:55:46] FATAL: Critical: ASyncLoadTexture
[02/22/07 19:55:46] FATAL: Critical: UNormalBitmapMaterial::PreCache
[02/22/07 19:55:46] FATAL: Critical: FDynamicActor::IsRenderable
[02/22/07 19:55:46] FATAL: Critical: VgSceneTreeNode::IsActorVisible
[02/22/07 19:55:46] FATAL: Critical: VgPlanetScene::RenderLevels
[02/22/07 19:55:46] FATAL: Critical: (Pos=17604.00,51852.00, 741.37)
[02/22/07 19:55:46] FATAL: Critical: UGameEngine::Draw
[02/22/07 19:55:46] FATAL: Critical: UWindowsViewport::Repaint
[02/22/07 19:55:46] FATAL: Critical: UWindowsClient::Tick


:cry:

[Riggin]

Go from Khal , through the 2 porters to NT

Turn to face the buildings....Bam...


[02/22/07 19:55:46] ERROR: Error: VirtualAlloc FAILED for 262144 bytes
[02/22/07 19:55:46] FATAL: Critical: Ran out of virtual memory. This condition may be caused by a lack of available space on your hard-drive.
[02/22/07 19:55:46] FATAL: Critical: Windows GetLastError: The system cannot find the path specified. (3)
[02/22/07 19:55:46] FATAL: Exit: Executing UObject::StaticShutdownAfterError
[02/22/07 19:55:46] FATAL: Exit: Executing UWindowsClient::ShutdownAfterError
[02/22/07 19:55:46] FATAL: Exit: OpenAL Audio subsystem shut down.
[02/22/07 19:55:46] FATAL: Critical: FMallocWindows::Malloc
[02/22/07 19:55:46] FATAL: Critical: FMallocWindows::Realloc
[02/22/07 19:55:46] FATAL: Critical: 00000000 262144 FArray
[02/22/07 19:55:46] FATAL: Critical: FArray::Realloc
[02/22/07 19:55:46] FATAL: Critical: 262144*1
[02/22/07 19:55:46] FATAL: Critical: TLazyArray::Load
[02/22/07 19:55:46] FATAL: Critical: TLazyArray::ASyncFileRead
[02/22/07 19:55:46] FATAL: Critical: ASyncLoadTexture
[02/22/07 19:55:46] FATAL: Critical: UNormalBitmapMaterial::PreCache
[02/22/07 19:55:46] FATAL: Critical: FDynamicActor::IsRenderable
[02/22/07 19:55:46] FATAL: Critical: VgSceneTreeNode::IsActorVisible
[02/22/07 19:55:46] FATAL: Critical: VgPlanetScene::RenderLevels
[02/22/07 19:55:46] FATAL: Critical: (Pos=17604.00,51852.00, 741.37)
[02/22/07 19:55:46] FATAL: Critical: UGameEngine::Draw
[02/22/07 19:55:46] FATAL: Critical: UWindowsViewport::Repaint
[02/22/07 19:55:46] FATAL: Critical: UWindowsClient::Tick


:cry:

Well, there's your problem....they're using smileys in their code!

-Riggin

[Meritt]

They said the fixed a specific memory leak.

Nothing was said about all of the leaks.

[perfect]

Well, there's your problem....they're using smileys in their code!

-Riggin

Better smileys than mongooses, I always say.

Smileys are rancid. Do not use them.

[Riggin]

Better smileys than mongooses, I always say.

Smileys are rancid. Do not use them.

No doubt! With all that chewing, mongeese are hell on memory leaks!

-Riggin

[Pixi]

Well, there's your problem....they're using smileys in their code!

-Riggin

Hehe...funny :D

[Aegorian]

They said the fixed a specific memory leak.

Nothing was said about all of the leaks.

QFOMFGT

There is not A memory leak in Vanguard... there are MANY. They plug them 1 (or a few) at a time and over time we begin to see a cumulative result. There is no magic fix for this, but after this patch it should be better (by at least 1 memory leak).

[troldan]

maybe you should check your hd space like the error sais.

[Mardy]

maybe you should check your hd space like the error sais.

lol and to be more specific, the first 2 lines of your error tells you what you need.

[02/22/07 19:55:46] ERROR: Error: VirtualAlloc FAILED for 262144 bytes
[02/22/07 19:55:46] FATAL: Critical: Ran out of virtual memory. This condition may be caused by a lack of available space on your hard-drive.



Try making sure you have plenty of free hard drive space, and maybe up the virtual memory alloc in your windows. Now if you have the settings set too high but don't have the free hard drive space to handle it, then that won't work either.

So either way, make sure you have plenty of free hard drive space heh.

[vylo]

They may not have fixed ALL memory leaks yet, I think this is the third or so memory leak I have heard of them fixing.

[Multiplex]

lol and to be more specific, the first 2 lines of your error tells you what you need.

[02/22/07 19:55:46] ERROR: Error: VirtualAlloc FAILED for 262144 bytes
[02/22/07 19:55:46] FATAL: Critical: Ran out of virtual memory. This condition may be caused by a lack of available space on your hard-drive.



Try making sure you have plenty of free hard drive space, and maybe up the virtual memory alloc in your windows. Now if you have the settings set too high but don't have the free hard drive space to handle it, then that won't work either.

So either way, make sure you have plenty of free hard drive space heh.

I read that it was an issue with the page file getting too big for windows to handle... not necessarily running out of room on the drive itself.

[Aegorian]

lol and to be more specific, the first 2 lines of your error tells you what you need.

[02/22/07 19:55:46] ERROR: Error: VirtualAlloc FAILED for 262144 bytes
[02/22/07 19:55:46] FATAL: Critical: Ran out of virtual memory. This condition may be caused by a lack of available space on your hard-drive.



Try making sure you have plenty of free hard drive space, and maybe up the virtual memory alloc in your windows. Now if you have the settings set too high but don't have the free hard drive space to handle it, then that won't work either.

So either way, make sure you have plenty of free hard drive space heh.

well that's what a memory leak does :) basically his RAM is filled and his allocated page file is filled as well. I'm sure he has plenty of HD space left, but it should never get to this point if memory is properly released. It's either allocate more space to your page file (which i dont necessarily recommend) or fix the leaks to remedy this.

[troldan]

or dont run with 256 mb mem and page file

[Multiplex]

or dont run with 256 mb mem and page file

I currently have 2gb of memory and over 20gb of free HDD space and I still get memory leaks and crashes related to those leaks.

[Aegorian]

I currently have 2gb of memory and over 20gb of free HDD space and I still get memory leaks and crashes related to those leaks.

yup. me too :) Granted, i crash a lot less often than many other posters who experience them. I can usually play for a few hours w/o a crash.

[Kiste]

QFOMFGT

There is not A memory leak in Vanguard... there are MANY. They plug them 1 (or a few) at a time and over time we begin to see a cumulative result. There is no magic fix for this, but after this patch it should be better (by at least 1 memory leak).

Whatever they fixed, it sure as hell didn't make me crash one lick less frequently.

[Kiste]

Try making sure you have plenty of free hard drive space, and maybe up the virtual memory alloc in your windows. Now if you have the settings set too high but don't have the free hard drive space to handle it, then that won't work either.

So either way, make sure you have plenty of free hard drive space heh.

Do you think people haven't tried that a million times before?

[kab]

or dont run with 256 mb mem and page file

If software is leaking memory no amount of RAM or HD space is going to save you. It will exhaust all resources eventually. Please, don't post "omg ur comp iz teh suq" like a complete buffoon without at least educating yourself enough to form what might at least appear to be a coherent argument.

Sigil did not say they fixed "a" memory leak. They said the patch should fix two major memory leaks. That does not mean more do not exist nor does it mean that the log is necessarily even a result of it. However, given that Sigil admits there are memory leaks and has not claimed to have fixed them all it's rather absurd to start assuming it can't be.

[troldan]

i havent logged in yet today but i usually can go 6 hours or so without a crash less if i run across alot of zones.

I have 4gb ram on vista 64 and a 8800 gtx.
the symptoms of an incomming crash are usually nothing.
I may have a stutter before the crahs but stutters happen too much to tell me its gonna crash.
usually i'm smooth as silk and then boom crash.
hoepofully this is the mem leak they fixed.

[Starfall]

Memory leaks are a pig to find and fix, hence the rise of languages with automatic garbage collection like C# and Java. They may not match C++ for performance, but they improve reliability.

Until then, give the guys at Sigil time. They should find most of them eventually.

[Evan]

i havent logged in yet today but i usually can go 6 hours or so without a crash less if i run across alot of zones.

I have 4gb ram on vista 64 and a 8800 gtx.
the symptoms of an incomming crash are usually nothing.
I may have a stutter before the crahs but stutters happen too much to tell me its gonna crash.
usually i'm smooth as silk and then boom crash.
hoepofully this is the mem leak they fixed.

Thats because the computer tries its hardest to make everything work correctly. And then it becomes too much for the PC to handle and it screams "OHSHI-" and drops it, well, like its hot.

And its MONGOOSES!

[Aegorian]

Whatever they fixed, it sure as hell didn't make me crash one lick less frequently.

Note that not all memory leaks affect all people. It may be a leak bound to a certain area of the game or a certain mechanic being used. This fix may impact some people, like yourself, not at all.

[Kiste]

Ok, seems I was full of it in my previous posting. It's not that the game doesn't crash one lick less frequently like I claimed before. I now crash so often, it's unplayable. Running around in Trush crashes me every 10 minutes. Used to be one crash per hour or so (which most the time results in death in this game).

[Aegorian]

Ok, seems I was full of it in my previous posting. It's not that the game doesn't crash one lick less frequently like I claimed before. I now crash so often, it's unplayable. Running around in Trush crashes me every 10 minutes. Used to be one crash per hour or so (which most the time results in death in this game).

post your log file. If that's the case it's either a VERY aggressive leak or something else.

[Kiste]

post your log file. If that's the case it's either a VERY aggressive leak or something else.

Logfile looks the same as everyone's. Out of virtual memory, can't locate path yadda yadda yadda. Has been posted a gazillion times. Plus, I send the crash report every time.

[Swish]

I dont know about the memory leak but I am crashing like I never have before. For no reason, out in the open. Keeps happening

[Aegorian]

Logfile looks the same as everyone's. Out of virtual memory, can't locate path yadda yadda yadda. Has been posted a gazillion times. Plus, I send the crash report every time.

What area are you two in?

[Kiste]

What area are you two in?

It happens everywhere on every char. In some areas (Tursh, Trengal Keep) more frequently than in others. Prolly has something to do with the amount of players, NPCs and Mobs in the area. Also, chunking reduces the time between crashs.

[spajdr]

I always end here, when it crashed last time, it took like 1.1GB RAM, free was 450-500MB .. swap file is set to 768MB, so total memory is 2768MB.
It doesnt eat so much memory as before, and also release some, but still it crashes.

#define CalculateAmbient AmbientFormulaColor
#define CalculateSpecular SpecularFormulaLightingCubePointLinear
#define CalculateLighting LightingFormulaLightingCubePointLinear
#define USES_LIGHTS 0
#define CalculateAlbedo AlbedoFormulaTexture
#define CalculatePixelNormal PixelNormalFormulaTexture
#define CalculateOpacity OpacityFormulaNone
#define CalculateTintedColor TintedColorFormulaTexture
#define Calcula
[02/22/07 20:17:03] ERROR: Error: -- PS_UberShader -- Setting: Def_UsesUVs = 1
[02/22/07 20:17:03] ERROR: Error: -- PS_UberShader -- Setting: Def_UsesDetailLevel = 3
[02/22/07 20:18:02] ERROR: Error: PS_UberShader (pixelShader#2 ): internal error: production failed!
UberShaderFragments.h(389): error X1500: syntax error : unexpected token 'i'
UberShaderFragments.h(391): error X1500: syntax error : unexpected token 'e'
UberShaderFragments.h(393): error X1500: syntax error : unexpected token 'e'
UberShaderFragments.h(417): error X1500: syntax error : unexpected token 'd'
UberShaderFragments.h(418): error X1500: syntax error : unexpected token 'd'
UberShaderFragments.h(419): error X1500: syntax error : unexpected token 'd'
UberShaderFragments.h(590): error X1500: syntax error : unexpected token 'd'
UberShaderFragments.h(591): error X1500: syntax error : unexpected token 'd'
UberShaderFragments.h(592): error X1500: syntax error : unexpected token 'd'
UberShaderFragments.h(593): error X1500: syntax error : unexpected token 'd'
PS_UberShader.fx(6): error X1500: syntax error : unexpected token 'i'
PS_UberShader.fx(19): error X1500: syntax error : unexpected token 'e'
PS_UberShader.fx(20): error X1500: syntax error : unexpected token 'i'
PS_UberShader.fx(23): error X1500: syntax error : unexpected token 'e'
PS_UberShader.fx(43): error X1500: syntax error : unexpected token 'i'
PS_UberShader.fx(45): error X1500: syntax error : unexpected token 'e'
PS_UberShader.fx(47): error X1500: syntax error : unexpected token 'e'
PS_UberShader.fx(72): error X1500: syntax error : unexpected token 'i'
PS_UberShader.fx(74): error X1500: syntax error : unexpected token 'e'

[02/22/07 20:18:02] ERROR: Error: // Passes Last Frame: 0 Constants Set Last Frame: 0
// MaxVersion 0x201 this version 0x200
#define CalculateAmbient AmbientFormulaNone
#define CalculateSpecular SpecularFormulaNone
#define CalculateLighting LightingFormulaPointLinearPointLinear
#define USES_LIGHTS 0
#define CalculateAlbedo AlbedoFormulaTimes
#define CalculatePixelNormal PixelNormalFormulaTexture
#define CalculateOpacity OpacityFormulaNone
#define CalculateTintedColor TintedColorFormulaNone
#define CalculateSpecularMaterial Specula
[02/22/07 20:18:02] ERROR: Error: -- PS_UberShader -- Setting: Def_UsesUVs = 1
[02/22/07 20:18:02] ERROR: Error: -- PS_UberShader -- Setting: Def_UsesDetailLevel = 3
[02/22/07 20:19:20] ERROR: Error: VirtualAlloc FAILED for 69632 bytes
[02/22/07 20:19:20] FATAL: Critical: Ran out of virtual memory. This condition may be caused by a lack of available space on your hard-drive.
[02/22/07 20:19:20] FATAL: Critical: Windows GetLastError: Systém nemo~e nalézt uvedenou cestu. (3)
[02/22/07 20:19:20] FATAL: Exit: Executing UObject::StaticShutdownAfterError
[02/22/07 20:19:20] FATAL: Exit: Executing UWindowsClient::ShutdownAfterError
[02/22/07 20:19:20] FATAL: Exit: OpenAL Audio subsystem shut down.
[02/22/07 20:19:21] FATAL: Critical: FMallocWindows::Malloc
[02/22/07 20:19:21] FATAL: Critical: FMallocWindows::Realloc
[02/22/07 20:19:21] FATAL: Critical: 7FF50000 67608 FArray
[02/22/07 20:19:21] FATAL: Critical: FArray::Realloc
[02/22/07 20:19:21] FATAL: Critical: 2817*24
[02/22/07 20:19:21] FATAL: Critical: USpriteEmitter::RenderParticles
[02/22/07 20:19:21] FATAL: Critical: DeferredParticles
[02/22/07 20:19:21] FATAL: Critical: VgPlanetScene::RenderScene
[02/22/07 20:19:21] FATAL: Critical: VgPlanetScene::RenderLevels
[02/22/07 20:19:21] FATAL: Critical: (Pos=48876.48, 4470.28,38535.80)
[02/22/07 20:19:21] FATAL: Critical: UGameEngine::Draw
[02/22/07 20:19:21] FATAL: Critical: UWindowsViewport::Repaint
[02/22/07 20:19:21] FATAL: Critical: UWindowsClient::Tick

plus many of these errors also
[02/22/07 20:02:17] WARN: Warning: Failed to load 'Sound CombatSounds.SlashVToughHideCritical': Failed to find object 'Sound CombatSounds.SlashVToughHideCritical'
[02/22/07 20:02:17] INFO: Log: Failed to load 'Sound CombatSounds.SlashVToughHideCritical': Failed to find object 'Sound CombatSounds.SlashVToughHideCritical'

[Deinnun]

Yes there are still leaks in the game, I got one such crash tonight. I did not notice much of an improvement. I think the garbage collector has troubles finding stale data to dump. Typically, the more you travel the faster you will hit the crash point.

As soon as VG reaches 2Gb it will crash, it can't go beyond that no matter how big the page file is.

[Puffy]

Yes there are still leaks in the game, I got one such crash tonight. I did not notice much of an improvement. I think the garbage collector has troubles finding stale data to dump. Typically, the more you travel the faster you will hit the crash point.

As soon as VG reaches 2Gb it will crash, it can't go beyond that no matter how big the page file is.

not much improvements here either, the more chunks you visit, the more likely the chances of crashing. I stayed in a chunk for 4 hours and didnt crash once. Started traveling back to town and get CTD.

Also using the highest performance textures helped alot.

[popsicledeath]

They said the fixed a specific memory leak.

Nothing was said about all of the leaks.

AKA they didn't do anything but throw us a bone to chew on while we're about to be taken out back and shot...

[freefall99]

I used to crash to all the time when traveling a lot. So now I make it a habbit to /flush once I chunk. This helps keep the memory usage minimal.

[spajdr]

I used to crash to all the time when traveling a lot. So now I make it a habbit to /flush once I chunk. This helps keep the memory usage minimal.

flush changes nothing for me, it crash for me even if i got plenty of RAM.
Even sometimes /flush makes game to crash, when using it.

[imready2go]

Note that not all memory leaks affect all people. It may be a leak bound to a certain area of the game or a certain mechanic being used. This fix may impact some people, like yourself, not at all.

Very true. I do not have a high-end machine (P4 3.0, 2GB Ram, Nvidia 6800) and my hard drive has almost no open space (wife has a 100GB video project hogging most of the HD). Yet I haven't crashed since Beta. Hitching and lag, sure, but never a CTD. And notice that the people who suffer these "memory leaks" the most often seem to have pretty nice machines?

Is it possible there's something else going on besides a memory leak? Wouldn't a memory leak effect everyone pretty equally?

[Boxster]

Very true. I do not have a high-end machine (P4 3.0, 2GB Ram, Nvidia 6800) and my hard drive has almost no open space (wife has a 100GB video project hogging most of the HD). Yet I haven't crashed since Beta. Hitching and lag, sure, but never a CTD. And notice that the people who suffer these "memory leaks" the most often seem to have pretty nice machines?

Is it possible there's something else going on besides a memory leak? Wouldn't a memory leak effect everyone pretty equally?

That's a very good point, I remember in beta I use a p4-2.8ghz, 6800gt and 1 gig ram and I haven't crash a bit. Now I have e6600, 2gig ram, 8800gtx, I crash when I ran out of physical memory. I have a seperate monitor showing my memory, it starts at around 1000k left once loaded in game and it just keep drop and drop, /flush will bring it up a bit, but eventually when down to 100k or less it will crash. I have notice sometimes it crash at 400k+ too randomly. This patch did nothing for me in terms of memory leak fix. :(

I now play in balance mode so that I can last longer in game.

[Garjala]

That's a very good point, I remember in beta I use a p4-2.8ghz, 6800gt and 1 gig ram and I haven't crash a bit. Now I have e6600, 2gig ram, 8800gtx, I crash when I ran out of physical memory. I have a seperate monitor showing my memory, it starts at around 1000k left once loaded in game and it just keep drop and drop, /flush will bring it up a bit, but eventually when down to 100k or less it will crash. I have notice sometimes it crash at 400k+ too randomly. This patch did nothing for me in terms of memory leak fix. :(

I now play in balance mode so that I can last longer in game.
I almost never crashed until Sigil put in 15th day patch. After that crashes due to memory leaks have been more or less frequent.

[Cushdaddy]

Ok, seems I was full of it in my previous posting. It's not that the game doesn't crash one lick less frequently like I claimed before. I now crash so often, it's unplayable. Running around in Trush crashes me every 10 minutes. Used to be one crash per hour or so (which most the time results in death in this game).

Same thing happened to me. I used to get booted every hour or so but now its a VERY common thing.

[Sunderban]

Ok, seems I was full of it in my previous posting. It's not that the game doesn't crash one lick less frequently like I claimed before. I now crash so often, it's unplayable. Running around in Trush crashes me every 10 minutes. Used to be one crash per hour or so (which most the time results in death in this game).

thats been my exact same experience. it was around once an hour before now its every 10 minutes or so....sometimes 2-3 times in 10 minute span.