Guild Wars 2

These world boss crashes are getting real tiring. How many times do I need to submit these similar callstacks?
I crash almost daily at Karka Queen, or Shatterer. Today, I crashed at both.

I don’t crash anywhere else. I think in the years I’ve been playing, I’ve had one (1) crash that wasn’t at a world boss.

I have been sending in callstacks for over a year now for crashes at world bosses, and while I’ve not been looking that closely at them, they almost always look the same. These crashes showed up around the time the culling feature was removed (when was that, a year and a half ago?)

And no, I’m not interested in playing at “low quality” settings. That is a BS solution, and by doing that stupid workaround, Anet won’t get the volume of callstacks they should be getting over this ridiculous issue.

Further, I play 99% of my gameplay with everything maxed, and there is no preset for that. High only sets about half the settings to max. I still have to go in and manually set half the settings higher after I choose the high preset. I’m not interested in fiddling with a dozen settings multiple times a day just to workaround some crashes that should have been fixed a long time ago.

Please, for the love of {deity} put some priority on fixing these crashes. I have sent you countless callstacks now. The issue is easily reproducible:
1) Go to a world boss where a zerg collects
2) Auto attack boss and wait
3) Crash

Please post the crashlog.
You can find it here:
C:\Users\YourUsername\AppData\Roaming\Guild Wars 2\ArenaNet.log

Ironically, by posting, it took a couple days to encounter another crash.
Attached is tonights crash at shatterer….

Looks pretty familiar… projectiles that don’t exist…

I have the same problem

Here’s tonight shatterer crash…

more projectiles in the logs

@Renwa: Are you running any other memory-intensive programs while playing gw2?

@op: If it doesn’t bother you too much you could reduce Character Model Limit to low and uncheck High Res Character Textures. Everything else can still be at max.
That stopped these crashes for me.

Tonight’s Shatterer crash…

@Tura
What’s the point of a setting if it can’t be used. Clearly there’s something wrong here and it needs to be fixed.

This would be better served over in the Tech Support sub-forum.

Good luck.

Tonights KQ Crash…

Tonights KQ crash…

I would suggest deleting your local.dat, which is now located at “C:\Users\<YOURUSER>\AppData\Roaming\Guild Wars 2” by default.

Also run a repair by adding -repair to the end of the client shortcut once. (Be sure to remove it after finishing the repair).

Keep in mind deleting local.det will cause you to lose some of your settings in options, like sound volume and quality as I recall.

This usually helps me immensely with the rare CTD’s that invariably seem to crop up.

Halcyon.7352:

I would suggest deleting your local.dat, which is now located at “C:\Users\<YOURUSER>\AppData\Roaming\Guild Wars 2” by default.

Also run a repair by adding -repair to the end of the client shortcut once. (Be sure to remove it after finishing the repair).

Keep in mind deleting local.det will cause you to lose some of your settings in options, like sound volume and quality as I recall.

Sure, I’ll do this again… I’m honestly not expecting it to do anything this time as opposed to the other times… I’ll either keep posting call stacks, or I’ll post that the issue has magically gone away. We’ll see what happens.

Halcyon.7352:

This usually helps me immensely with the rare CTD’s that invariably seem to crop up.

If this was a “rare CTD”, I wouldn’t be making a post like this. This is a reproducible issue that happens almost every single time I perform the repro steps. While I can’t make 100% statements, based on what I’ve seen, this is a widespread issue based on the game engine not being able to handle what Anet is claiming it can. The repeated and fairly similar callstacks support this.

and tonights KQ crash…

I did another repair and delete local.dat after this crash, so we’ll see what happens from the post above.

And tonights KQ crash…

Proof the local.dat delete + gw.dat repair did nothing…

Did you ever post this over in tech support, since this probably isn’t a game bug? And have you submitted a ticket with support to see if they could help?

RoseofGilead.8907:

Did you ever post this over in tech support, since this probably isn’t a game bug?

What makes you think this isn’t a bug? Please back up your statement.

