Bug 485147 - xpdf segfaults in an obscure but reliable manner
Summary: xpdf segfaults in an obscure but reliable manner
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xpdf
Version: 15
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-11 20:58 UTC by Michal Jaegermann
Modified: 2011-08-31 01:39 UTC (History)
2 users (show)

Fixed In Version: xpdf-3.03-1.fc14
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-30 20:47:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
a sample screen output from described (3.98 KB, text/plain)
2009-02-11 20:58 UTC, Michal Jaegermann
no flags Details
gdb backtrace (2.86 KB, text/plain)
2009-02-11 21:00 UTC, Michal Jaegermann
no flags Details
backtrace from the current xpdf bomb (8.78 KB, text/plain)
2010-04-27 19:21 UTC, Michal Jaegermann
no flags Details

Description Michal Jaegermann 2009-02-11 20:58:53 UTC
Created attachment 331620 [details]
a sample screen output from described

Description of problem:

Here is a reliable way to bomb out from xpdf.
- Start displaying some file
- On a screen menu go to a full screen mode
- Select with a mouse on a scree some rectangle
- From a screen menu do "Zoom to selection"
- Try to scroll up or down with "Page-Up" or "Page-Down"

The last operation may, or may not, work for a moment but upon hitting a page boundary - kaboom!  If cores are turned on then you may later find in there:

Program terminated with signal 11, Segmentation fault.
#0  0x000000335f87b4b2 in _int_malloc () from /lib64/libc.so.6

or

Program terminated with signal 6, Aborted.
#0  0x000000335f832f65 in raise () from /lib64/libc.so.6

It may be that some memory is somewhere stomped upon as core sizes and what is printed on a screen varies quite a bit.  A fairly typical sample is attached.

A sample trace from gdb (attached too) seems to show that in frame 6, XPDFCore.cc:82, the following code:

XPDFCoreTile::~XPDFCoreTile() {
  if (image) {
    gfree(image->data);
    image->data = NULL;
    XDestroyImage(image);
  }
}

attempts to run gfree with image->data already NULL.  Why this really happens, and if there are simpler ways than described to get similar effects, I have no idea.

Version-Release number of selected component (if applicable):
xpdf-3.02-9.fc11
xpdf-3.02-7.fc10

How reproducible:
always as described

Additional info:
I tried that on rawhide and F10, x86_64 and i386 installations. It "works" every time.

Comment 1 Michal Jaegermann 2009-02-11 21:00:47 UTC
Created attachment 331621 [details]
gdb backtrace

Comment 2 Tom "spot" Callaway 2009-03-12 20:29:40 UTC
Upstream confirms that they have this fixed in their next release, but isn't sure what change they made that fixed it, nor do they know when the next release will come out, so this one is going to go stagnant waiting on upstream to release again.

Comment 3 Bug Zapper 2009-06-09 11:17:22 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2010-04-27 12:56:24 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Michal Jaegermann 2010-04-27 19:21:26 UTC
Created attachment 409557 [details]
backtrace from the current xpdf bomb

(In reply to comment #4)
> This message is a reminder that Fedora 11 is nearing its end of life.

This bombs out like it ever was.  Attached is "*** glibc detected *** xpdf: munmap_chunk(): invalid pointer: 0x00007f0e39002010 ***" with xpdf-3.02-15.fc13.x86_64 after steps described in the original report.

Comment 6 Bug Zapper 2011-06-02 18:16:38 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Michal Jaegermann 2011-06-03 06:18:05 UTC
The current xpdf-3.02-16.fc14, and surely xpdf-3.02-16.fc15 too, is crashing the same way as before.  Even a backtrace from glibc with an invalid pointer did not change that much if at all.

I wonder if this will ever get fixed.

Comment 8 Tom "spot" Callaway 2011-08-22 18:31:16 UTC
Revisiting this issue. 3.03 seems to resolve this crash. Please test when the update hits.

Comment 9 Fedora Update System 2011-08-22 19:07:00 UTC
xpdf-3.03-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/xpdf-3.03-1.fc15

Comment 10 Fedora Update System 2011-08-22 19:07:17 UTC
xpdf-3.03-1.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/xpdf-3.03-1.fc14

Comment 11 Fedora Update System 2011-08-22 19:07:33 UTC
xpdf-3.03-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/xpdf-3.03-1.fc16

Comment 12 Fedora Update System 2011-08-23 04:29:32 UTC
Package xpdf-3.03-1.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xpdf-3.03-1.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/xpdf-3.03-1.fc15
then log in and leave karma (feedback).

Comment 13 Michal Jaegermann 2011-08-23 22:08:57 UTC
(In reply to comment #8)
> Revisiting this issue. 3.03 seems to resolve this crash. Please test when the
> update hits.

I tried that with xpdf-3.03-1.fc17.x86_64 on a rawhide installation. Indeed that crash is gone (and I was rather worried that related troubles will resurface in more "everyday" scenarios but scrolling through a document in a big zoom and a full screen mode does have its uses). Thanks. xpdf-3.03 has quite impressive a version specific "laundry list" in CHANGES file. :-)

Just a note: EPEL repos can benefit from these updates too.  I did not notice anything new for EPEL on koji.

Comment 14 Fedora Update System 2011-08-30 20:46:48 UTC
xpdf-3.03-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 15 Fedora Update System 2011-08-31 01:35:11 UTC
xpdf-3.03-1.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 16 Fedora Update System 2011-08-31 01:39:09 UTC
xpdf-3.03-1.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.