From: John B. <joh...@gm...> - 2013-09-28 16:58:21
|
On Sat, Sep 28, 2013 at 9:30 AM, Bob Friesenhahn < bfr...@si...> wrote: > Firefox on my Android phone is consuming 259MB of storage, 28.12MB of > which is application binaries. Why should we care about a growth of 8500 > bytes? For better or worse libpng has been space-optimized over the last two or three years for Firefox. I've done other space optimizations that should be generic, but the specific tested platform has always been Firefox. I can't remember seeing a space-related issue from any other app. The fact of the matter is that libpng is an easy target for managers concerned about code bloat; libpng comes pre-bloated because it provides so much image processing and so many features and because any given app uses so few of them. Consequently it is important to know whether or not the 8500 bytes are the ICC profile checks. If they are that's fine, because the checks detect a number of cases where the ICC profile data is almost certain to cause problems, including crashes, inside a CMS. It's not really libpng's job to detect these; the CMS should do it. However it was much easier for me to do moderately complete profile validation than it was to deal with the random bugs that would otherwise be fired at libpng. It takes a long time to track down a color space bug, particularly as it often requires access to the particular CMS which shows the problem. John Bowler |