Bug: quitting Akregator leaves remaining memory footprint

After quitting Akregator, this app is not fully removing its footprint 
form the memory but at least leaving a kio_http_cache_cleaner process 
behind. That kio_http_cache_cleaner process isn't categorized in the 
process tree for usr/bin/akregator but appears as an independent 
process, though. However, in the 'System Monitor' app on page 
'Applications' it remains listed as some app with title "Akregator". The 
memory usage of the residual app entry is there stated to be 2.8 MB. 
Searching on the "Processes" page of the System Monitor app, I find 
exactly one entry which by its memory footprint is most likely to be the 
relict, and this is why I mentioned it already above to be related to 
this issue:
.../kf5/kio_http_cache_cleaner


Some observations:
The running app shows on the Application page a memory footprint of 
257.0 MB. The "Process" page shows that the usr/bin/akregator process is 
about 113.1 MB, and then there are in the process tree listed 3 
'QtQWebEngine" processes and a sd_espeak-ng process summing up to 
another 28.8 MB. Obviously, the memory footprint of the App and the 
memory footprint of its process tree shows about 115 MB difference.
Closing the Akregator app by normal user action FILE - QUIT, all this 
process tree disappears.
However, as said, on the System Monitor's Application page an 2.8 MB 
entry still titled "Akregator" remains.

Starting now a new instance of Akregator I find a second Application 
entry with its new 250 MB footprint and process tree having appeared. 
The "former" 2.8 MB entry remains as a first entry. Closing the new 
instance, still one 2.8 MB app entry remains, probably the former one. 
However, I cannot know if it indeed is a "former" relict, or became 
overwritten with some "new" relict.

I observe that the remaining footprint of 2.8 MB fluctuates over the 
course of minutes from 2.8 MB to 2.7 MB, to 2.6 MB but also back to 2.7 
MB and 2.8 MB. I therefore conclude there is indeed some process running 
adn that it is not simply System Monitor to forgot to remove an entry.

As said, searching through the processes and their memory footprints, I 
find exactly one entry which by its memory footprint is most likely to 
be the relict:
.../kf5/kio_http_cache_cleaner

I tested this for the app being configured to show and to not show a 
"system tray icon".

I wouldn't have the knowledge to figure out if the Akregator app,the 
kio_http_cache_cleaner, or even the System Monitor app is buggy, how or 
where the 115 MB gap between process tree footprint and reported 
Application footprint is caused, and am also not sure where in the bug 
tracker to place this bug report.

So, I decided to leave this message here in the hope that some skilled 
KDE developer find it and pick it up for improving KDE. By the way, 
Thanks for KDE!


Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.12.9+bpo-amd64 (64-bit)
Graphics Platform: X11