Here’s some major indicators that it is a bug:
- The crash occurs in an almost identical fashion every time. If this were a hardware issue on my end, the callstacks would not be consistent as the hardware would simply crap out at a random spot anytime it hit load. Consistent callstacks is a good indication of a bug in that location of the code.
- This appears to be a widespread issue, given that almost everyone who discusses it talks about dropping their quality settings to workaround. You are welcome to read above about my opinion on low quality settings as well as about providing Anet with proper statistics on how their game actually performs.
- Finally, the crash showed up at the same time as they introduced a new feature – the removal of culling. That’s a bit too coincidental for me.

And without further ado, tonights KQ crash.

And tonight was a touch different. Tonight the crash catching portion of the game also died immediately. It did not let me even do the direct submissions of the callstack tonight.

Tonights KQ crash…

Crash Tequatl. Same problem. Can you help?

Tonights Crash, strangely similar to the other crashes… I was lucky tonight. I was able to login in time and have a group that got me back into the same district to get credit.

Kuka, that crash looks similar to mine

A Modniir Ulgoth crash tonight too! I am surprised by this as this is the first time I’ve crashed there (that I can remember). Callstack still looks similar, no surprise there.

I had 3 crashes on Jourmag last night and also 3 crashes when activating Plinx on Cursed Shore.. this is getting pretty frustrating now seems more and more events are becoming unplayable for me.. no point starting events knowing the risk of being booted out of maps and every chance your time is wasted, I mean its already hard enough to get into doing some events unless you arrive 30mins -1hr early without all these mullarkey as well.

Chad Taylor.3487:

DougTheSlug.3920:

These world boss crashes are getting real tiring. How many times do I need to submit these similar callstacks?
I crash almost daily at Karka Queen, or Shatterer. Today, I crashed at both.

I don’t crash anywhere else. I think in the years I’ve been playing, I’ve had one (1) crash that wasn’t at a world boss.

I have been sending in callstacks for over a year now for crashes at world bosses, and while I’ve not been looking that closely at them, they almost always look the same. These crashes showed up around the time the culling feature was removed (when was that, a year and a half ago?)

And no, I’m not interested in playing at “low quality” settings. That is a BS solution, and by doing that stupid workaround, Anet won’t get the volume of callstacks they should be getting over this ridiculous issue.

Further, I play 99% of my gameplay with everything maxed, and there is no preset for that. High only sets about half the settings to max. I still have to go in and manually set half the settings higher after I choose the high preset. I’m not interested in fiddling with a dozen settings multiple times a day just to workaround some crashes that should have been fixed a long time ago.

Please, for the love of {deity} put some priority on fixing these crashes. I have sent you countless callstacks now. The issue is easily reproducible:
1) Go to a world boss where a zerg collects
2) Auto attack boss and wait
3) Crash

Thanks for submitting your log files. I’ve found your corresponding crash reports and we will look into the issue immediately.

The skinny is that it looks like we’ve allowed you to shoot yourselves in the foot with maxed out graphics settings combined with crazy boss zergs. The GW2 client is a 32bit process which has access to just 4gb of RAM, even less in practice due to fragmentation in high churn environments like a zerg fest. I can see from your log files that you are hitting an upper limit of about 3.5 gb of allocated memory before crashing on a failed allocation(i.e. running out of memory).

In the meantime here are some things you can turn down that will free up some memory in zergs without compromising graphics too much:

-Disable “High-Res character textures”
-Ease back on “Character Model Limit” and “Character Model Quality”
-Ease back on “Lod Distance”

The memory use for characters can roughly be described as = character count * character quality * 4 (if high-res is enabled).

Report back if those changes don’t help and I will do the same when we have a fix in-bound.

im hoping this explains maybe my situation as well. Since I crash both in zergs and in populated areas.

I just hope anet is working on a 64bit in the background >.>

edit: and actually YES! Those are the same errors I get when playing!

Try using this:
http://www.techpowerup.com/forums/threads/large-address-aware.112556/

It is used on 32bit games like Sins of a solar empire to be able to use another gig or so of RAM, and I have used it on this since I purchased the game last October, with only 2 crashes or so over the course of my entire GW2 playtime. Give it a shot, easily undo’s itself if you don’t want it or it doesn’t work.

