Guild Wars 2

Everytime I use a waypoint out of any zone I crash right to desktop, I can’t begin to explain how bad this sucks while trying to do fractles and ending up being booted from the dungeon my group went to next or just trying to play the game in general.

My system
Windows 7 32 bit – SP1
4 gigs of DDR2
intel core2 Quad Q6600 2.4GHz
Nvidia GeForce GTX 470 – up to date drivers
DirectX 11 – up to date

The Crash

—> Crash <—
Out of Memory: arena=Environment, cat=Map, allocBytes=38630160, arenaBytes=38827128, fallbackBytes=49156, align=0 ,
App: Gw2.exe
Pid: 3320
Cmdline:
BaseAddr: 00400000
ProgramId: 101
Build: 16100
When: 2012-11-20T05:24:30Z 2012-11-20T00:24:30-05:00
Uptime: 0 days 0:11:55
Flags: 0

“Out of Memory: arena=Environment, cat=Map, allocBytes=38630160, "

Speaks for itself.

reduce your settings (textures in particularly) or use bcedit to change the userva limit

I tried to play with video settings lower than the recommended and it still crashes, but Ill try again for a while and report back : thanks

Use a 64-bit windows version. Solved the problem for me and many others….

Not gonna pay for Win7 64 bit to play a 50 dollar game when its something on their end not mine. They need to fix the issues with 32 bit OS rather than leave their customers on the down if thats the case

PS thanks for the advice tho Fu Ling

Cannibalist.4037:

Not gonna pay for Win7 64 bit to play a 50 dollar game when its something on their end not mine. They need to fix the issues with 32 bit OS rather than leave their customers on the down if thats the case

Well, theres surely ways to handle memory management better. Much of it is probably large chunk sizes resulting in excessive heap fragmentation.

The best solution would be to turn the animations to “Low” settings from the graphics options.. It’s the “issue” that draws away most of your RAM.. The rest of the settings are bothering the GPU mostly, so use them as you see fit.. I also use a 32bit OS for gaming, and it’s what worked for me..

It won’t solve the problem in the long run, but it will allow you to play for a longer period of time without the crash.. Note that zoning triggers it eventually no matter what you’ll do, (it usually crashes after 4 to 5 zone changes, personal story not included) but at least you can travel using waypoints with no particular issue..

I personally suspect a “hidden” memory leak, or the client’s inability to determine whether someone uses a 32bit or 64bit OS.. On the other hand, from memory management reports, the game doesn’t exceed 2.5 Gigs of RAM while running, but the error still appears no matter what, even if you have 30% free RAM..

As for your system? You do not have 4 Gigs of RAM if you use a 32bit OS, you have 3.2, as the rest goes unrecognized by the OS.. Only 64bit systems are able to recognize and utilize RAM beyond 3.2 Gigs, so keep that also in mind..

Another solution would be to increase your Windows swap file (Virtual Memory) to 8438MB, but like i say earlier, it won’t create a permanent solution.. The issue is client wise..

You’re all posting on the wrong idea that physical memory (Working set and Private Set) is the most important aspect.

There is another field that is important on Virtual Memory based operating systems, that Task manager has no option to display what so ever.

This Virtual Size, as its known in Process Explorer, is often 500MB-1GB larger than the working set and is why the game is far more likely to crash on 32bit operating systems.

This Virtual Size is also often used to store quick cached copies of video resources so a game can be alt tabbed in and out of quickly without having to rehit the hdd for textures (among other things).

Just opening the GW2 launcher, 1.1GB of virtual space is allocated for the process.
By the time you hit the menu, its at 1.5GB

This is already close to unstable gameplay if it was running on a 32bit operating system.

Once loaded into a map (say Bloodtide) its already operating at 1.7GB’s of virtual. with a 2GB user address space, simply changing to a new map will crash the process.

1.9GB on portalling to lions arch
Bam, theres your crash.

changing the address space distribution on 32bit will help, in some cases, but it can send the OS unstable in many of them.

I have 8gb ddr3 and W7 64bit and I crash all the time using waypoints. Ive seen my virtual memory as high as 2.2gb’s at times…..

I just crashed out using a waypoint in town at Divinity’s reach. I had to ctrl alt del to close Guild Wars 2.