https://bugs.kde.org/show_bug.cgi?id=527064

Méven <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
      Latest Commit|                            |https://invent.kde.org/fram
                   |                            |eworks/kio/-/commit/525140d
                   |                            |1cbee11a9f171566bfdb609c106
                   |                            |076b22
             Status|ASSIGNED                    |RESOLVED

--- Comment #5 from Méven <[email protected]> ---
Git commit 525140d1cbee11a9f171566bfdb609c106076b22 by Méven Car.
Committed on 20/10/2026 at 10:03.
Pushed by meven into branch 'master'.

filepreviewjob: remove the local copies of remote files that previews leave

A preview of a remote file that no thumbnailer reads remotely downloads the
file to ~/.cache/<app>/kpreviewjob/<pid>/ first.
Three cases left copies there, and the folder grew without limit.

Killing the preview job did not stop the download, which then wrote the whole
file after the job had removed its copy.
The download is killed with the job now.

A download that failed kept its data in a ".part" file, which a worker keeps so
that a later copy can resume.
Each preview downloads to a new name, so nothing resumed it.
The download is now written without a ".part" file, and the job removes what it
wrote.
A failed download also no longer goes on to make a thumbnail from the
incomplete copy.

A process that crashed left its folder.
The folders of processes that no longer run are removed when a process creates
its own.

M  +153  -0    autotests/filepreviewjobtest.cpp
M  +6    -0    autotests/filepreviewjobtest.h
M  +41   -3    src/gui/filepreviewjob.cpp
M  +1    -0    src/gui/filepreviewjob.h

https://invent.kde.org/frameworks/kio/-/commit/525140d1cbee11a9f171566bfdb609c106076b22

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to