pdftotext crashed with signal 24 in FlateStream::getHuffmanCodeWord()

Bug #380179 reported by mizu
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
poppler (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Ubuntu 9.04

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/pdftotext
Package: poppler-utils 0.10.5-1ubuntu2
ProcCmdline: pdftotext -enc UTF-8 -q -nopgbrk /usr/share/doc/texlive-doc/latex/minitoc/minitoc.pdf -
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 24
SourcePackage: poppler
StacktraceTop:
 FlateStream::getHuffmanCodeWord ()
 FlateStream::readSome () from /usr/lib/libpoppler.so.4
 FlateStream::getChar () from /usr/lib/libpoppler.so.4
 GfxFont::readEmbFontFile () from /usr/lib/libpoppler.so.4
 Gfx8BitFont::Gfx8BitFont () from /usr/lib/libpoppler.so.4
Title: pdftotext crashed with signal 24 in FlateStream::getHuffmanCodeWord()
Uname: Linux 2.6.30-020630rc7-generic i686
UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare scanner users vboxusers video

Revision history for this message
mizu (michal-zimen) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:FlateStream::getHuffmanCodeWord (this=0x9062d48,
FlateStream::readSome (this=0x9062d48) at Stream.cc:4195
FlateStream::getChar (this=0x9062d48) at Stream.cc:4129
GfxFont::readEmbFontFile (this=0x9123f38, xref=0x8f6ffe8,
Gfx8BitFont (this=0x9123f38, xref=0x8f6ffe8,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in poppler (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

thanks for the report, could you attach the minitoc.pdf file to the report? thanks in advance.

Changed in poppler (Ubuntu):
status: New → Incomplete
Revision history for this message
mizu (michal-zimen) wrote : Re: [Bug 380179] Re: pdftotext crashed with signal 24 in FlateStream::getHuffmanCodeWord()

Hi pedro,

Here it is:

On Mon, Jun 8, 2009 at 10:32 PM, Pedro Villavicencio <email address hidden>wrote:

> thanks for the report, could you attach the minitoc.pdf file to the
> report? thanks in advance.
>
> ** Changed in: poppler (Ubuntu)
> Status: New => Incomplete
>
> --
> pdftotext crashed with signal 24 in FlateStream::getHuffmanCodeWord()
> https://bugs.launchpad.net/bugs/380179
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
--mizu--

"Every man dies; not every man really lives."
                      --William Wallace, Braveheart

Revision history for this message
Pedro Villavicencio (pedro) wrote :

works fine with latest poppler on karmic, could you please try the same there? Thanks in advance.

visibility: private → public
Revision history for this message
Rey Tucker (rtucker) wrote :

Is this perhaps occurring during indexing by tracker? If so, it may be a duplicate of bug 450795; signal 24 is from a CPU time limit being exceeded.

Revision history for this message
LeeV (leev) wrote :

Upgrade of Karmic yesterday, this error popped up today. Not sure why, I don't think I tried to open a PDF doc?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

LeeV are you sure its the same issue you're facing? could you please open a new report with apport? thanks.

Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

Thank you for taking the time to report this crash and helping to make
Ubuntu better. We've discovered that apport was inappropriately
reporting signal 24 crashes. These reports are a result of an
application exceeding limits set on CPU time which is normal behavior.
Subsequently, we are closing this bug report as Invalid. We apologize
for any inconvenience this has caused. Please report any future bugs or
crashes that you may have.

Changed in poppler (Ubuntu):
status: Incomplete → Invalid
tags: added: signal-24
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.