Comment 10 for bug 51538

Revision history for this message
Alex Chekholko (alex-chekholko) wrote : Re: [Bug 51538] Re: Evince crashes with "bogus memory allocation size" error

I tried to reproduce this, but was unable to.

I tried page 59 of the PDF, and page 59 of the manuscript (page 94 of the PDF).

Stock Ubuntu 7.10 , evince 2.20.1

document:
$ md5sum /tmp/irbookonlinereading.pdf
5612fc4ea997806d6dd8ad2929d4fd2d /tmp/irbookonlinereading.pdf

On Fri, Apr 4, 2008 at 7:07 PM, Scott <email address hidden> wrote:
> A publicly accessible .pdf that triggers this error:
> http://nlp.stanford.edu/IR-book/pdf/irbookonlinereading.pdf . Note:
> this document will probably be updated in place, and redistribution is
> not permitted, so this is potentially a time-limited example.
>
> The problem area is on page 59.
>
> Viewing this page in 'fit page width' mode with a small window yields a
> lot of "Error: Bad bounding box in Type 3 glyph" messages. Slowly
> increasing the window size causes evince to exit with the message "Out
> of memory". Maximizing the window or scrolling to page 59 in a large or
> maximized window causes evince to exit with the message "Bogus memory
> allocation size"
>
> See attached gdb backtrace from a breakpoint on exit(). T3FontCache()
> in libpoppler calls gmallocn(8,284192164).
>
> (Note: Trace is not from an ubuntu install. Versions: evince-2.22.0,
> poppler-0.6.1 )
>
> ** Attachment added: "gdb backtrace of the "Bogus memory allocation size" error"
> http://launchpadlibrarian.net/13123201/poppler-bogus-memory-allocation-size-backtrace
>
>
> --
> Evince crashes with "bogus memory allocation size" error
> https://bugs.launchpad.net/bugs/51538
> You received this bug notification because you are a direct subscriber
> of the bug.
>