LRC: ASAN detects "new-delete-type-mismatch" on quitting the client
Issue generated from Tuleap's migration script. Originally submitted by: Stepan Salenikovich (ssalenik)
Seems to be systematic since the current master. Not sure if it is unique to the GNOME client or not, so marking it as an LRC issue...
\*\* (gnome-ring:19273): DEBUG: quitting
=================================================================
==19273==ERROR: AddressSanitizer: new-delete-type-mismatch on 0x6020001a4e10 in thread T0:
object passed to delete has wrong type:
size of the allocated type: 16 bytes;
size of the deallocated type: 8 bytes.
\#0 0x7ffff6f034b2 in operator delete(void\*, unsigned long) (/usr/lib/x86\_64-linux-gnu/libasan.so.2+0x9a4b2)
\#1 0x62511d in std::unique\_ptr<GlobalInstances::InstanceManager, std::default\_delete<GlobalInstances::InstanceManager> >::\~unique\_ptr() (/home/ssalenikovich/projects/ring-client-gnome/build/gnome-ring+0x62511d)
\#2 0x7ffff2b0ed31 (/lib/x86\_64-linux-gnu/libc.so.6+0x39d31)
\#3 0x7ffff2b0ed84 in exit (/lib/x86\_64-linux-gnu/libc.so.6+0x39d84)
\#4 0x7ffff2af5a46 in \_\_libc\_start\_main (/lib/x86\_64-linux-gnu/libc.so.6+0x20a46)
\#5 0x4b3ff8 in \_start (/home/ssalenikovich/projects/ring-client-gnome/build/gnome-ring+0x4b3ff8)
0x6020001a4e10 is located 0 bytes inside of 16-byte region [0x6020001a4e10,0x6020001a4e20)
allocated by thread T0 here:
\#0 0x7ffff6f028b2 in operator new(unsigned long) (/usr/lib/x86\_64-linux-gnu/libasan.so.2+0x998b2)
\#1 0x4b5e1a in ring\_client\_startup /home/ssalenikovich/projects/ring-client-gnome/src/ring\_client.cpp:306
\#2 0x7ffff555e243 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10243)
SUMMARY: AddressSanitizer: new-delete-type-mismatch ??:0 operator delete(void\*, unsigned long)
==19273==HINT: if you don't care about these warnings you may set ASAN\_OPTIONS=new\_delete\_type\_mismatch=0
==19273==ABORTING
[Thread 0x7fffd5e38700 (LWP 19284) exited]
[Thread 0x7fffd6a94700 (LWP 19283) exited]
[Thread 0x7fffe0922700 (LWP 19276) exited]
[Thread 0x7fffe1123700 (LWP 19275) exited]
[Thread 0x7fffe1bf2700 (LWP 19274) exited]
[Thread 0x7ffff7e71ac0 (LWP 19273) exited]
[Inferior 1 (process 19273) exited with code 01]