Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 165738 - evince: corrupted double-linked list: 0x000000383d8326f8 ***
evince: corrupted double-linked list: 0x000000383d8326f8 ***
Product: Fedora
Classification: Fedora
Component: evince (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Kristian Høgsberg
Depends On:
  Show dependency treegraph
Reported: 2005-08-11 13:42 EDT by Jimmie Mayfield
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-22 16:15:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jimmie Mayfield 2005-08-11 13:42:26 EDT
+++ This bug was initially created as a clone of Bug #158437 +++

The original bug was closed when the author could not reproduce it on 0.3.1. 
However, I've been able to reliably reproduce a similar crash with 0.3.2 as
shipped with Fedora Core 4.

Description of problem:
When closing evince I get this error message.

Version-Release number of selected component (if applicable):
evince 0.3.2

How reproducible:

Steps to Reproduce:
There are a couple scenarios but this is the most straightforward (the PAM
documents referenced here were installed with FC4).

1. evince /usr/share/doc/pam-0.79/pdf/pam_appl.pdf
2. from within that window, File->Open and choose
   you should now have 2 document windows open
3. now close the window containing pam_appl.ps

Actual results: the corrupted double-linked list error appears.  Note that the
remaining evince window has effectively hung and the process must be killed.

Expected results:
No error message.

Additional info:
   evince 0.3.2
Comment 1 Kristian Høgsberg 2006-09-22 16:15:59 EDT
I don't see this anymore, closing bug.

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