Bug 485736 - Dolphin crashes due to memory leak
Summary: Dolphin crashes due to memory leak
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 24.02.2
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-18 13:49 UTC by Rune
Modified: 2024-07-03 03:47 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rune 2024-04-18 13:49:46 UTC
SUMMARY


STEPS TO REPRODUCE
1. Open a directory containing large text files or its parent directory in dolphin

OBSERVED RESULT
In the parent directory, the directory containing the text files does not show any preview icons. Memory usage skyrockets and when RAM+Swap is full, dolphin crashes after the system hangs for a few seconds.
In my case, the text files (4) are around 600-700MB each and my 32GB of RAM (64 with ZRAM) are full within a few seconds.


EXPECTED RESULT
Icons indicating text files should be shown on the directory containing them. Memory usage should remain normal.

SOFTWARE/OS VERSIONS
Linux: 6.8.7
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION
Tested with 4 >600mb .par files
Comment 1 Rune 2024-04-18 14:16:35 UTC
I thought it was because of the .par files, but that seems to be wrong. In fact, I duplicated the directory, then deleted and restored some files and now everything went back to normal for a short while. I deleted the old directory and renamed the duplicated one to what the old one was, and after restarting dolphin, the problem was there again. Sadly, I have no information on what could be happening here.
Additional info: 
- All directories mentioned here are synced to my Nextcloud
- The memory is used by the process "kio-worker"
Comment 2 Justin Zobel 2024-06-03 06:25:13 UTC
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to attach a backtrace to allow the developers to debug this crash.
Comment 3 Bug Janitor Service 2024-06-18 03:47:00 UTC
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!
Comment 4 Bug Janitor Service 2024-07-03 03:47:36 UTC
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!