Trinitycore: [3.3.5][Crash]Unit::RemoveAurasByType

[Re3os]

1

[joschiwald]

confirmed, Target in https://github.com/TrinityCore/TrinityCore/blob/3.3.5/src/server/game/Entities/Vehicle/Vehicle.cpp#L863 is already deleted

[ghost]

Fair enough that you have provided debug crash logs. Wish you had built it with Git rev. hash, though.

---

edit: 2 things you can do to improve your own core: upgrade Boost and OpenSSL. From your logs:

Using SSL version: OpenSSL 1.0.1f 6 Jan 2014 (library: OpenSSL 1.0.1f 6 Jan 2014)
Using Boost version: 1.54.0

Boost: The current requirement states that you need to use version 1.55 or higher. See also:
https://trinitycore.atlassian.net/wiki/display/tc/Linux+Requirements

OpenSSL is not important for TrinityCore, but it might be important for yourself if you give external users access to your server, because your version is from before the OpenSSL Heartbleed vulnerability bug got fixed in 1.0.1.h. The current available version is 1.0.1.s (supported in MySQL 5.6.30).

[Re3os]

@tkrokli thanks)

[ghost]

http://paste.ubuntu.com/16959231/

Rev: cae19692ab2b627b292cdeed59069d5f6fa3be30

[Keader]

No news about it?

[ghost]

No more news yet, unless you yourself have got a crash log (debug build) to post.

[Evgeni16]

Confimed

crash log - http://pastebin.com/q3UXYqsk
rev - https://github.com/TrinityCore/TrinityCore/commit/69b581deff2cb42b9cb5620c87f0861fcb760bea

[sirikfoll]

Is there any patch/procedure that could help track down this crash?
We tried to get an Npc Entry by adding volatile uint32 entry = Target->GetBase()->GetEntry(); at void VehicleJoinEvent::Abort(uint64) but the values are just weird, like 22761519 and 587414915

[joschiwald]

@sirikfoll read my comment, you can't access Target in VehicleJoinEvent::Abort

[sirikfoll]

@joschiwald Do you recommend any patch/procedure that I can do to help track down this crash?

[joschiwald]

as workaround, replace target ptr by guid in vehicle join event

[xjose93]

If it helps: https://gist.github.com/xjose93/f18e1c47a5708fdbc7fcfb3ca79993de

Not sure about the rev but its like 35 days ago.

[ghost]

More than 9 months without updates for this crash.
@joschiwald : anything against closing this one?

[Aokromes]

near 2 years already with a lot of changes on spell system, if this bug is still valid open a new ticket using updated core