a few days ago i encountered an issue were after logging in a character my server would virtual hang and use alot more memory than usual 2-6 gigs worth client wont get responses from server etc.

after some trouble shooting i went to back to an older copy of the database, and everything worked fine.

now today it happened again, and i have been able to reproduce the the issue, but not figure out the actual cause.

steps to reproduce on my system, is to accidntly run the 32bit world server, after i did that the 64bit version will come up fine but when a client logs in seems to hang at loading pet data, for about 10 secs then continues to load the server( when all is working fine Pet data seems to load immediatly

the client will talk to the server for a minute or less then communication appears to stop and cannot play

to fix the issue i reverted to my previous database ( no DB changes were made my me) made another backup, and played for 15 minutes without issue

i shut down server and restarted the 32 bit world server and my problems arose again.
reverted database and all is good,
it looks to me like there is something in the 32 bit servr that is changing my DB that makess it unplayable

Well an easy way to figure out if that is the case is this. Make a copy before, then a copy after. Have both of them loaded in the SQL engine. Have one called something like eqworld_pre and the other called eqworld_post. Now load up ToadSQL and do a database comparison. That will show the difference.

I run the 32bit debug version all the time as it is easier to catch memory leaks then the 64bit version and I haven't noticed this issue. There is an occasion when logging in seems to stall but it eventually goes through and no noticeable increase in memory from the stall.

Jab I have noticed my server has an issue with the stall then eventually goes through as well. Sometimes it hangs and I have to restart client and it usually loads fine. It is not as bad if I have my zone set to load when server starts, but it does happen occasionally.

I plan on dumping my db and installing fresh copy once John gets it where you, or him, can create a db dump from server.

Edit: 64bit btw.

Basically the server is waiting for the zone to start up before it will allow the client to continue loading in. We had the same issue over at VGOEmu I ended up only loading the essentials then starting the packet thread (which use to wait for everything to start) and lettings the longer loading threads like the spawn threads and such load while loading in so the client could continue loading in to a zone that was not already started which fixed almost all of the locking up while loading in to a un-started zone.

WOW! That is some great work Xinux! Hope those guys over at VGO appreciate you. If they don't well... We would treat you right.