[poppler] Bogus memory allocation size

[Ralph]

Thanks folks.  What's odd about this PDF, is that I've seen scans much larger that poppler can handle.  The linux system is 64bit, it's one of the stock ubuntu images used for Amazon's ec2. 

-- 
Ralph G.
(co-founder of plangrid.com, blueprints on the iPad)


On Friday, May 4, 2012 at 9:49 AM, suzuki toshiya wrote:

> Dear Josh,
> 
> Thank you for comment. "Bogus memory allocation size" is given by
> gmallocn(), gmallocn3(), or greallocn(). It is not raised by the
> memory exhaust, but by the checking of invalid argument (e.g. requested
> memory size ... numMember x sizeOfMember > INT_MAX, etc).
> I received sample PDF by Ralph and tried on i386 GNU/Linux, but
> could not reproduce the issue. I will try on amd64 systems in
> next week.
> 
> Regards,
> mpsuzuki
> 
> Josh Richardson wrote:
> > I've seen this error on Mac OS when trying to generate an image that was
> > very big (accidentally.)
> > 
> > On 5/3/12 11:05 PM, "suzuki toshiya" <mpsuzuki at hiroshima-u.ac.jp (mailto:mpsuzuki at hiroshima-u.ac.jp)> wrote:
> > 
> > > OK, I'm interested in the sample PDF, although I'm not a maintainer.
> > > What I was thinking in last post was... a PDF including huge rasterized
> > > image (JPEG, PNG, etc) is given to the poppler running on some
> > > embedded systems, and memory exhaust caused in image loading routines.
> > > If the error occurs on OS X or Ubuntu, my guessing would be wrong :-)
> > > 
> > > Regards,
> > > mpsuzuki
> > > 
> > > Ralph wrote:
> > > > Good catch! osx 10.7 and ubuntu 9.10 confirmed.
> > > 
> > > 
> > > _______________________________________________
> > > poppler mailing list
> > > poppler at lists.freedesktop.org (mailto:poppler at lists.freedesktop.org)
> > > http://lists.freedesktop.org/mailman/listinfo/poppler
> > 
>