Return-Path: <awaresystems.be+caf_=filtered=awaresystems.be@gmail.com>
Delivered-To: filtered@awaresystems.be
Received: from mx-q.one.com (mx-q.one.com [91.198.169.248])
	by mail6.local (Postfix) with ESMTP id 237BA8014FACC
	for <filtered@awaresystems.be>; Tue, 11 Jun 2013 11:24:23 +0200 (CEST)
X-Virus-Scanned: by one.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
Received-SPF: pass (mx-q: domain of awaresystems.be+caf_=filtered=awaresystems.be@gmail.com designates 209.85.217.169 as permitted sender)
X-Greylist: whitelisted by SQLgrey-1.8.0-rc2
Received: from mail-lb0-f169.google.com (mail-lb0-f169.google.com [209.85.217.169])
	by mx-q.one.com (Postfix) with ESMTP id D6798A4F24
	for <filtered@awaresystems.be>; Tue, 11 Jun 2013 09:24:22 +0000 (UTC)
Received: by mail-lb0-f169.google.com with SMTP id d10so7266263lbj.14
        for <filtered@awaresystems.be>; Tue, 11 Jun 2013 02:24:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=x-forwarded-to:x-forwarded-for:delivered-to:domainkey-status
         :x-gmail-fetch-info:delivered-to:x-virus-scanned:x-amavis-alert
         :x-greylist:mime-version:in-reply-to:references:date:message-id:from
         :to:subject:x-beenthere:x-mailman-version:precedence:list-id
         :list-unsubscribe:list-archive:list-post:list-help:list-subscribe
         :content-type:mime-version:sender:errors-to;
        bh=HHg6wY7tgUiqk0CVhiHHaFO0dIR3fGjdUr+iWCwOsDM=;
        b=fQfO4dmlCX9UBqe9aULdh34kiqBbmmhW2svLxivL8nSQswjAFOJ1/5sTkS0pFdsCDr
         pDb0IZuAYKVW3Orhlj4BylgP+JHaya680GjISoM0u3KXcVZR7Mayx45Mc0WWS0AwUOjH
         Hxaw2YYLy8Dx4reCucruqjyUq5Exw7XoaSW11rI8pM+Ly3EG21tTrAZH+Zvk60bMd8Md
         JLAN94cCZ8btC/oWCxqiPRCtm9qw19+z5PrKmJuM0MgRG3sWoirSS2uIf/nPCVkNT6P2
         +wAk///W3Uf929VwCcqXsNO/79L9LEU1319Y6+Ob6IH12x+69wWnaPk6QuIuT7iQbt9T
         YOXA==
X-Received: by 10.112.181.2 with SMTP id ds2mr8338277lbc.0.1370942662318;
        Tue, 11 Jun 2013 02:24:22 -0700 (PDT)
X-Forwarded-To: filtered@awaresystems.be
X-Forwarded-For: awaresystems.be@gmail.com filtered@awaresystems.be
Delivered-To: awaresystems.be@gmail.com
Received: by 10.114.82.70 with SMTP id g6csp132385ldy;
        Tue, 11 Jun 2013 02:24:21 -0700 (PDT)
X-Received: by 10.112.163.132 with SMTP id yi4mr8411043lbb.88.1370942660621;
        Tue, 11 Jun 2013 02:24:20 -0700 (PDT)
DomainKey-Status: bad format
Received-SPF: neutral (google.com: 91.198.169.50 is neither permitted nor denied by best guess record for domain of tiff-bounces@lists.maptools.org) client-ip=91.198.169.50;
Received: by 10.152.100.180 with POP3 id ez20mf3259930lab.32;
        Tue, 11 Jun 2013 02:24:20 -0700 (PDT)
X-Gmail-Fetch-Info: info@awaresystems.be 1 pop.awaresystems.be 110 info@awaresystems.be
Delivered-To: info@awaresystems.be
Received: from mx-c.one.com (mx-c.one.com [91.198.169.50])
	by mail6.local (Postfix) with ESMTP id B5BFA8014FACC
	for <info@awaresystems.be>; Tue, 11 Jun 2013 10:29:52 +0200 (CEST)
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0-rc2
Received: from lists.maptools.org (ks365428.kimsufi.com [94.23.4.142])
	by mx-c.one.com (Postfix) with ESMTP id 849E677E4B
	for <info@awaresystems.be>; Tue, 11 Jun 2013 08:29:52 +0000 (UTC)
Received: from [10.1.0.241] (localhost.localdomain [127.0.0.1])
	by lists.maptools.org (Postfix) with ESMTP id 264F335C03B;
	Tue, 11 Jun 2013 03:29:00 -0500 (EST)
Received: from mail-la0-f65.google.com (mail-la0-f65.google.com
	[209.85.215.65])
	by lists.maptools.org (Postfix) with ESMTPS id 12B3035C03B
	for <tiff@lists.maptools.org>; Tue, 11 Jun 2013 03:25:32 -0500 (EST)
Received: by mail-la0-f65.google.com with SMTP id lx15so1439420lab.8
	for <tiff@lists.maptools.org>; Tue, 11 Jun 2013 01:25:31 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.42.236 with SMTP id r12mr6806264lal.46.1370939131322;
	Tue, 11 Jun 2013 01:25:31 -0700 (PDT)
