Curse

SJG · Jul 25, 2005, 12:17 PM // 12:17

Guild Wars has been giving me of out-of-memory exceptions lately (since the last update on Thursday), it seems to happen when I switch characters frequently. Sometimes they happen on garbage collection and sometimes on memory allocation, which is probably what you'd expect. I can't give any more details because they do not log them in the windows event log.

Has anyone else been getting these problems?

Numa Pompilius · Jul 25, 2005, 12:42 PM // 12:42

FWIW, I haven't noticed any memory leaks here.

Unforgiven · Jul 26, 2005, 02:31 AM // 02:31

Hmm I havent seen any of that and I have a low end comp. I cant think why it would just do that other than the fact it cant process that much in your gw because your comp. what are your comp specs?

SJG · Jul 26, 2005, 12:52 PM // 12:52

I have a P4 machine with 1 gig of RAM and 256 meg of VRAM, so I don't think my computer's specs are the problem.

It did happen when I was trying to make a list of collectors and swapping accounts (I was getting some decent collectors items for my new character) so I was doing lots of minimizing and maximizing GW and a fair bit of swapping accounts when I managed to get one.

I guess I'll have to keep an eye on GW's memory usage and see if it is eating all my memory.

sledgeunderhill · Jul 26, 2005, 09:19 PM // 21:19

I was experiencing similar errors recently - I have an ATI card and installed ATI tools which allows you to have an on screen display of the amount of texture memory and heap memory being used by the 3d process.

I had been running my GW with heapsize option set to half a gig (under the misguided belief that it would improve performance). With this option on, I noticed crashes within 10 minutes of starting the game. I turned it off, then watched to see how much memory the application was using. It would vary in size, from 175 Mb to around 300 Mb, depending on how large the map area and how populous the town was.

I think that what triggered the errors for me was changing the main processor on my comp. I went from an AMD 64 3000+ to the x2 4400. Different memory structure - or it could be that a memory cell went bad. Or heck, it could have been the way the update changed the handling of a forced heapsize.

Anyhow, run a memtest utility to see if there are hardware errors, if you are using the heapsize option, turn it off, and if you are using an ATI video card, you can try that tool I mentioned to track the memory usage.

Good luck!