Bug - Intermittent CTD or EQ freezes when setting the AdvLoot options from chat link

[Diebold666]

As a developer myself I know how almost worthless this post is since I can't reproduce the problem, but just throwing this data point out in case anyone else has the same issue and thought it was only just them.

For the last week I've had about 15 instances of either crashing to the desktop when selecting one of the Advloot settings (AN, AG, etc) on gear linked through chat (not personal inventory), or freezing all running instances of EQ on my system forcing me to kill all running copies (I three box on my computer). If it's just a CTD, then it's only is the process where I clicked one of the boxes on the item form (I do love this functionality; hopefully DB adds it one day) - the other two instances of EQ keep chugging along just fine. If it's a freeze however, all applications just stop - CPU usage goes to 0, screen freezes and becomes unresponsive (but not grayed out) and I have to bring up task manager to hard kill the processes.

I've rebooted, checked the game files, ran the MQ2 updater - but sadly I can't reproduce it (even if I have the person re-link the item in general chat for me to re-check the box). I've been really lucky about not having any CTDs unless I run MQ2 and EQ for more than 24 hours in the past, so this behavior is unusual.

dbg.txt doesn't give any useful info, as the crash was a minute or so after the final entry (I was dicking around in player housing dumping goods into storage)

[Wed May  9 11:43:36 2018]02024:DoMainLoop: just before first while(!EverQuest.ReceievedWorldObjects).
[Wed May  9 11:43:37 2018]02025:Zone Connect -- Received MSG_SND_WOBJECTS_RESPONSE
[Wed May  9 11:43:37 2018]02026:DoMainLoop: complete after first while(!EverQuest.ReceievedWorldObjects).
[Wed May  9 11:43:37 2018]02027:DoMainLoop: just before second while(!ReadyEnterWorld).
[Wed May  9 11:43:37 2018]02028:Zone Connect -- Sending out a MSG_READY_ENTER_WORLD.
[Wed May  9 11:43:38 2018]02029:Zone Connect -- Received MSG_READY_ENTER_WORLD
[Wed May  9 11:43:39 2018]02030:DoMainLoop: completed second while(!ReadyEnterWorld).
[Wed May  9 11:43:39 2018]02031:Setting up models.
[Wed May  9 11:43:39 2018]02032:Setting up character.
[Wed May  9 11:43:39 2018]02033:Activating music.
[Wed May  9 11:43:39 2018]02034:Initialization complete.
Entering main loop.
[Wed May  9 11:43:39 2018]02035:Memory: Load: 49, Total Phys: 24421, Avail Phys: 12342, Total Page: 48842, Avail Page: 35061, Total Virtual: 4095, Avail Virtual: 2274, FreeBlocks: 2047,12,12,9,9,7,6,6,6,5
[Wed May  9 11:43:39 2018]02036:MaxTextures: 63508k, CurrentTextures: 30186k, HighQualityTextures: 30145k
[Wed May  9 11:43:40 2018]00665:D3DXCreateTextureFromFileEx()    failed to create texture sparkle01.dds    for    particle system.


[Wed May  9 11:48:55 2018]00666:D3DXCreateTextureFromFileEx()    failed to create texture electricj.dds    for    particle system.

I also checked Computer management (this is Win 7), and there were no log entries around the time of the crash under any of the Windows Logs. Lemme know if there's something else I can post / additional logging I can turn on to help track this down.

 

[eqmule]

Did any of the other 15 instances use the advloot window while you where manually clicking the checkboxes? I know I have crashed a few times without MQ2 even being loaded just manually checking loot in the advloot window, so it's likely it's a eq bug not MQ2 related at all.

MQ2 just calls the client function, the exact same function as the client itself calls when it adds items to the loot filters from the advloot window...

 

[Diebold666]

Did any of the other 15 instances use the advloot window while you where manually clicking the checkboxes?

All of the instances with CTD/Freeze was after I clicked a link in general chat for an item to bring up it's stats etc, and I clicked one of the embedded AG, AN checkboxes, only for it to crash/lock at the moment I clicked the checkbox - and my advloot selection is never saved locally when this "bug" happens.

Like I said, it's almost a useless bug report because I can't replicate it - it doesn't seem to be linked to either windows uptime or MQ2/EQgame.exe process runtime.

I should probably try a fresh install as all three clients run on different drives so they don't hit the hard drive platters at the same time slowing things down, and I've only had this problem on the client I use for my main who is also the main looter.

If there's any logging or debug options I can enable to help track this down I'll be glad to give it a shot (short of running wireshark/ sysinternals procmon).