<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Cache lcms transformed values for ICC colorspaces in getRGB(), getCMYK() and getGray()" href="https://bugs.freedesktop.org/show_bug.cgi?id=68420#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Cache lcms transformed values for ICC colorspaces in getRGB(), getCMYK() and getGray()" href="https://bugs.freedesktop.org/show_bug.cgi?id=68420">bug 68420</a> from <a class="email" href="mailto:aacid@kde.org" title="Albert Astals Cid <aacid@kde.org>"> Albert Astals Cid</a> <pre>I think that having a cache is always a good thing, i'm just scared at how much memory use it could potentially end up using, sure in your case is just a 1MB more over 900MB, wow we really need that much memory? Are you sure you're using valgrind right? Actually the correct tool for this would be massif. Anyway, what i'm trying to say i'd be much happier with some kind of patch if the cache was limited, though obviously that means maitaining a proper cache and not just a std::something, which is both harder to code and may slow it down a bit. Because if we don't limit the cache it can end up being 64M big, no?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>