STEPS TO REPRODUCE 1. Generate large amounts of files in a folder, as little as 60 or more than 1000 2. In left panel, `Files`, navigating to the folder, scrolling down and Elisa crashes. 3. If Elisa didn't crash, increase the amount of files you generated until it crashes. OBSERVED RESULT Elisa crashed EXPECTED RESULT Elisa doesn't crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArchLinux (available in About System) KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.7.4 Qt Version: 5.15.1 ADDITIONAL INFORMATION I tried to solve this myself, but the best I can get is to know it crashes on app.exec(). Which didn't help much. This may not even be a Elisa issue, could be related to baloo. I compiled debug version from git master, the bug doesn't disappear. Output: 23:01:16: Starting /home/hany/Dev/C++/Qt/KDE/Desktop/build-elisa-Desktop-Debug/bin/elisa ... QSocketNotifier: Can only be used with threads started with QThread Cyclic dependency detected between "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" qrc:/qml/ElisaMainWindow.qml:17:1: QML ElisaMainWindow: Accessible must be attached to an Item file:///usr/lib/qt/qml/org/kde/kirigami.2/templates/OverlayDrawer.qml:291:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... } file:///usr/lib/qt/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:153:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... } file:///usr/lib/qt/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:83:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... } org.kde.elisa.indexers.manager: Local file system indexer is inactive org.kde.elisa.indexers.manager: Baloo indexer is unavailable org.kde.elisa.indexers.manager: Baloo indexer is inactive file:///usr/lib/qt/qml/org/kde/kirigami.2/ContextDrawer.qml:79: TypeError: Cannot call method 'hasOwnProperty' of null qrc:/qml/ContextView.qml:93:13: QML Image: Failed to get image from provider: image://icon/media-optical-audio org.kde.elisa.indexers.manager: Baloo indexer is available org.kde.elisa.indexers.manager: Baloo indexer is active org.kde.elisa.indexers.manager: trigger init of baloo file indexer qrc:/qml/NavigationActionBar.qml:134:21: QML Image: Failed to get image from provider: image://icon/arrow-down qrc:/qml/NavigationActionBar.qml:134:21: QML Image: Failed to get image from provider: image://icon/arrow-down qrc:/qml/NavigationActionBar.qml:134:21: QML Image: Failed to get image from provider: image://icon/arrow-down qrc:/qml/NavigationActionBar.qml:134:21: QML Image: Failed to get image from provider: image://icon/arrow-down qrc:/qml/NavigationActionBar.qml:134:21: QML Image: Failed to get image from provider: image://icon/arrow-down qrc:/qml/NavigationActionBar.qml:134:21: QML Image: Failed to get image from provider: image://icon/arrow-down qrc:/qml/ImageWithFallback.qml:36:5: QML Image: Failed to get image from provider: image://icon/folder KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = elisa path = /home/hany/Dev/C++/Qt/KDE/Desktop/build-elisa-Desktop-Debug/bin pid = 32557 KCrash: Arguments: /home/hany/Dev/C++/Qt/KDE/Desktop/build-elisa-Desktop-Debug/bin/elisa KCrash: Attempting to start /usr/lib/drkonqi Unable to start Dr. Konqi Re-raising signal for core dump handling. ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=32557 comm="elisa" exe="/home/hany/Dev/C++/Qt/KDE/Desktop/build-elisa-Desktop-Debug/bin/elisa" sig=11 res=1 23:02:32: The program has unexpectedly finished. 23:02:32: The process was ended forcefully. 23:02:32: /home/hany/Dev/C++/Qt/KDE/Desktop/build-elisa-Desktop-Debug/bin/elisa crashed.
Thanks for your report. Could you please send a backtrace of the crash? As is, we cannot analyze your report.
Created attachment 132705 [details] backtrace1 Not sure if this is what you wanted. But I guess it's backtrace.
Thanks for the backtrace but it is missing symbols info. Please have a look at https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
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!