Created attachment 62790 [details] Inkscape docked dialogs Version: unspecified (using KDE 4.7.0) OS: Linux In Inkscape, when having two or three docked dialogs, scrolling on them is laggy and slow. It doesn't happen with other gtk themes. I tested this on two machines with same results (Nvidia and Intel graphic cards). Reproducible: Always Steps to Reproduce: Using oxygen-gtk theme, open Inkscape, maximize its window and open three o more dialogs (like "Fill and stroke", "Layers" and "Align and distribute") so that they were docked. Scroll on them. Actual Results: Laggy and slow scroll. Expected Results: Smooth scroll like other gtk themes. Using oxygen-gtk 1.1.1 and gtk2 2.24.5.
A Debian user jus reported this issue against Debian's BTS and posted some gtkperf results, please see <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665674#5> for further information.
1. First of all, concerning gtkperf, oxygen is rather heavy theme, and its drawing algorithms are not that simple as in qtcurve, so some slowdown should be expected. 2. Also, to test real performance I'd suggest switching off any animations. 3. For me Inkscape is (and has always been) already very slow even at rendering its basic interface. 4. If scrolling works very slow for you, try disabling inner shadows hack and recompiling (see README). There are several apps which are affected by this problem. But I'm not sure if we are able to overcome this problem, since we are forced to make such inefficient hacks to implement the features we try to. It's GTK+ limitations which make us do such ugly hacks. I guess we'll just close this as WONTFIX or UPSTREAM, but I'll wait for Hugo's opinion.
It is slightly faster scrolling if I recompile after disabling inner shadows. The combo box is still laggy. Here are the gtkperf results: GtkPerf 0.40 - Starting testing: Sun Mar 25 16:34:36 2012 GtkEntry - time: 0.07 GtkComboBox - time: 3.57 GtkComboBoxEntry - time: 5.40 GtkSpinButton - time: 0.54 GtkProgressBar - time: 0.35 GtkToggleButton - time: 0.74 GtkCheckButton - time: 0.76 GtkRadioButton - time: 0.78 GtkTextView - Add text - time: 0.59 GtkTextView - Scroll - time: 1.30 GtkDrawingArea - Lines - time: 0.47 GtkDrawingArea - Circles - time: 1.00 GtkDrawingArea - Text - time: 1.16 GtkDrawingArea - Pixbufs - time: 0.15 --- Total time: 16.90
Same problem here but not only inkscape. Wireshark and MySQL Workbench are very slow when using Oxygen-GTK. Problems are fixed when using QtCurve so I think this is an actual performance bug of Oxygen-GTK. Running on Kubuntu 12.10 64bit.
Also forgot to mention that my system has 8GB or RAM, a dual core Intel Core i5 M520 @2.40GHz CPU and a Nvidia GeForce GT 330M so performance just on displaying apps smoothly shouldn't be an issue. Now that I switched to QtCurve style for GTK apps, I even noticed some very noticable performance boost on firefox and other GTK apps than the ones mentioned in my previous comment.
@Vangelis Oxygen rendering path is much more complex than qt curve, due to gradients, animations, etc. It is therefore expected to be slower and this does not make it a bug. It is your call to decide between performances and features ... (note that you would get even more perfomances improvement would you use the Raleigh style).
Also note that nvidia (or rather, at least some of the versions of the linux drivers) are known to behave badly with respect to cached pixmaps, which oxygen does alot (as opposed to QtCurve), in order to "improve" performances on other graphics card (and other drivers). Not much we can do about this.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
This a KDE 4 bug report. Do we even have Oxygen-GTK in KDE 5? I guess it should just be closed.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!