[Heaptrack] [Bug 394627] Unable to use with Mudlet
https://bugs.kde.org/show_bug.cgi?id=394627 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #9 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 394627] Unable to use with Mudlet
https://bugs.kde.org/show_bug.cgi?id=394627 --- Comment #8 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 394627] Unable to use with Mudlet
https://bugs.kde.org/show_bug.cgi?id=394627 Justin Zobel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #7 from Justin Zobel --- Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 394627] Unable to use with Mudlet
https://bugs.kde.org/show_bug.cgi?id=394627 --- Comment #6 from Milian Wolff --- ugh, looks like it's an issue when using heaptrack with your custom debug_free/new - can you disable that while using heaptrack for now? I'll have to figure out how to prevent the lock order violation... Probably needs a custom allocator, which I wanted to implement anyways for some time now... -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 394627] Unable to use with Mudlet
https://bugs.kde.org/show_bug.cgi?id=394627 --- Comment #5 from Vadim Peretokin --- (gdb) attach 19809 Attaching to process 19809 [New LWP 19812] [New LWP 19813] [New LWP 19815] [New LWP 19816] [New LWP 19817] [New LWP 19818] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 38 ../sysdeps/unix/sysv/linux/x86_64/syscall.S: No such file or directory. (gdb) thread apply all bt Thread 7 (Thread 0x7ffa18b74700 (LWP 19818)): #0 0x7ffa322b8afd in __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x7ffa322b119d in __GI___pthread_mutex_lock (mutex=0x7ffa35f77440 <(anonymous namespace)::HeapTrack::s_lock>) at ../nptl/pthread_mutex_lock.c:80 #2 0x7ffa35d6d313 in heaptrack_free () at /tmp/.mount_heaptrwI0A5y/opt/lib/heaptrack/libheaptrack_preload.so #3 0x7ffa35d6be06 in free () at /tmp/.mount_heaptrwI0A5y/opt/lib/heaptrack/libheaptrack_preload.so #4 0x004ee3ae in debug_free(void*, char const*, int) (p=0x2d3e540, file=0xa3fe67 "unknown", line=0) at ../3rdparty/edbee-lib/edbee-lib/edbee/util/mem/debug_new.cpp:67 #5 0x004ee47e in operator delete(void*) (p=0x2d3e540) at ../3rdparty/edbee-lib/edbee-lib/edbee/util/mem/debug_new.cpp:90 #6 0x7ffa329cd299 in () at /home/vadi/Programs/Qt/5.9.3/gcc_64/lib/libQt5Core.so.5 #7 0x7ffa329c8989 in QMetaType::destroy(int, void*) () at /home/vadi/Programs/Qt/5.9.3/gcc_64/lib/libQt5Core.so.5 #8 0x7ffa329dbe39 in QMetaCallEvent::~QMetaCallEvent() () at /home/vadi/Programs/Qt/5.9.3/gcc_64/lib/libQt5Core.so.5 #9 0x7ffa329dbeb9 in QMetaCallEvent::~QMetaCallEvent() () at /home/vadi/Programs/Qt/5.9.3/gcc_64/lib/libQt5Core.so.5 #10 0x7ffa329b6687 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /home/vadi/Programs/Qt/5.9.3/gcc_64/lib/libQt5Core.so.5 #11 0x7ffa32a07d13 in () at /home/vadi/Programs/Qt/5.9.3/gcc_64/lib/libQt5Core.so.5 #12 0x7ffa30a97fb7 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7ffa30a981f0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7ffa30a9827c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7ffa32a0736f in QEventDispatcherGlib::processEvents(QFlags) () at /home/vadi/Programs/Qt/5.9.3/gcc_64/lib/libQt5Core.so.5 #16 0x7ffa329b205a in QEventLoop::exec(QFlags) () at /home/vadi/Programs/Qt/5.9.3/gcc_64/lib/libQt5Core.so.5 #17 0x7ffa327ddf9b in QThread::exec() () at /home/vadi/Programs/Qt/5.9.3/gcc_64/lib/libQt5Core.so.5 #18 0x7ffa27d495e5 in () at /home/vadi/Programs/Qt/5.9.3/gcc_64/plugins/platforms/../../lib/libQt5DBus.so.5 #19 0x7ffa327e2c3a in () at /home/vadi/Programs/Qt/5.9.3/gcc_64/lib/libQt5Core.so.5 #20 0x7ffa322ae7fc in start_thread (arg=0x7ffa18b74700) at pthread_create.c:465 #21 0x7ffa316e8b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7ffa1a647700 (LWP 19817)): #0 0x7ffa316dc951 in __GI___poll (fds=0x7ffa14039ad0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ffa30a98169 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffa30a98502 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffa25763b26 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7ffa30abf645 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ffa322ae7fc in start_thread (arg=0x7ffa1a647700) at pthread_create.c:465 ---Type to continue, or q to quit--- #6 0x7ffa316e8b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7ffa1ae48700 (LWP 19816)): #0 0x7ffa316dc951 in __GI___poll (fds=0x7ffa14009720, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ffa30a98169 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffa30a9827c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffa30a982c1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ffa30abf645 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ffa322ae7fc in start_thread (arg=0x7ffa1ae48700) at pthread_create.c:465 #6 0x7ffa316e8b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7ffa1b649700 (LWP 19815)): #0 0x7ffa316dc951 in __GI___poll (fds=0x21baba0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ffa30a98169 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffa30a9827c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffa1b65146d in () at /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so #4 0x7ffa30abf645 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ffa322ae7fc in start_thread (arg=0x7ffa1b649700) at pthread_create.c:465 #6 0x7ffa316e8b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/cl
[Heaptrack] [Bug 394627] Unable to use with Mudlet
https://bugs.kde.org/show_bug.cgi?id=394627 --- Comment #4 from Milian Wolff --- Yes, attach to mudlet and then get the output for the following GDB command: thread apply all bt Please paste that here then -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 394627] Unable to use with Mudlet
https://bugs.kde.org/show_bug.cgi?id=394627 --- Comment #3 from Vadim Peretokin --- Mudlets backtrace is the following: 1 __lll_lock_wait lowlevellock.S 135 0x7fdd7848d10d 2 __GI___pthread_mutex_lock pthread_mutex_lock.c 78 0x7fdd78486023 3 heaptrack_free 0x7fdd7bb02313 4 free 0x7fdd7bb00e06 5 debug_free(void *, const char *, int) 0x4e21b5 6 operator delete(void *) 0x4e225f 7 QObject::~QObject() 0x7fdd78be7858 8 ?? 0x7fdd58267074 9 QObjectPrivate::deleteChildren() 0x7fdd78bde19b 10 QObject::~QObject() 0x7fdd78be79cb 11 ?? 0x7fdd58277e79 12 ?? 0x7fdd5825714b 13 QNetworkConfigurationManagerPrivate::updateConfigurations() 0x7fdd7933143a 14 QNetworkConfigurationManagerPrivate::initialize() 0x7fdd79331dae 15 qNetworkConfigurationManagerPrivate() 0x7fdd7932bfdd 16 QNetworkConfigurationManager::QNetworkConfigurationManager(QObject *) 0x7fdd7932c077 17 QNetworkAccessManager::QNetworkAccessManager(QObject *) 0x7fdd792ba096 18 cTelnet::cTelnet(Host *) 0x582f6b 19 Host::Host(int, QString const&, QString const&, QString const&, int) 0x69c520 20 HostManager::addHost(QString, QString, QString, QString) 0x6ad33e ... It looks like a deadlock. -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 394627] Unable to use with Mudlet
https://bugs.kde.org/show_bug.cgi?id=394627 --- Comment #2 from Vadim Peretokin --- Just running Mudlet is enough. Heaptracks backtrace is not that interesting: 1 wait4 syscall-template.S 78 0x7fbfefa7d76a 2 ?? 0x560fe3ef58a0 3 ?? 0x560fe3ef709d 4 ?? 0x560fe3ef16d8 5 ?? 0x560fe3ef049e 6 ?? 0x560fe3ef049e 7 ?? 0x560fe3ef049e 8 ?? 0x560fe3ef766e 9 ?? 0x560fe3eee9de 10 __libc_start_main libc-start.c 310 0x7fbfef9bab97 11 ?? 0x560fe3eeea4a -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 394627] Unable to use with Mudlet
https://bugs.kde.org/show_bug.cgi?id=394627 --- Comment #1 from Milian Wolff --- Can you try to debug this and see what happens? I.e. attach a debugger when it hangs and get me a full backtrace for all threads? Otherwise, can you add information for me to reproduce this issue? Do I just run mudlet? Do I need some parameters or input files? -- You are receiving this mail because: You are watching all bug changes.
