| 2010-06-23 14:55:57 |
Drax |
description |
Hiding and showing a layer containing only an embedded image causes the memory usage to spike uncontrollably. When the image is linked instead of embedded, this issue does not occur.
Steps to reproduce:
1. Create a new document.
2. Embed an image in the document.
3. Open Task Manager.
4. On the 'Performance' tab, take note of memory usage.
5. In Inkscape, repeatedly show and hide the layer containing the embedded image.
The memory usage climbs each time the image is shown. This can climb at rates up to 150MB each time it is shown, when working with large images. Eventually, the RAM will be completely consumed by Inkscape and can cause system instability. Closing Inkscape releases the memory. |
Hiding and showing a layer containing only an embedded image causes the memory usage to spike uncontrollably. When the image is linked instead of embedded, this issue does not occur.
Steps to reproduce:
1. Create a new document.
2. Embed an image in the document.
3. Open Task Manager.
4. On the 'Performance' tab, take note of memory usage.
5. In Inkscape, repeatedly show and hide the layer containing the embedded image.
The memory usage climbs each time the image is shown. This can climb at rates up to 150MB each time it is shown, when working with large images. Eventually, the RAM will be completely consumed by Inkscape and can cause system instability. Closing Inkscape releases the memory.
This was tested on Windows Vista Home Basic, with 2 GB RAM. This was tested on 0.47-3 and 0.48pre1-1.
When watching the memory info in Inkscape, the 'libgc - In Use' is what increases. |
|
