Memory leak while browsing photos in 0.6.1
Submitted by an unknown user
Link to original bug (#716671)
Description
---- Reported by shotwell-maint@gnome.bugs 2010-07-21 00:26:00 -0700 ----
Original Redmine bug id: 2309
Original URL: http://redmine.yorba.org/issues/2309
Searchable id: yorba-bug-2309
Original author: Ken VanDine
Original description:
Binary package hint: shotwell 0.6.1
While watching memory use (both virtual and RSS), I noticed memory usage grows while browsing and never freed.
Steps to reproduce (while watching memory use):
-
Open shotwell
-
Select an event and double click a photo
-
Use arrows keys to navigate photos
In my case, launching shotwell initally used 361M virt and 36M RSS, after about 10 minutes of use it was up to 490M virt and 128M RSS. Watching the growth, both grew slowly as switching photos, but not on each photo. One thing to note, there is an error displayed in the console, not sure if it is related:
Warning: Directory OlympusCs, entry 0×0101: Strip 0 is outside of the data area; ignored.
Warning: Invalid JPEG preview image.
That was repeated many times, but not sure if it happened exactly when memory consumption grew.
Downstream bug report: https://bugs.edge.launchpad.net/ubuntu/source/shotwell/bug/608074
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:40:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 3 years ago
I attempted to reproduce this unsucessfully. I started Shotwell with a 500-photo library, opened a photo in full-window view, then held down the right arrow key for several minutes to iterate through photos. Even after a few minutes the 'Virtual Memory' and 'Memory' columns in System Monitor had not increased for the Shotwell process.
I wonder if the memory leak might be related to the console error that kenvandine mentioned.
Comment 2
Updated by Jim Nelson over 3 years ago
It's possible. Ken, can you find the photo in your library and attach it to this ticket? The console error should print as soon as you're viewing the photo.
The error message is from Exiv2, by the way; see #1872 (closed).
Comment 3
Updated by Ken VanDine over 3 years ago
This error is printing when viewing any of my photos, all taken with the same camera.
Warning: Directory OlympusCs, entry 0×0101: Strip 0 is outside of the data area; ignored.
Warning: Invalid JPEG preview image.
Comment 4
Updated by Adam Dingle over 3 years ago
- Priority set to High
Comment 5
Updated by Adam Dingle over 3 years ago
-
Priority deleted (
<strike>
_High_</strike>
)
Comment 6
Updated by Jim Nelson over 3 years ago
I'm seeing the Exiv2 error message, but I'm still unable to reproduce this problem. We do have a report of a possible memory leak after importing a large number of photos (#2349 (closed)), but that appears to be different than what you're seeing.
Would you say a large number of your photos come from the same camera? Or is your library filled with photos from a variety of sources?
Comment 7
Updated by Ken VanDine over 3 years ago
- Status changed from Open to 5
- Resolution set to fixed
- % Done set to 100
I can no longer reproduce the bug. I am still seeing the error on the console that seems to come from exiv2, so perhaps that wasn't related. It is possible it was a bug somewhere in the stack that has been fixed, like vala. I am running Maverick and have gotten several updates to vala since reporting the bug. Currently on 0.9.4-1ubuntu1.
Comment 8
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:46 UTC ---
This bug was previously known as bug 2309 at http://redmine.yorba.org/show_bug.cgi?id=2309 Imported an attachment (id=261767)
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Resolution: RESOLVED FIXED