[Wotlk] Server Crash about mangosbot-bots HOT 5 CLOSED

Through the whole time the server ran "ERROR:Player::addSpell: nonexistent in SpellStore spell #75460 request." was spammed pretty much in intervals of few seconds to few minutes.

from mangosbot-bots.

92f85f3e_mangosd.exe_[22-1_17-16-11].dmp

Here is the crash dump file.

from mangosbot-bots.

The provided call stack indicates a crash in a Mangosbot project, specifically in the Boost Asio library, which is commonly used for asynchronous operations in C++. The crash seems to be related to thread handling in Boost Asio and involves waiting for an object.

The relevant parts of the call stack are as follows:

1. Crash in Player::BindToInstance:

   • The crash occurred in the Player::BindToInstance function at line 17959 of the Player.cpp file.
   • The parameter load is a boolean with a memory address 0x76F9C0.

2. Crash in DungeonMap::Add:

   • The crash also occurred in the DungeonMap::Add function at an unspecified line in the Map.cpp file.
   • Local variables include an instance of InstanceGroupBind with an unreadable memory address and a WorldPacket object.

3. Crash in MovementHandler.cpp:

   • The crash is related to a lambda function in MovementHandler.cpp at line 187.
   • Local variables include a Map* pointer, a GenericTransport* pointer, and a BattleGround* pointer, all with unreadable memory addresses.

4. Crash in WorldSession::HandleMoveWorldportAckOpcode:

   • The crash occurred in the WorldSession::HandleMoveWorldportAckOpcode function at line 257 of MovementHandler.cpp.
   • Local variables include a Difficulty enum and a WorldLocation object with coordinates and orientation.

5. Thread Crash in Boost Asio:

   • The second call stack indicates a thread crash in the Boost Asio library.
   • The crash occurred in the timer thread function of the Boost Asio library, waiting for a single object.
   • The crash is related to Boost Asio's internal thread handling.

It seems that there might be a synchronization issue or a problem with threading in the Boost Asio library, possibly leading to a deadlock or a crash. Without the exact code and more context, it's challenging to pinpoint the exact cause. You may want to review the relevant parts of your codebase, paying attention to multithreading issues, object lifetimes, and potential race conditions.

Here are some steps you can take to troubleshoot the issue:

• Check if there are any concurrent accesses to shared resources without proper synchronization.
• Review the usage of thread-related constructs such as mutexes, locks, and condition variables.
• Ensure that objects being accessed by multiple threads are properly managed and not deleted prematurely.
• Consider enabling debugging symbols and obtaining a more detailed stack trace to help identify the root cause.

If possible, provide more context or code snippets related to the mentioned functions, especially the parts involving multithreading and Boost Asio usage, for a more accurate analysis.

This is from ChatGPT, hope this is useful.

from mangosbot-bots.

Ah more information i forgot to disclose. This is a repack i got from Github, i didn't compile this.

from mangosbot-bots.

I haven't had 2005 and 2008 VC Redist installed, i will re-check again with them installed but i am not sure that is the cause of this.

from mangosbot-bots.