From mint-bounce@lists.fishpool.fi Sat Oct 7 12:59:04 2006 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de From: Eero Tamminen Organization: Koti To: mint@lists.fishpool.fi Subject: Re: [MiNT] JPEG Lib Date: Sat, 7 Oct 2006 13:53:41 +0300 User-Agent: KMail/1.6.2 Cc: Maurits van de Kamp , mint@fishpool.com References: <0004ab75.01c788f814d0@smtp.freeola.net> <165747A1-2026-4EAB-9180-4A13D486734B@bassment.nu> In-Reply-To: <165747A1-2026-4EAB-9180-4A13D486734B@bassment.nu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200610071353.41708.oak@helsinkinet.fi> X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: oak@helsinkinet.fi Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-1.0 tagged_above=-50.5 required=7.0 tests=BAYES_00 X-Spam-Level: Hi, On Saturday 07 October 2006 00:00, Maurits van de Kamp wrote: > > I don' think it is happening with all jpegs. > > Maybe only with progressive jpegs? Just a wild guess, could be a > starting point. :o) Probably not related, but for other jpeg image types you can ask the jpeg lib to scale huge images smaller (with 2,4,8 factors) while it's decompressing them, to save memory. With progressive jpeg images you cannot do that, the library needs the original full size image data in memory to progress it... (On Linux this can be clearly seen when Valgrinding/Massifing image apps with different jpeg types.) - Eero