2011-01-06, 07:35 AM
SaptaZapta Wrote:So frustrating.... I wish I could just go into their offices, log in on a debug client connected to the production servers, crash it, and get cracking.
I've never seen their code but I've been programming in C and C++ for over 25 years, including troubleshooting other people's code (one of the yuckier tasks a programmer can face, btw).
I assume the "weights" have to do with the size of the data structures used to store the items, which obviously means they are somehow copying inventory data into "temporary" storage - and causing a data overrun in certain situations. Memory smears (data overrun) are nasty, but they can be found. Let me at the goddam code!
Or at least get somebody with the error 38 problem log on from your comps and get you a full crash dump... eTracer is obviously not doing the job
They should have programmers like you at Nexon.



