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 779961 - Layers dialogue: Slow scrolling with lots of layers
Layers dialogue: Slow scrolling with lots of layers
Product: GIMP
Classification: Other
Component: User Interface
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
Depends on:
Reported: 2017-03-13 03:32 UTC by Daniel Hug
Modified: 2018-06-17 22:21 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Daniel Hug 2017-03-13 03:32:42 UTC
When viewing PSDs in Gimp that have over a hundred layers in many different layer groups, it is very slow to do much in that layer dialogue - especially to scroll. Two possible solutions?:
 - Have all layer groups be collapsed / folded by default
 - Have a collapse all and uncollapse all button

Other people want this too:
Comment 1 Michael Schumacher 2017-03-13 08:48:06 UTC
I guess it will be equally slow with over a hundred layer groups.

Collapsing is a workaround, we'd like to figure out where the slowness comes from, i.e. what takes time when scrolling.
Comment 2 Jehan 2017-03-17 03:34:37 UTC

Could you upload an example file where you encounter such a slowness issue please? Will make it faster to confirm. :-)

Is scrolling slow only when scrolling with the mouse middle button or same when scrolling by dragging the scrollbar?

There are similar scrolling issues to some other applications in GTK+, like libreoffice, and people who experience this often realize that scrolling by dragging the scrollbar is smooth (whereas using the middle button is extra-slow). No idea if that is the same problem, just throwing thoughts out. This may be a GTK+ issue.
Comment 3 GNOME Infrastructure Team 2018-05-24 17:34:33 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance:
Comment 4 Michael Natterer 2018-06-17 22:21:06 UTC
Daniel, please answer my question at