Bug 250768

Summary:	Dolphin leaks memory when viewing large numbers of thumbnails
Product:	[Applications] dolphin	Reporter:	Xiong Chiamiov <xiong.chiamiov>
Component:	general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	aspotashev, finex, mail, non7top
Priority:	NOR
Version:	16.12.2
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	xrestop on a fresh opening of dolphin xrestop after previews are enabled and memory use stabilizes xrestop (batch mode) after previews are enabled and memory use stabilizes xrestop after dolphin has been closed free after dolphin has been closed

Description Xiong Chiamiov 2010-09-10 11:55:14 UTC

Version:           unspecified (using Devel) 
OS:                Linux

I open a folder with 5,630 images in it in Dolphin, with thumbnails on.  X spikes up to 1200M virt, 900 real.  Close dolphin, X's memory usage is unaffected.  Reopen folder, and now those figures are roughly doubled.

I originally reported this over at the Arch forums: https://bbs.archlinux.org/viewtopic.php?pid=823434

When viewing the same folder in Thunar (with thumbnails), X's memory usage doesn't change.  Thus, I'm inclined to believe it's a problem with either Dolphin or one of its components.

Reproducible: Always

Steps to Reproduce:
Open directory with several thousand images.  Click "Preview" button.



kdebase 4.5.1, x86

Comment 1 FiNeX 2010-09-12 15:13:43 UTC

It could be a regression, I've a directory with about 4500 images (more than 2Gb) and 4.4.5 works fine :-)

Comment 2 Xiong Chiamiov 2010-09-14 04:14:09 UTC

Created attachment 51619 [details]
xrestop on a fresh opening of dolphin

Comment 3 Xiong Chiamiov 2010-09-14 04:14:59 UTC

Created attachment 51620 [details]
xrestop after previews are enabled and memory use stabilizes

Comment 4 Xiong Chiamiov 2010-09-14 04:15:21 UTC

Created attachment 51621 [details]
xrestop (batch mode) after previews are enabled and memory use stabilizes

Comment 5 Xiong Chiamiov 2010-09-14 04:15:44 UTC

Created attachment 51622 [details]
xrestop after dolphin has been closed

Comment 6 Xiong Chiamiov 2010-09-14 04:16:24 UTC

Created attachment 51623 [details]
free after dolphin has been closed

The amount of memory used should be significantly lower than this.

Comment 7 Xiong Chiamiov 2010-09-14 21:21:12 UTC

Since I have an nvidia card, I tried installing oxygen from the 4.5 subversion branch, as described here: http://hugo-kde.blogspot.com/2010/09/performance-issues-one-script-and-call.html - no luck.  Also tried switching themes away from Oxygen completely.

Comment 8 Dawit Alemayehu 2012-02-26 23:51:00 UTC

*** Bug 230179 has been marked as a duplicate of this bug. ***

Comment 9 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:19:50 UTC

Resetting assignee to default as per bug #305719

Comment 10 Frank Reininghaus 2013-04-25 20:35:12 UTC

Is still still an issue in KDE 4.10.2 or later?

Comment 11 Frank Reininghaus 2013-09-25 16:24:43 UTC

Please let us know if this is still a problem in more recent versions. We don't do anything unusual with our previews (load them using a KIO::PreviewJob and let QPixmap's destructor handle the cleanup), so I guess that this is/was not a problem with Dolphin itself, but with something inside kdelibs or Qt.

If the issue is still there, it should also happen when enabling previews in the "File Open" dialog of KDE applications. If you still see such problems, please leave a comment here. Thanks for your help!

Comment 12 Julian Steinmann 2018-03-31 10:29:10 UTC

Closing now, seems like this has been fixed upstream.