Last thing - what is your gfx card? Integrated, standalone? Drivers updated?

Not sure if it's useful for this specifically, since I run multiples, but just some observations from my machines:

32-bit Vista Business, Intel Dual Core 2.20GHz Laptop, 4 GB RAM, ATI Mobility Radeon HD 3650 512MB

One client: medium settings, very few crashes (one or two over the span of days), happened during dock/undock, hadn't left the starting island in those sessions (was doing mining missions), occurred at terminal (Asintec Alpha). Performance slows to a crawl/rubberbanding when opening map.

Three clients: low settings, sound off, unplayable, did notice one of the clients memory footprints skyrockets when the third is started to double the usage of the others (didn't check if it was the one starting or another one, I can if that info would be useful).

Two clients: low settings, sound off (attempted to have sound on, on one client, didn't really work, cut in and out, oddest thing was that it seemed to be effected by the camera position of the client that still had the sound turned off). Occasional crashes (once every one or two days), only one client will crash, occurs at dock/undock, mining again so rarely if ever leave the one island. Occurred at Asintec Alpha, also occurs at terminal on secondary Alpha (handful of people around, but does seem more likely to occur the more others are around, crashes happen less at the secondary Alpha). Loading map causes heavy slowdown, closing map will cause clients to temporarily go "not responding".

64-bit Windows 7, Intel Quad Core 2.67 GHz, 4 GB RAM, ATI Radeon HD 4800 1024MB

Three clients: Low settings, sound off. No crashes over the span of multiple days I've used it so far. Once third client is started, see the large jump in memory footprint again. Will stabilize over long period of time when not moving (sitting still, mining) to all be equal (about 450MB for each footprint). Moving will cause footprints to go up a bit, one client will have a bit of an elevated footprint compared to the others. Docking/undocking will cause the large jump to occur again (not sure if this is every time, or just occasional, can observe more closely if that's helpful). Loading/closing of map will cause slowdown/minor pause, but clients are still responsive.

Hope that information is useful, happy to provide more/help out however I can if wanted/needed

Evening all,

I have the same issue regarding log in, client sits on a half full bar loading up the agent screen, then upto 5 mins waiting with a half full bar before it goes back to the initial screen or dumps me from the game within a few minutes.

Very frustrating, running 64bit Windows 7 on a Mac under boot camp.  I don't have any issues running LOTRO or World of Tanks, or Eve when I played.

Very frustrating.

Regards,

Draul

Just noticed that this was a thread that kinda dealt with the crashing issues so sorry i made a new one out of frustration.

Not to get on your case DevBoy but you have had crashing issues for over 6 months, you have collected what must be 100,000 crash logs or more. When your server had issues with the influx of people a few weeks back you quickly brought in a specialist and within a few days the issue was resolved. It seems pretty obvious there is a serious memory leak in the Perpetuum code, why don't you guys bring in a specialist to resolve this frustrating issue? Pretty please with sugar on top!

Im crashing as well. Whether I am running 3 clients or just one.

And I do not run out of ram either. 8GB of it, each client takes about 1GB (64 bit system but each process 32bit process is given its own 32 bit address space I believe)

The new client that fixes some issues I found will be out with the patch on friday. As I didn't find a definite cause of the problems this might only help the situation and not fix it completely yet. Game stability is still top priority and we're working on it constantly.

Yes, most of the current crashes people experience are due to the client running out of memory, that's why I spent the whole last week looking for any memory leaks or memory pooling issues. None were found, but the client does pool up memory in certain places to speed up the zone changing process - these pools are now reset each time you teleport and so the memory usage pattern will be a lot more consistent at the price of a few seconds of extra load time.
We don't have a custom memory allocator in place.

Internal TP's now stop automatic modules. Previously, it was just external, but now I find the I have to restart my sheild when jumping internally too on Tellesis. I suspect it's part of the

"these pools are now reset each time you teleport "

thanks for the clarification

Wow. Cutting it in half is huge. Maybe worth a blog.

Sweet

This will make us multiboxers lives many times easier.

Why client compiled without LARGEADDRESSAWARE option?