After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 730280 - Thumbnails causes slow page changes
Thumbnails causes slow page changes
Status: RESOLVED DUPLICATE of bug 691448
Product: evince
Classification: Core
Component: general
3.12.x
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-05-16 23:03 UTC by Adrian Johnson
Modified: 2017-05-30 16:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Adrian Johnson 2014-05-16 23:03:05 UTC 
When viewing some PDF files such as this one:

http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf

and thumbnails are displayed in the sidebar, selecting page up/down is slow if the thumbnail is not already rendered. ie if the current displayed page is at the bottom of the thumbnails sidebar, selecting the next page is delayed by 2 - 3 seconds. But if I selected the previous page, which is already displayed in the thumbnails sidebar, it is displayed in a fraction of a second.
Comment 1 José Aliste 2014-05-16 23:06:58 UTC 
This is a known limitation of GtkIconView and the way we are doing the cache of thumbnails. Basically GtkIconView is doing Height For width calculations and these are redone each time we update one thumbnail image...
Comment 2 Germán Poo-Caamaño 2014-05-16 23:10:00 UTC 
Either related or a duplicated of Bug 730280
Comment 3 Germán Poo-Caamaño 2015-10-16 14:54:05 UTC 
Probably I meant Bug 342110 :-)
Comment 4 Germán Poo-Caamaño 2015-10-16 14:56:56 UTC 
FWIW, it is also slow even when showing the Index pane.
Comment 5 Nelson Benitez 2017-05-30 16:35:08 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the code repository.

*** This bug has been marked as a duplicate of bug 691448 ***