Application: elisa (20.12.3) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.0-31-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.4 Distribution: Ubuntu 21.04 -- Information about the crash: - What I was doing when the application crashed: I selected 'Genres' from the side menu, chose a genre (issue persists regardless of which genre is chosen), and then attempted to scroll through the subsequent artist list, at which point the app crashed. The crash can be reproduced every time. -- Backtrace: Application: Elisa (elisa), signal: Segmentation fault [KCrash Handler] #4 0x00007fc113caf6c0 in QHash<QQmlPropertyData*, RequiredPropertyInfo>::isEmpty (this=<error reading variable: Cannot access memory at address 0x58>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:285 #5 QHash<QQmlPropertyData*, RequiredPropertyInfo>::empty (this=<error reading variable: Cannot access memory at address 0x58>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:544 #6 QQmlIncubatorPrivate::incubate (this=0x563b32ebb660, i=...) at qml/qqmlincubator.cpp:333 #7 0x00007fc113cafd02 in QQmlIncubationController::incubateFor (this=this@entry=0x563b3215e510, msecs=<optimized out>) at qml/qqmlincubator.cpp:409 #8 0x00007fc11245cc74 in QQuickWindowIncubationController::incubate (this=0x563b3215e500) at items/qquickwindow.cpp:171 #9 QQuickWindowIncubationController::timerEvent (this=0x563b3215e500) at items/qquickwindow.cpp:154 #10 0x00007fc1137bb02f in QObject::event (this=0x563b3215e500, e=0x7ffe1f12bf40) at kernel/qobject.cpp:1336 #11 0x00007fc1147d5783 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x563b3215e500, e=0x7ffe1f12bf40) at kernel/qapplication.cpp:3632 #12 0x00007fc11378d7ba in QCoreApplication::notifyInternal2 (receiver=0x563b3215e500, event=0x7ffe1f12bf40) at kernel/qcoreapplication.cpp:1063 #13 0x00007fc1137e6533 in QTimerInfoList::activateTimers (this=0x563b31db1170) at kernel/qtimerinfo_unix.cpp:643 #14 0x00007fc1137e6e74 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:183 #15 idleTimerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:230 #16 0x00007fc11139a8eb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x00007fc1113edd28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x00007fc111398023 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x00007fc1137e7204 in QEventDispatcherGlib::processEvents (this=0x563b31db10b0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #20 0x00007fc11378c11b in QEventLoop::exec (this=this@entry=0x7ffe1f12c180, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #21 0x00007fc113794604 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #22 0x0000563b2fc47824 in main (argc=<optimized out>, argv=<optimized out>) at ./src/main.cpp:165 [Inferior 1 (process 10381) detached] The reporter indicates this bug may be a duplicate of or related to bug 428585. Possible duplicates by query: bug 439068, bug 438742, bug 438025, bug 437955, bug 436978. Reported using DrKonqi
Does this issue happen only right after you launch the app, and go away if you scroll through that grid again after the "scanning music" notification in the top-right corner of the window has gone away? If so, this is Bug 428585.
(In reply to Nate Graham from comment #1) > Does this issue happen only right after you launch the app, and go away if > you scroll through that grid again after the "scanning music" notification > in the top-right corner of the window has gone away? If so, this is Bug > 428585. Nate, Originally, the issue occurred regardless of whether the "scanning music" notification was present on the window. However, after double checking just now, I can no longer reproduce the issue at all, with or without the notification.
Weird. Well, if you can't reproduce the issue and I can't either, Its unlikely we'll be able to get it fixed, because the crash backtrace doesn't show any obvious culprits. :( I do suspect that this is the same as Bug 428585 though.
(In reply to Nate Graham from comment #3) > Weird. > > Well, if you can't reproduce the issue and I can't either, Its unlikely > we'll be able to get it fixed, because the crash backtrace doesn't show any > obvious culprits. :( > > I do suspect that this is the same as Bug 428585 though. Dang. Well, I'm sorry to have sent you on a fruitless search.
No worries, it's a normal thing. :)