Received: by 10.114.176.162 with HTTP; Tue, 11 Jun 2013 01:25:31 -0700 (PDT)
In-Reply-To: <CAL5BmcReOLzb-Pm3o0PYvRBzb4Pnno7AuhXFED0MCWGnbQPKBw@mail.gmail.com>
References: <CAL5BmcSAZLK=2KTidKAh4OZD=8H1V3u5adTeak8Pwmh9zxXVXQ@mail.gmail.com>
	<alpine.GSO.2.01.1306101313170.7509@freddy.simplesystems.org>
	<CAL5BmcReOLzb-Pm3o0PYvRBzb4Pnno7AuhXFED0MCWGnbQPKBw@mail.gmail.com>
Date: Tue, 11 Jun 2013 11:25:31 +0300
Message-ID: <CAL5BmcTJRAvVKnEC_EnosPZvyPiDyTj+Cb+fWJ==-7hjLHsKfA@mail.gmail.com>
From: Christos Charalambous <chrischaralambous80@gmail.com>
To: tiff@lists.maptools.org
Subject: [Tiff] Fwd:  Detection of corrupted TIFF files bug
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1594144949=="
Mime-version: 1.0
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org

--===============1594144949==
Content-Type: multipart/alternative; boundary=001a11c34b9aee687304dedca325

--001a11c34b9aee687304dedca325
Content-Type: text/plain; charset=ISO-8859-1

---------- Forwarded message ----------
From: Christos Charalambous <chrischaralambous80@gmail.com>
Date: 2013/6/11
Subject: Re: [Tiff] Detection of corrupted TIFF files bug
To: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>


Thanks for the response Bob ,

The resolution is about 1280x672 . The images that have this resolution
more or less are identified as corrupted . I have 3 GB ram on my system .
Is it possible that the ReadRGBAImage process is using all my ram ?

Kind regards

Chris


2013/6/10 Bob Friesenhahn <bfriesen@simple.dallas.tx.us>

> On Mon, 10 Jun 2013, Christos Charalambous wrote:
>
>>
>> The problem is that although some of the images are detected correctly as
>> corrupted , others which are scanned correctly are dete
>> cted as corrupted as well . Those that are wrongly detected as corrupted
>> , have a big resolution , but i don't think that this ha
>> s anything to do with it .
>>
>
> Why do you assume that image resolution has nothing to do with it? The
> interface you are using (ReadRGBAImage()) needs to buffer the whole decoded
> image in RAM and so it is likely that the system does not have sufficient
> memory available to support high resolution images.
>
> Bob
> --
> Bob Friesenhahn
> bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/**
> users/bfriesen/ <http://www.simplesystems.org/users/bfriesen/>
> GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
>

--001a11c34b9aee687304dedca325
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><br><div class=3D"gmail_quote">---------- Forwarded me=
ssage ----------<br>From: <b class=3D"gmail_sendername">Christos Charalambo=
us</b> <span dir=3D"ltr">&lt;<a href=3D"mailto:chrischaralambous80@gmail.co=
m">chrischaralambous80@gmail.com</a>&gt;</span><br>
Date: 2013/6/11<br>Subject: Re: [Tiff] Detection of corrupted TIFF files bu=
g<br>To: Bob Friesenhahn &lt;<a href=3D"mailto:bfriesen@simple.dallas.tx.us=
">bfriesen@simple.dallas.tx.us</a>&gt;<br><br><br><div dir=3D"ltr">Thanks f=
or the response Bob ,<div>
<br></div><div>The resolution is about 1280x672 . The images that have this=
 resolution more or less are identified as corrupted . I have 3 GB ram on m=
y system . Is it possible that the ReadRGBAImage process is using all my ra=
m ?</div>

<div><br></div><div>Kind regards</div><div><br></div><div>Chris</div></div>=
<div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br><br>=
<div class=3D"gmail_quote">2013/6/10 Bob Friesenhahn <span dir=3D"ltr">&lt;=
<a href=3D"mailto:bfriesen@simple.dallas.tx.us" target=3D"_blank">bfriesen@=
simple.dallas.tx.us</a>&gt;</span><br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div>On Mon, 10 Jun 2013, Christos Charalamb=
ous wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
The problem is that although some of the images are detected correctly as c=
orrupted , others which are scanned correctly are dete<br>
cted as corrupted as well . Those that are wrongly detected as corrupted , =
have a big resolution , but i don&#39;t think that this ha<br>
s anything to do with it .<br>
</blockquote>
<br></div>
Why do you assume that image resolution has nothing to do with it? The inte=
rface you are using (ReadRGBAImage()) needs to buffer the whole decoded ima=
ge in RAM and so it is likely that the system does not have sufficient memo=
ry available to support high resolution images.<span><font color=3D"#888888=
"><br>


<br>
Bob<br>
-- <br>
Bob Friesenhahn<br>
<a href=3D"mailto:bfriesen@simple.dallas.tx.us" target=3D"_blank">bfriesen@=
simple.dallas.tx.us</a>, <a href=3D"http://www.simplesystems.org/users/bfri=
esen/" target=3D"_blank">http://www.simplesystems.org/<u></u>users/bfriesen=
/</a><br>


GraphicsMagick Maintainer, =A0 =A0<a href=3D"http://www.GraphicsMagick.org/=
" target=3D"_blank">http://www.GraphicsMagick.org/</a><br>
</font></span></blockquote></div><br></div>
</div></div></div><br></div>

--001a11c34b9aee687304dedca325--

--===============1594144949==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
--===============1594144949==--
