Bug 227412 - kio_thubnail is spawned multible times and eats up all ram
Summary: kio_thubnail is spawned multible times and eats up all ram
Status: RESOLVED FIXED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-17 18:57 UTC by Jim Jones
Modified: 2010-08-06 11:57 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Jones 2010-02-17 18:57:09 UTC
Version:            (using KDE 4.4.0)
OS:                Linux

kio_thubnail is spawned multible times and eats up all ram
right befor this processes occuppied about 600MB RAM.
killing the processes frees the ram but the funny thing is that after all sessions of dolphin are closed - the kio_thubnail processes dont get killed and they keep running.

i use dolphin in column view - maybe its related to this view only but i have "preview" not enabled.
Comment 1 Markus 2010-02-19 06:40:01 UTC
I have a similar problem using KDE 4.4.0 on Slackware 13:

I have disabled preview images on videos in dolphin, but when moving the mouse over a video file to right-click and open it, kio_thumbnail will start mplayer to create a preview icon for the information panel on the right. If i just move the mouse over different video files then multiple instances of kio_thumbnail and mplayer will be launched which will cause the system to be very slow for a while...

Especially for video files it would be nice to not create a preview image for videos in the information panel if not enabled in the options.
Comment 2 Peter Penz 2010-08-06 11:57:52 UTC
Thanks for the report, this issue has been fixed in KDE SC 4.5.0: Some file analyzers ignored the maximum set size for parsing and this has been a problem especially for video files. This issue got fixed now in a central place, so that even analyzers that ignore the maximum will quit after reading 64 KB (at least if this is specified by the application).