Chad Taylor.3487:

DougTheSlug.3920:

These world boss crashes are getting real tiring. How many times do I need to submit these similar callstacks?
I crash almost daily at Karka Queen, or Shatterer. Today, I crashed at both.

I don’t crash anywhere else. I think in the years I’ve been playing, I’ve had one (1) crash that wasn’t at a world boss.

I have been sending in callstacks for over a year now for crashes at world bosses, and while I’ve not been looking that closely at them, they almost always look the same. These crashes showed up around the time the culling feature was removed (when was that, a year and a half ago?)

And no, I’m not interested in playing at “low quality” settings. That is a BS solution, and by doing that stupid workaround, Anet won’t get the volume of callstacks they should be getting over this ridiculous issue.

Further, I play 99% of my gameplay with everything maxed, and there is no preset for that. High only sets about half the settings to max. I still have to go in and manually set half the settings higher after I choose the high preset. I’m not interested in fiddling with a dozen settings multiple times a day just to workaround some crashes that should have been fixed a long time ago.

Please, for the love of {deity} put some priority on fixing these crashes. I have sent you countless callstacks now. The issue is easily reproducible:
1) Go to a world boss where a zerg collects
2) Auto attack boss and wait
3) Crash

Thanks for submitting your log files. I’ve found your corresponding crash reports and we will look into the issue immediately.

The skinny is that it looks like we’ve allowed you to shoot yourselves in the foot with maxed out graphics settings combined with crazy boss zergs. The GW2 client is a 32bit process which has access to just 4gb of RAM, even less in practice due to fragmentation in high churn environments like a zerg fest. I can see from your log files that you are hitting an upper limit of about 3.5 gb of allocated memory before crashing on a failed allocation(i.e. running out of memory).

In the meantime here are some things you can turn down that will free up some memory in zergs without compromising graphics too much:

-Disable “High-Res character textures”
-Ease back on “Character Model Limit” and “Character Model Quality”
-Ease back on “Lod Distance”

The memory use for characters can roughly be described as = character count * character quality * 4 (if high-res is enabled).

Report back if those changes don’t help and I will do the same when we have a fix in-bound.

I’m rarely critical of ANet, but…

Given that 64-bit has been the norm since well-before GW2’s release, given that 64-bit is not even vaguely hard (I’m a 35 year veteran coder who develops scientific software, lotsa fancy graphics), given that C++ is very capable of producing bit-width agnostic code…

…why in heck is GW2 32-bit? 3rd party library dependencies? Old code ported from 32-bit GW1?

“*—> Crash <—*
OOM: Heap, bytes=1048624, "

OOM = out of memory error
can only be prevented by restarting the game more often because of memory leaks or turning down your graphic settings (ugh)

GW2 really needs a 64bit exe, even WoW and WildStar have it. I have been asking for a 64 bit exe since release, but no luck so far

I’m asking for a 64bit Client already since a loooong time, together with DirextX11 Support…

I hope we will see these heavy performance upgrades finally one day, maybe hopefully with the next Feature Pack, that would be awesome.

I also have performace problems with my memory when I’m in WvW and huge zergs clash into each other, then i also crash with the same errors, mostly when the zergs raise over 40-50+ people. Being self in such a big group is no problem weirdly, but just if run into an enemy group of such a size, then bang, and game off

I wish these changes would be made soon, so that playing WvW with max settings and hittign such zegs wouldn’t result into crashes, , maybe a bit lags or so – can lieve with that, so rarely as you clash with huge zergs, but not crashes, which are just only frustrating.

64bit and DX11 would give the game a significant performance boost I’m sure for alot of people.

Chad Taylor.3487:

In the meantime here are some things you can turn down that will free up some memory in zergs without compromising graphics too much:

-Disable “High-Res character textures”
-Ease back on “Character Model Limit” and “Character Model Quality”
-Ease back on “Lod Distance”

Thank you for your response, and specifically providing the settings that will have the most impact.
There are a lot of people out there who already discuss those workarounds, but the information is typically a pretty generic “turn your settings down”.

