Abnormal Program Termination? Read this.

[Evilmog]

I, like many of you, have come across that awesome C++ Library error.

Next time you crash with the same error, open your dbg.txt (Via your EQ/logs folder) and see if you see a line that says:

ERROR: Missing or corrupt datafile: Spdat.eff

Everyone of my crashes all had that one line in common, just before the disconnect line. And it wasn't just server specific, it was client specific.

A google search of just that phrase lead me to this:

http://forums.station.sony.com/eq/po...opic_id=172074

Now yes, that thread is old as hell (2010) but as I read through it and experimented with my client, I noticed I too was running into the same issues right before a crash, my commit size pushing 2GB, and in some cases exceeding it while idle (In which case I could still function in the zone I was in, but any attempts to zone would crash the client completely).

Reading through it I tried some of the suggestions posted by the Dev, one of which solved my crashing issue. In Options - Display - Advanced there's a Memory Mode option. Turning that from Most Memory Usage (Which appears to be default as that's what was selected in my UF client) to least memory usage, stopped all zoning crashes entirely.

So just tossing this out there, for many of you with top of the line gaming machines and have more than enough resources to feed EQ, EQ (as a 32 bit program) can only handle using so much before the known (and unknown) memory leaks will force a crash.