By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2035 - Gwenview uses all memory browsing a dir of .tiff files
Summary: Gwenview uses all memory browsing a dir of .tiff files
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: tdegraphics (show other bugs)
Version: 3.5.13.x [Trinity]
Hardware: amd64 Debian Wheezy
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 2968
  Show dependency tree / graph
 
Reported: 2014-04-24 01:46 CDT by Greg Madden
Modified: 2018-08-30 02:52 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
scanned image (tiff) of a construction drawing (1.28 MB, image/tiff)
2014-04-24 01:46 CDT, Greg Madden 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Greg Madden 2014-04-24 01:46:33 CDT 
Created attachment 2046 [details]
scanned image (tiff) of a construction drawing

Using Gwenview to browse/view a folder of .tiff images, ranging from 350K to 1.2M. I can view about 10 images before it uses all remaining memory ~ 6gb. Using top I can see the memory use jump after viewing each file. 

I use the menu bar browse>view image feature, one image at a time. Viewing jpeg images the same size and manner, memory use stays about the same after the initial image is viewed.
Comment 1 Michele Calgaro 2014-04-27 09:39:55 CDT 
I can reproduce the problem. Using several copies of the image attached by Greg, memory starts to fill up and after a while even the swap. Only after closing gwenview every goes back to normal.

It may be a problem with gwenview not releasing allocated memory or with tiff handling code. Will definitely need more investigation when we look into this (i.e. not before v14.0.0 is out).