Report back if those changes don’t help and I will do the same when we have a fix in-bound.

I’ll see how much I need to scale back to prevent the crashes.
My first steps involved:
Character Model Limit: Highest → High
LOD Distance: Ultra → High
I’ve not really been in a situation though these last couple days that would have triggered a crash. I’ll see if I need to go any further, I hope not as I’d prefer to keep whatever I end up at as permanent settings so I don’t need to flip them multiple times a day.

Here is my current ArenaNet.log
(contains 18x OOM:Heap since April 2014)

EDIT:

Try using this:
http://www.techpowerup.com/forums/threads/large-address-aware.112556/

It is used on 32bit games like Sins of a solar empire to be able to use another gig or so of RAM, and I have used it on this since I purchased the game last October, with only 2 crashes or so over the course of my entire GW2 playtime. Give it a shot, easily undo’s itself if you don’t want it or it doesn’t work.

Guild Wars 2 has already LAA that was set by default from ArenaNet.

DougTheSlug.3920:

Chad Taylor.3487:

In the meantime here are some things you can turn down that will free up some memory in zergs without compromising graphics too much:

-Disable “High-Res character textures”
-Ease back on “Character Model Limit” and “Character Model Quality”
-Ease back on “Lod Distance”

Thank you for your response, and specifically providing the settings that will have the most impact.
There are a lot of people out there who already discuss those workarounds, but the information is typically a pretty generic “turn your settings down”.

Report back if those changes don’t help and I will do the same when we have a fix in-bound.

I’ll see how much I need to scale back to prevent the crashes.
My first steps involved:
Character Model Limit: Highest -> High
LOD Distance: Ultra -> High

First steps didn’t quite cut it. While I wasn’t crashing all the time, I was still encountering some crashes.
Shatterer → wasn’t crashing anymore
KQ → Still encountering crashes

My settings are now turned down accordingly:
LOD Distance: Ultra → High
Character Model Limit: Highest → High
Character Model Quality: Highest → High

It would be nice if there was an ultimate quality pre-set
- This way I can drop the quality to “best appearance” (oh the irony) for these events, and quickly go back to all max using some sort of “all maxed” preset

Guys, it’s quite easy to explain I have the same problems for over 4 month let me tell you what exactly is the problem. You often said you get disconnect at Shatterer or KQ but I think the problem is that you did many world bosses before too, right? Because, when I do the daily world bosses (like 12 bosses) after 10 world bosses the ram usage for guild wars 2 is over 3GB and it’ll crash. It then often crashes with Shatterer or KQ because they need the most ram usage but the problem aint those two boss. And I’m playing with High/High/High the same like you and it crashs after 10 world bosses so if you want to do alle world bosses in one go you need to set character model limit and quality to low then it might work. There should really be a fix.

“The skinny is that it looks like we’ve allowed you to shoot yourselves in the foot with maxed out graphics settings combined with crazy boss zergs.” – Chad Taylor

This makes no sense, you people programmed it, you should know its limits right? Why does the Auto setting give me these settings? Why won’t the game then at least automatically adjust the graphics if zerg present?

When I first started playing GW2, it was awesome… to have DC or CTD after every 30 minutes.
Do you know what EMET is? One of those GW2’s CTDs is actually very dangerous to PC. “buffer overflow”, I think. GW2 managed to destroy my friend’s PC. Luckily I have my GW2 under the eye of EMET.

So I got kittened off. What kind of game is this, that doesn’t run on modern hardware, that cost me 1000€ to put together. A game not worth.
I started to change GFX settings one by one, every day, trying to figure out what makes me crash, what not.
For myself I found this out:
Textures above Low = DC/CTD
Character Model Quality above Lowest = DC/CTD
The rest of the settings do not matter, can have them on/off or maxed. It’s just those 2 that are fatal to GW2. Cannot have those 2 above minimum.

This game is rushed and dangerous. Malware. I have never seen so poor programming.

In light of the recent graphical updates…

We’ve added new graphics options for players with higher-end machines.
Tune the look of your scene with ambient occlusion or light adaptation.
Choose between two extra antialiasing options: SMAA Low and SMAA High.

