Bug 187997 - 100% cpu load with "Loading..." message that never ends
100% cpu load with "Loading..." message that never ends
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: evince (Show other bugs)
5
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: Kristian Høgsberg
bzcl34nup
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-04-05 05:44 EDT by Dimitris
Modified: 2008-04-03 22:41 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-04-03 22:41:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
PDF that causes evince to go 100% cpu load (119.79 KB, application/octet-stream)
2006-04-05 05:44 EDT, Dimitris
no flags Details

  None (edit)
Description Dimitris 2006-04-05 05:44:31 EDT
Description of problem:

I have several PDF files that evince can't open properly. Once they are opened
all the pages display a "Loading..." message, CPU usage reaches 100% and the
whole thing just stays there for hours.


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

evince-0.5.1-3


How reproducible:

every time.


Steps to Reproduce:
1. evince some.pdf
2. watch cpu
3. wait...
  
Actual results:

cpu usage at 100% without results

Expected results:

display pdf

Additional info:

all the PDF files that cause this problem are written in Greek.
Comment 1 Dimitris 2006-04-05 05:44:31 EDT
Created attachment 127334 [details]
PDF that causes evince to go 100% cpu load
Comment 2 Kristian Høgsberg 2006-04-05 11:46:51 EDT
This is a known performance problem in poppler (the pdf renderer used by
evince). It is indeed caused by the Greek fonts, which are embedded bitmap fonts
(type 3).  We're hoping to fix this in the fc6 timeframe.
Comment 3 Dimitris 2006-04-05 12:39:41 EDT
FC6 !!!???? thats in.. 6 or months? :(
Comment 4 Bug Zapper 2008-04-03 22:33:26 EDT
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
http://fedoraproject.org/wiki/LifeCycle/EOL

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Comment 5 Dimitris 2008-04-03 22:41:52 EDT
Fixed in a later release (FC7 and newer)

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