[Digikam-devel] [digikam] [Bug 330231] New: Memory leak when geo-location map is displayed

[Samuel Gilbert]

https://bugs.kde.org/show_bug.cgi?id=330231

            Bug ID: 330231
           Summary: Memory leak when geo-location map is displayed
    Classification: Unclassified
           Product: digikam
           Version: 3.5.0
          Platform: Archlinux Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Geolocation
          Assignee: digikam-devel at kde.org
          Reporter: samuel.gilbert at usherbrooke.ca

There is a memory leak when viewing a geo-location map.

I used ksysguard to monitor memory usage.

- When digikam is loaded, it uses about 200 MB
- If I scroll an album with 300 pictures page by page digikam's memory usage
stabilize around 430 MB
- Even I go to another big album with another 3000 pictures, the memory
footprint stays around 430 MB
- If I restart digikam and select the same album, but I display a map (by using
the earth icon on the right edge of the window), digikam will use over 500 MB
of RAM after scrolling through about 200 pictures.
- The same thing happens by selecting Image -> geo-location in the menu and
scrolling around.  Even if the geo-location window is closed, the memory
footprint doesn't go down significantly.
- After geo-location session of about 1.5 hour, digikam uses more than 2 GB of
RAM on my laptop

Reproducible: Always

Steps to Reproduce:
1. Fire up digikam
2. In the menu, select Image -> geo-location
3. Scroll to different places, change zoom.  I can get it to eat up 300 MB per
minute just by scrolling the map at the maximum zoom.
4. Close the geo-location window and notice that memory usage hasn't
significantly diminished
Actual Results:  
Lots of memory is used and never gets freed up unless digikam is closed

Expected Results:  
Memory usage should stabilize after awhile and it should go down to what it was
before when the geo-location window is closed

-- 
You are receiving this mail because:
You are the assignee for the bug.