Shotwell bug - Out of memory #5123
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Shotwell |
Fix Released
|
Unknown
|
|||
shotwell (Debian) |
Fix Released
|
Unknown
|
|||
shotwell (Ubuntu) |
Fix Released
|
High
|
Nathan Teodosio | ||
Noble |
Fix Released
|
High
|
Nathan Teodosio |
Bug Description
Impact
------
A memory leak that will cause Shotwell process to increasingly eat memory constantly during a slideshow.
Test case
---------
*Start Shotwell and import a folder with about 10 photos; End Shotwell.
*Save this script and execute it:
--->
#!/bin/sh
shotwell &
pid=$!
statm=/
time=0
inc=1
version=
while test -e "$statm"; do
#https:/
stack=$(cut -f6 -d' ' "$statm")
printf "%s %s\n" "$time" "$stack"
sleep "$inc"
time=
done > "$version.dat"
<---
*Press F5 to start slideshow and keep pressing right arrow to cycle through the photo set about 3 times.
*End Shotwell.
Expected: The memory logged in the *.dat file stops increasing instead of steadily and indefinidetely increasing.
You can use "xmgrace -legend load *.dat" to get a plot of the behavior before and after the fix for easier visualization (see attached shotwell-stat.png).
Regression potential
-------
The changes are on a function that causes the Pixbuf cache to be regenerated and the UI updated, so it should suffice to observe that images are loaded alright in the slide show.
Further information
-------------------
Bug upstream: https:/
Fix upstream: https:/
description: | updated |
Changed in shotwell: | |
status: | Unknown → Fix Released |
description: | updated |
no longer affects: | shotwell (Ubuntu Noble) |
no longer affects: | shotwell (Ubuntu Focal) |
no longer affects: | shotwell (Ubuntu Jammy) |
Changed in shotwell (Ubuntu Noble): | |
importance: | Undecided → High |
assignee: | nobody → Nathan Teodosio (nteodosio) |
Changed in shotwell (Ubuntu Noble): | |
status: | New → Fix Committed |
Changed in shotwell (Debian): | |
status: | Unknown → New |
Changed in shotwell (Debian): | |
status: | New → Fix Released |
Thank you for your bug report and pointing to the patch, that's one we should cherrypick indeed