Do we have any updates on these other settings that can trigger crashes?

I get the exact same crash as well … never used to happen until a couple of weeks ago.
wish they would fix this … its becoming rather irritating.

Ok well this is related to the same issues that I have been having.

The problem is crappy. Like really crappy. Like totally pathetic by ArenaNet programming. In fact for some areas I can not run other than low quality graphics. Else Insta Crash. And even with Low Quality Graphics it is a bit hit and miss. Now this is mostly the case in High Population Areas like Lions Arch.

IF ArenaNet had a half pie smart Development Environment Control this would not be an issue.

BUT and it is a killer for them. Until they sort it out. Pay for an expansion when I can not reliably play what I have paid for. What a bunch of deluded people. How about you sort out your version control and your DEV issues. Provide a stable platform for a start?

Just a suggestion because it is not being run on a minimal environment. But the only program that causes a problem is GW2. That says to me that the problem is GW2 and crap developers.

10 months later and this still hasn’t been fixed. I’m not even surprised. Here is my log, please get this fixed it’s really not that difficult.

Fallen.4960:

Ok well this is related to the same issues that I have been having.

The problem is crappy. Like really crappy. Like totally pathetic by ArenaNet programming. In fact for some areas I can not run other than low quality graphics. Else Insta Crash. And even with Low Quality Graphics it is a bit hit and miss. Now this is mostly the case in High Population Areas like Lions Arch.

IF ArenaNet had a half pie smart Development Environment Control this would not be an issue.

BUT and it is a killer for them. Until they sort it out. Pay for an expansion when I can not reliably play what I have paid for. What a bunch of deluded people. How about you sort out your version control and your DEV issues. Provide a stable platform for a start?

Just a suggestion because it is not being run on a minimal environment. But the only program that causes a problem is GW2. That says to me that the problem is GW2 and crap developers.

I’m not saying your problems aren’t something to be upset about, because I’d definitely be pretty upset if I was crashing all the time…

But I never get client crashes unless I press F12 and spam the space button or something like that (force-closes client).

I have a 4.5 year old laptop too. Don’t be too quick to blame anet.

funny thing, happens to me too. dunno if there have been changes but ive got a high end engine, cuts everything easily just KQ crashes regularly
ill try the settings adapt and see how it goes
really annoying

Roughly a year ago, I turned my settings down. I noticed ugly as heck models showing up in large zergs, and an overall slight reduction in how the game looks, but I at least stopped crashing.

Since the release of HoT, I have been noticing more and more crashes. Some are no doubt bugs in the new code that are slowly being worked out, but I’ve crashed at Teq 2 days in a row now, OOM for both of them.

This seems to indicate that the situation has not actually been improved (no idea if any effort has even been put into this?) but is slowly getting worse. No doubt, more skins, more models, more this and that, and suddenly we need to turn down our settings even more so the game looks even worse?

Do we have any updates on this show stopping issue?

Thanks for finding and bumping this. Post from Chad confirms what I was suspecting from the last few days. It is just sad that it’s been a year and as it is clear, no fix was yet implemented. As game grows and more assets are added (HoT is a major release), this problem will become more and more widespread. The problem is that getting better hardware wont help, ever. You can have 64 GB of RAM and double SLI GeForce 980 and it WILL still crash due to reaching memory limitation of GW2’s software architecture. So eventually we will all have to put our texture settings to lowest and make GW2 look like a potato just to stop OOM crashes? Once HoT content related bugs are found and patched this should be the top priority issue for Arena’s programmers.

Its seem the more skin and skill effect add after this expansion make this game a memory hog. I usually crash on zerging event. Running on lowest setting seems to be helped prolong the crash. But when HoT live I crash every 5 minute .

After chance my OS from window7 32bit to 64 bit version there almost no crash eversince while running medium setting.

Want to bump this again. Setting textures to lower quality significantly reduces memory usage during big events (like world bosses). With everything on High/Ultra the GW2 process constantly hits the 3.x GB boundary and crashes. Time for a 64 bit GW2 client.