the issue should be fixed with shotwell 0.15 in Ubuntu 13.10
** Changed in: shotwell (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/
** Changed in: shotwell (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1191585
Title:
Crash when exporting photos to a directory
Remember that JPEG is compressed, and that in memory each pixel requires
24 bits (3 bytes). So, a 3000x3000 image is 25MB in RAM. Seventy of
them is 1.7GB.
In order to speed up the export, Shotwell uses background threads to
parallelize the process, uone thread per CPU. I suspect that's the
iss
So it turns out that this is only reproducible when I'm running "low"
on memory. I rather optimistically run my 8Gb laptop without swap and
while trying to reproduce this again tonight I noticed that at the
point of the crash, the whole machine grinds to a halt and I got some
OOM killer spew in dm
Thanks for the stack trace, that goes a long way toward finding the
problem. One question: if you run Shotwell from the console and
reproduce the problem, do you see a message displayed on the console,
something like "raw pixbuf for could not be loaded"?
** Changed in: shotwell (Ubuntu)
S
This is with the standard package (i.e. no debug symbols), but FWIW,
this is some of the output when reproducing the crash under gdb:
| L 26654 2013-06-16 22:18:42 [CRT] Offset of directory Sony1, entry 0x2001 is
out of bounds: Offset = 0x0034ec76; truncating the entry
|
| L 26654 2013-06-16 22:
