Red Hat Bugzilla – Bug 227438
Epiphany is very slow on page rendering or crashes (pango enabled)
Last modified: 2008-04-09 10:05:28 EDT
Description of problem:
I am forced to use pango enabled epiphany because of some bugs that i submitted
earlier. Now i have performance issues or crashes.
Try to use this page to see what i mean:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Fedora Core 6 is no longer supported, could you please reproduce this with the
updated version of the currently supported distribution (Fedora 7, 8, or
Rawhide)? If this issue turns out to still be reproducible, please let us know
in this bug report. If after a month's time we have not heard back from you, we
will have to close this bug as CANTFIX.
Setting status to NEEDINFO, and awaiting information from the reporter.
[This is mass-filed message to all open Fedora Core 6 bugs related to Xorg or
Gecko. If you see any other reason, why this bug shouldn't be closed, please,
comment on it here.]
Yes, the problem with this specific page exists on fedora 8 and latest epiphany
2.20. Check it for yourself for a moment to see what happens.(things get worse
if you use a relative slow pc)
If pango is disabled then things getting better and you get a message about "a
script not responding" and you can choose between "continue" or "stop script".
If you press "continue" epiphany freezes for 2-3 seconds.
can fully reproduce here both with epiphany-2.20.2-1.fc8 as well as with
Browser gets totally unresponsive and although neither of them crashes (and I
have pretty good hardware here), I get always that "a script not responding dialog".
The page is huge. Could it be that it is just that?
At this point, we're going to only be taking security fixes and major stability
fixes into this release of Fedora. However, we still want to ensure the bug is
fixed in the next version. We'd appreciate if you could test Firefox 3,
available at http://www.mozilla.com/en-US/firefox/all-beta.html or now shipping
as the default in Fedora rawhide and provide feedback as to whether it still
exists so we can file a ticket upstream to try to fix it in Firefox 3 before it
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.
[This is a mass-closing request, if you think that this bug shouldn't be closed,
please, reopen with additional information.]