[x] I have checked the commit log to see if the issue has been resolved since my server was last updated
[x] This issue occurs on release branch (if other branch, please specify)
Additional Information (Steps to reproduce/Expected behavior) :
No info on how it happens as its the first time seeing this, but will keep an eye if it happens again.
Thread 1 "topaz_game" received signal SIGSEGV, Segmentation fault.
__GI___libc_free (mem=0x7e6df610) at malloc.c:3113
3113 malloc.c: No such file or directory.
3108 in malloc.c
#0 __GI___libc_free (mem=0x7e6df610) at malloc.c:3113
#1 0x000055555568a399 in CItemEquipment::~CItemEquipment() (this=0x555587c3d480)
at /topaz-next/src/map/items/item_equipment.cpp:46
#2 0x00005555555ef0d4 in CItemContainer::__base_dtor (this=<optimized out>)
at /topaz-next/src/map/item_container.cpp:47
#3 std::default_delete<CItemContainer>::operator() () at /usr/include/c++/7/bits/unique_ptr.h:78
#4 std::unique_ptr<CItemContainer, std::default_delete<CItemContainer> >::~unique_ptr ()
at /usr/include/c++/7/bits/unique_ptr.h:263
#5 CCharEntity::__base_dtor (this=0x55558816d260)
at /topaz-next/src/map/entities/charentity.cpp:220
#6 0x00005555555ef219 in CCharEntity::__deleting_dtor (this=0x55558816d260)
at /topaz-next/src/map/entities/charentity.cpp:235
#7 0x0000555555574e7f in map_close_session (tick=..., map_session_data=0x5555881e4300)
at /topaz-next/src/map/map.cpp:827
#8 do_sockets (next=..., rfd=0x7fffffffdaf0) at /topaz-next/src/map/map.cpp:431
#9 main (argc=<optimized out>, argv=<optimized out>)
at /topaz-next/src/common/kernel.cpp:276
0x7ffff7a79a67 <__GI___libc_free+55>: je 0x7ffff7a79b90 <__GI___libc_free+352>
=> 0x7ffff7a79a6d <__GI___libc_free+61>: mov -0x8(%rdi),%rsi
0x7ffff7a79a71 <__GI___libc_free+65>: lea -0x10(%rdi),%r13
0x7ffff7a79a75 <__GI___libc_free+69>: test $0x2,%sil
0x7ffff7a79a79 <__GI___libc_free+73>: jne 0x7ffff7a79bb8 <__GI___libc_free+392>
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
releasebranch (if other branch, please specify)Additional Information (Steps to reproduce/Expected behavior) :
No info on how it happens as its the first time seeing this, but will keep an eye if it happens again.