A little more analysis for you, Z & Jab.
I added a ton of ACHIEVEMENT__TRACE loggers to almost every function in Achievements*.cpp, and started my world. Things were going along fine, tho slower than I hoped, while I watched my system memory skyrocket (1.2GB fro EQ2World.exe (Debug|Win32)).
Here's the interesting part though. It went through 1469 of our Achievements with no problem (except slowness), and when it got to the for() of achievement # 1470, everything stopped dead. Attaching my log for analysis.
2012-10-21_eq2world_5940.zip
Note: I cannot promise this is not related to queued logging, because I have never sent so much to it before - but it seems a real coincidence that the world stops responding on 1470, doesn't it?
Edit: Well shit, there goes that theory. In Release|Win32, it blew right passed 1470 without stalling. However didn't appear to actually process anything:
...
12:21:56 T Achievements: Start Achievement packet for id: 1469
12:21:56 T Achievements: Start Requirement for: '100 Goblin Slain'
12:21:56 T Achievements: Start Achievement packet for id: 1470
12:21:56 T Achievements: Exit: 'MasterAchievementList::CreateMasterAchievementListPacket'
12:21:56 I Titles: Loading Titles...
12:21:57 D World: Loaded 471 Titles
...
Could DEBUG be halting because 1470 has no data? Grasping at straws now. Sorry.
You do not have the required permissions to view the files attached to this post.