| Summary: | Gwenview crashes, out of memory | ||
|---|---|---|---|
| Product: | [I don't know] kde | Reporter: | Seb <bastisemail> |
| Component: | general | Assignee: | Unassigned bugs <unassigned-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Reported already (bug #162505). |
Version: (using KDE 4.0.4) Installed from: SuSE RPMs OS: Linux Very often Gwenview crashes. Application case: Go through a list of photos (about 2.5 MB jpegs). Edit (rotate) some of them, say 15. Gwenview now reqires about 1.5 GB RAM! After rotating 30 images without saving during this process, Gwenview crashes (computer then is totally in swap, no mouse movement even possible). It does not seem to be a memory leak, but a design issue: Does Gwenview store jpeg images as jpegs or does it expand the images to their rel size (this seems to, since the memory usage grows by about 10MB when loading a single image)? Does Gwenview store the operation ("rotate") or does it save the images during the command flow (in order to provide undo/redo functionality)??? (memory grows while rotating images)