<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Lots of memory used for inserting an image (fine at save & reload) SKIA Raster"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134342#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Lots of memory used for inserting an image (fine at save & reload) SKIA Raster"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134342">bug 134342</a>
from <span class="vcard"><a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> <span class="fn">Telesto</span></a>
</span></b>
<pre>(In reply to Luboš Luňák from <a href="show_bug.cgi?id=134342#c4">comment #4</a>)
<span class="quote">> Bitmap data cannot be shared between LO (using 24bpp) and Skia (using
> 32bpp). Maybe one day when LO code becomes flexible about what the best
> format for a bitmap is.</span >
As this bug description more a combined'of multiple observations, lets split it
up a bit (for my understanding)
1) The difference on file open between Skia 1,3 vs 870 GDI MB is based on the
difference between 23bpp and 32bbp?
2) Memory usage after inserting the 3 files = 1,9 GB
Memory usage when reopening the saved file + moving images = 1,3 GB is
something else. unrelated to Skia
3) Memory usage from 1,8 GB to 2,5 GB on save is expected.. As I still not sure
what the export filter actually does.. Is the image read again into memory for
some file information or something like that. Its not image compression/ nor
the plain image itself (75 + 75 + 7,5 MB). It seems unnecessary at plain sight</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>