Client crashes when open bot inventory

[Raz0r1337]

Issue type *

Bug

Server/AzerothCore version

newest PB fork

Description *

The client crashes immediately as soon as I open the bot inventory.

Steps to reproduce

1. Go to a retailer
2. Open a bot inventory through MB

Expected behavior *

Bot inventory should be shown instead of a client crash

Actual behavior / Errors

no errors no crashlog or dump

Crashlog / Gist link (optional)

No response

Screenshots

No response

Pre-submission checklist *

• I searched for existing issues that match mine.
• I tested with the minimum set of addons/changes.
• I provided reproduction steps and/or relevant logs.

Additional context

I haven't played much over the last few days, but the problem is fairly new.

[Wishmaster117]

Can you provide me logs in the Errors folder? Have you deleted the content of cache folder, have you any lua error in BugSack? Is it happening when you do something in the inventory or just when you open it?
Are you using regular client or modified client?
Need more informations because on my client can't make it crash.

[Raz0r1337]

None are generated.
I click on the bag icon.
The bot UI appears without any inventory items, then freezes briefly and disappears.

No crash or errors folder.

I use the HD client, at least for the most part.
https://discord.gg/wotlk-3-3-5a-hd-client-858041817043042364

[Raz0r1337]

About Lua errors I have to look a second time with Lua errors on.
It'll take a little while, though.
I'll get back to you as soon as I have time.

[Raz0r1337]

To be honest, I'm not sure right now if I cleared the cache.
I'll check that again just to be safe.

So far, I've only deleted everything from MB in the Wtf/Account folder.

[Raz0r1337]

So, I've tried everything now and disabled all add-ons, but the problem still persists.

“Lua error” and “bugsack” don't explain anything.
When I open the bot's inventory, the window opens but doesn't display any items, and at that exact moment, the game freezes and closes immediately afterward without any message or log.

[Wishmaster117]

Very strange have you compiled with the latest bridge and addon main branche? I tryed in the HD client and have no problem

[Wishmaster117]

Could you capture the native Wow.exe crash with Microsoft Sysinternals ProcDump? Since the client freezes and closes without a Lua error or a WoW crash log, a native process dump would be much more useful here.

Do the following:

1. Download ProcDump from Microsoft Sysinternals.
2. Create this folder:

C:\MultiBotCrashCapture

3. Open Command Prompt as Administrator in the folder containing procdump.exe.
4. Run:

procdump.exe -accepteula -ma -e -t -w Wow.exe C:\MultiBotCrashCapture

5. Start WoW only after ProcDump is waiting for Wow.exe.

6. Reproduce the crash exactly:

   • go to a vendor;
   • open the bot inventory through MultiBot;
   • wait until the client freezes/closes.

7. Do not close the ProcDump console until it has finished writing the dump.

After reproducing the crash, please send me the following:

• the generated .dmp file from:

C:\MultiBotCrashCapture

• the complete ProcDump console output;
• the SHA-256 hash of your Wow.exe:

Get-FileHash "PATH\TO\Wow.exe" -Algorithm SHA256

• the file information for your Wow.exe:

Get-Item "PATH\TO\Wow.exe" | Select-Object FullName,Length,LastWriteTime,@{N="FileVersion";E={$_.VersionInfo.FileVersion}},@{N="ProductVersion";E={$_.VersionInfo.ProductVersion}}

• the exact MultiBot version/commit you are using;
• the exact Bridge version/commit compiled on the server;
• the relevant worldserver log lines from a few seconds before and after the crash;
• confirmation that you completely deleted the client Cache folder before reproducing the issue.

Please also run this immediately after the crash and send the output:

Get-WinEvent -FilterHashtable @{LogName='Application'; StartTime=(Get-Date).AddMinutes(-10)} |
Where-Object {
    $_.ProviderName -in @('Application Error','Windows Error Reporting') -or
    $_.Message -match 'Wow.exe'
} |
Select-Object TimeCreated,Id,ProviderName,LevelDisplayName,Message |
Format-List

That may already show the exception code and the faulting module even if WoW itself does not create anything in the Errors folder.

One important note: a -ma dump contains the full process memory and may contain private information. Please do not upload the .dmp publicly to this GitHub issue. Send the dump to me privately instead. The console output, hashes, versions, and Windows event information are fine to post here.

With that dump we should be able to determine whether the crash happens inside Wow.exe, an HD-client DLL, Direct3D, an overlay, or whether it is triggered by the inventory data itself.

[Raz0r1337]

Yeah, I just updated the core and all addons today to make sure I had everything.
That's strange—it's definitely not the add-ons. It crashes even without add-ons, with just MB.

[Raz0r1337]

Maybe the wow_optimize.dll makes this.
I have to try. It had no bugs so far so I forget using it. 😉

[Raz0r1337]

It's not wow_optimize, but AwesomeWotLK in combination with the newer versions of MultiBot that's the culprit.

[Wishmaster117]

If u provide .dmp file i can take a look

[Raz0r1337]

I'm on it, but I have to make that dump first. 😉

[Raz0r1337]

I've sent you all over Discord. 😉
Thx for looking at this.