Summary: | Krusader crashed after starting Disk Usage | ||
---|---|---|---|
Product: | [Applications] krusader | Reporter: | Jim <jimmthegeek> |
Component: | general | Assignee: | Krusader Bugs Distribution List <krusader-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | jhdore, krusader-bugs-null, mark, mkyral |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi attachment-26115-0.html |
Description
Jim
2019-07-11 18:00:47 UTC
Created attachment 128023 [details]
New crash information added by DrKonqi
krusader (2.7.2 "Peace of Mind") using Qt 5.12.8
- What I was doing when the application crashed:
Calculating usage of my home directory, the calcualtion started, and crashed about 1/3rd the way through.
-- Backtrace (Reduced):
#6 0x00007f6d7904b3f6 in QUrl::scheme() const () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007f6d791c0a80 in QMimeDatabase::mimeTypeForUrl(QUrl const&) const () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x000055e589f4bf4e in ()
#9 0x000055e589eb9690 in ()
#10 0x000055e589ece3d5 in ()
Created attachment 128248 [details]
New crash information added by DrKonqi
krusader (2.6.1-beta "Stiff Challenges") using Qt 5.14.1
- What I was doing when the application crashed:
I let Disk Usage calculate sizes in my home folder. After some time it crashes.
-- Backtrace (Reduced):
#6 std::__atomic_base<int>::load (__m=std::memory_order_relaxed, this=0xb1) at /usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include/g++-v9/bits/atomic_base.h:413
#7 QAtomicOps<int>::loadRelaxed<int> (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#8 QBasicAtomicInteger<int>::loadRelaxed (this=0xb1) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107
[...]
#10 QString::QString (other=..., this=0x7ffcbb15b408) at ../../include/QtCore/../../src/corelib/text/qstring.h:1051
#11 QUrl::scheme (this=this@entry=0x55d97e4ac068) at io/qurl.cpp:2004
This is still happening in later versions of Qt & Framework, crash report below. As the other reports, I was running disk usage on my home directory. The crash occurred quite a while after starting. I checked in on it a couple of times. The last figures I saw were about 99,000 files occupying just over 20Gb. I ran this twice with it crashing both times. As usual the crash reporting assistant refused to report it directly claiming "not enough information", as it always does. Application: krusader (2.7.2 "Peace of Mind") Qt Version: 5.14.2 Frameworks Version: 5.73.0 Operating System: Linux 5.8.18-200.fc32.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 32 (Thirty Two)" -- Backtrace: Application: Krusader (krusader), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7effeb51bdc0 (LWP 3666))] Thread 6 (Thread 0x7effd4dda700 (LWP 3673)): #0 0x00007effeeabdaaf in poll () from /lib64/libc.so.6 #1 0x00007effeda6eaae in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #2 0x00007effeda6ebe3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x00007effef16db8b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #4 0x00007effef12091b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #5 0x00007effeef8c427 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x00007efff018051b in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x00007effeef8d690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x00007effee553432 in start_thread () from /lib64/libpthread.so.0 #9 0x00007effeeac8913 in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7effd69d7700 (LWP 3672)): #0 0x00007effee559e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007effd7736fbb in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x00007effd7736a8b in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x00007effee553432 in start_thread () from /lib64/libpthread.so.0 #4 0x00007effeeac8913 in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7effd71d8700 (LWP 3671)): #0 0x00007effee559e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007effd7736fbb in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x00007effd7736a8b in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x00007effee553432 in start_thread () from /lib64/libpthread.so.0 #4 0x00007effeeac8913 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7effcffff700 (LWP 3670)): #0 0x00007effee559e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007effd7736fbb in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x00007effd7736a8b in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x00007effee553432 in start_thread () from /lib64/libpthread.so.0 #4 0x00007effeeac8913 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7effdca07700 (LWP 3669)): #0 0x00007effee559e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007effd7736fbb in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x00007effd7736a8b in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x00007effee553432 in start_thread () from /lib64/libpthread.so.0 #4 0x00007effeeac8913 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7effeb51bdc0 (LWP 3666)): [KCrash Handler] #4 0x000055a8ebf8a397 in QString::~QString() () #5 0x000055a8ec0903f7 in FileItem::getMime() () #6 0x000055a8ec01c4cf in DiskUsage::slotLoadDirectory() () #7 0x00007effef150fb0 in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #8 0x00007effef1544ce in QTimer::timeout(QTimer::QPrivateSignal) () from /lib64/libQt5Core.so.5 #9 0x00007effef149abf in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #10 0x00007effefadc063 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #11 0x00007effef121fc0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #12 0x00007effef16ce83 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #13 0x00007effef16d7c4 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #14 0x00007effeda6e78f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #15 0x00007effeda6eb18 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #16 0x00007effeda6ebe3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #17 0x00007effef16db73 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #18 0x00007effef12091b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #19 0x00007effef1285a6 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #20 0x000055a8ebf85b55 in main () [Inferior 1 (process 3666) detached] Thank you for reporting this crash 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 crash with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Created attachment 153334 [details] attachment-26115-0.html I don't have access to the original system that had the issue any more. I have installed Krusader on two other systems and it seems to be working properly. On Sat, Oct 29, 2022 at 7:40 PM Justin Zobel <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=409725 > > Justin Zobel <justin.zobel@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > > --- Comment #4 from Justin Zobel <justin.zobel@gmail.com> --- > Thank you for reporting this crash 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 crash 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 reported the bug. I, too, don't have the machine that originally had the problem. This Krusader is the same version ("Peace of Mind" but number, 2.7.2) I had the problem on initially but, of course, Fedora has had four major releases since then and the core has had many updates. I left the Disk Usage window running for over an hour without crashing, so it seems that the problem doesn't exist any more, at least here. 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! 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! |