try to disable anti-aliasing

I´m running a win7 64bit with 8gb and never had a crash only some rare disconnects (like once in an evening) and mostly the moment I klick the leave station button. I also checked the RAm useage it´s around 45% so its 3,6 GB. I conclude that if I would run on a 32bit operating system to expect crashes due to the amount of addres ram. IMHO the ram usage is not optimized and It might be worthy to investigate. but this is pure speculation. as always if you have hardware above the minimum or optimum you will/might escape such issues.

I have 2 accounts, both characters do everything together. One account regularly crashes, the other never does.
The one that crashes uses the market a lot and has lots of stuff in hangers, my guess is that crashes are related to accessing the database, and has nothing to do with settings or hardware.

What eats the memory? I've never seen either of my clients to run above 1,2gb of memory (even with different graphic setting they used about the same). Running W7 64bit w/ 8gb of ram.

Do you have a in-client tracker connected with memory use?

See, this is what concerns me.

you say its memory running out, but people have 8 gigs +, I have 16 gigs on my home PC and there is no signs of memory running out at all.

My machine at work has 2gig, runs photoshop, outlook, office all manner of software which use lots of memory and I also have 3 printers printing large image files... and it never crashes!

so I call bullshit on the memory running out.

Im going to drive a readyboost drive and disabling the page file on my machine at home, but really, ive send enough dmp file reports now that dev's should have a better idea.

What he's saying is that the process... perpetuum.exe can't use more then 2 gb's of memory... this holds true with every 32-bit application.

from what it sounds like, they are working on trying to figure a way to reduce the 'bloat' in memory which will make these errors less common.

so it doesn't matter if you have 128gb of memory... the limit is the 32 bit architecture of the application.

So I call your bullshit and raise you a failure to comprehend.

Norrdec I'm actually working on such an in-client tracker as we speak, the problem is that it reduces the performance to a level where I'm happy if it gets to the terrain in 20 minutes and reaches 2 seconds per frame speeds.

Yes, the 32 bit architecture of the client is what's causing the issue - a single 32 bit process on any windows system can't use more than 2 gigabytes of memory as it simply runs out of address space (this is because 32 bit applications use 32 bits to point to a memory block, which equals to 4 gigabytes, but half of that is reserved by the system to manage the process). Running multiple 32 bit applications on the same system means that each will be able to use 2 gigabytes, so photoshop and your browser can work side by side without issues. (And if your physical memory would run out the page file comes into play yes)

As for the landmass being the problem that's just not true as we unload the previous map before loading the new one, so it just simply replaces it, and they are of equal size.

The issue is being looked into in depth, don't worry we know what we're doing

Yeah, one of the issues was that the memory tracker was running out of memory Now I'm dumping the data to the hdd to analyze later - says a lot that the first dump was 35 gbytes by the time I got to the login screen.

Yes but its not going to use 2gig's in 30 seconds flat while docked at an outpost doing nothing!

So I call your failure to comprehend and raise you evidence to the contrary

What you're missing is "(the amount of memory in your system doesn't actually matter, a 32 bit executable can only utilize 2 gbytes of it)"

16 Gb of ram, 100 Gb of ram. Ram isn't the issue it's the handling of the allocated memory to the process.

And I believe Syndic to be right. You can open up the cache of the game at any time and check it while you deploy The graph goes crazy. Looks like terrain, texture and models being loaded into memory cause an error/crash. This is why teleporters will usually cause problems. Loading old terrain crossed with new terrain data is conflicting. D:

I'd happily have a 5 second longer deploy time if memory was scrubbed correctly. Then work on lowering the deploy timer!

Whoops see below