FirelandsProject / firelands-cata

This is an open source project, from the emulator version 4.3.4. Log in to the discord for more information: https://discord.com/invite/GZ5rsxumxN
GNU Affero General Public License v3.0
55 stars 45 forks source link

Bug Report: Server Crashes with few DoT Spells #194

Open Steveboi90 opened 2 months ago

Steveboi90 commented 2 months ago

Current Behaviour

I've encountered a recurring server crash issue related to specific spells. Here's a breakdown of the problem:

Melt Armor Spell Crash: Spell ID: 99532 Issue: When the spell "Melt Armor" is applied and the player teleports away using the .tele command or leaves the instance while the spell is active, the server crashes. Error Output: Segmentation fault (core dumped) Immolate Spell Crash: Spell: Immolate Spell ID: 348 Issue: When "Immolate" is cast on an enemy and the player logs onto another character, the server crashes shortly afterward, similar to the issue with "Melt Armor".

Expected Blizzlike Behaviour

Server should not crash.

Source

No response

Steps to reproduce the problem

For Melt Armor: Apply the "Melt Armor" spell (ID 99532) to a target. Teleport away using the .tele command or leave the instance while the spell is active. Observe the server crash with the output Segmentation fault (core dumped). For Immolate: Cast "Immolate" on a target. Log out and switch to another character. Observe the server crashing shortly afterward.

Extra Notes

Log Level: Set to Debug. Despite this, no additional information pinpointing the error was found in the logs.

The crashes occur regardless of the specific raid or creature involved, indicating the problem lies with the spells themselves rather than the environment or NPCs.

FC rev. hash/commit

FC>Firelands rev. f1b6fc5b51e9 2024-07-31 23:45:08 +0000 (master branch) (Unix, RelWithDebInfo, Static) Using SSL version: OpenSSL 3.0.2 15 Mar 2022 (library: OpenSSL 3.0.2 15 Mar 2022) Using Boost version: 1.74.0 Using MySQL version: 80039 Using CMake version: 3.22.1 Compiled on: Linux 5.15.0-117-generic Automatic database updates are enabled for the following databases: Auth, Characters, World Worldserver listening connections on port 8085 Realmlist (Realm Id: 1) configured in port 8085 VMAPs status: Enabled. LineOfSight: 1, getHeight: 1, indoorCheck: 1 MMAPs status: Enabled maps directory located in /home/firelands/server/bin/data/maps. Total size: 409779433 bytes vmaps directory located in /home/firelands/server/bin/data/vmaps. Total size: 881241574 bytes mmaps directory located in /home/firelands/server/bin/data/mmaps. Total size: 2942694492 bytes Using enUS DBC Locale as default. All available DBC locales: enUS none Using World DB: FDB 434.22012

Operating system

Ubuntu 22.04, 4 Core and 8GB RAM

Custom changes or Modules

SoloCraft from M'Dic

Steveboi90 commented 2 months ago

Warrior:

Rend causes a crash when logging into another character in the same zone. Example: If I use Rend on the training dummies with an Orc Warrior and then log out to log into another Orc, the server crashes immediately. However, if I log into an Alliance character who is in a completely different area, the server continues to run for a while.

Deep Wounds causes a crash when logging into another character, but only if the character is in the same zone.

Additionally, I found the following: I tested DoTs and debuffs on the dummies with an Alliance character in Stormwind. Since I also created a Gnome Priest for testing, I used .tele Stormwind to travel to Stormwind. When I got close to the dummies, the server also crashed. I was able to reproduce this issue. I was on the last bridge leading to the district where the dummies are located.

Steveboi90 commented 2 months ago

Paladin:

The Censure DoT causes the server to crash when you log out and then log back in, either in the same zone or when approaching that zone. Examples:

When a Paladin applies Censure on training dummies and logs out while Censure is active, logging back in with a character in the same zone results in an immediate server crash. The same issue occurs if you log in with a different character near the zone where Censure was active.

Additional Tests:

Holy Fire should not trigger Censure.