http://bugs.winehq.org/show_bug.cgi?id=27973
Summary: Treeviews and listviews of the Starcraft 2 Editor freeze very often for a few seconds. Product: Wine Version: 1.3.25 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: florian@fkoeberle.de
The Stacraft 2 Editor is very inresponsive: For example selecting an item in the top left tree view of the trigger editor makes the editor freeze for 3 seconds until it becomes responsive again.
It doesn't matter how you select an item in the top left trigger view: Giving the tree view focus, clicking with the mouse and using up and down arrows to switch the currently selected item causes all a 3 second freeze. The left top treeview is a very large but collapsed tree.
Other treeviews of the trigger editor show also a very bad performance. Response times range from 1 to about 10 seconds. They seem to be depend on the size of the tree.
The archive browser, which can be used to browse textures or models, takes about a half minute (!) to open.
Switching to a differnt listview tab in the data editor can also take multiple seconds. Selecting an item in a long list takes about 2-3 seconds. Once you reduce the number of items displayed by the data editor by for example filtering the performance increases and it becomes very responsive. Even the treeview below the list is faster when the list above is smaller.
http://bugs.winehq.org/show_bug.cgi?id=27973
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dank@kegel.com
--- Comment #1 from Dan Kegel dank@kegel.com 2011-08-05 01:45:43 CDT --- Just to be clear, 'winetricks comctl32' works around this, right?
Have you tried profiling wine with, say, oprofile to see where the slow part is during the 30 second open of the archive browser?
http://bugs.winehq.org/show_bug.cgi?id=27973
--- Comment #2 from Florian florian@fkoeberle.de 2011-08-05 07:30:47 CDT --- It's not a comctl32 bug, native comctl32 has same performance issues.
How to use oprofile?
http://bugs.winehq.org/show_bug.cgi?id=27973
--- Comment #3 from Florian florian@fkoeberle.de 2011-08-05 07:45:37 CDT --- I noticed the following with the texture archive browser:
Searching and closing it takes also 30 seconds. During about 15 of this 30 seconds the treeview of the archive browser has a kind of flickering scrollbar: The part which you usually move around of the scrollbar switches from selected to unselected very frequently. I noticed that flickering only in that texture archive browser, other windows like very similar model archive browser don't flicker. The model archive browser is about as slow as the texture archive browser and they are almost identical. So maybe this means nothing.
http://bugs.winehq.org/show_bug.cgi?id=27973
Florian florian@fkoeberle.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |performance
http://bugs.winehq.org/show_bug.cgi?id=27973
--- Comment #4 from Florian florian@fkoeberle.de 2011-08-06 05:06:01 CDT --- Created an attachment (id=35831) --> (http://bugs.winehq.org/attachment.cgi?id=35831) oprofile report for searching for "a" in the texture archive manager
I tried to create a opcontrol report his way: opcontrol --init opcontrol --setup --event=CPU_CLK_UNHALTED:10000:0:1 --no-vmlinux opcontrol --start # searched for "a" in the archive manager and waited till the about 30 second freeze is over opcontrol --dump opcontrol --stop opreport |head -n 50 > /tmp/opreport.txt opcontrol --deinit
I don't know if that's right, but I have attached the log. I am not sure how to interpret it.
Top 3 are: 1314658 73.2872 no-vmlinux 115447 6.4357 comctl32.dll.so 43645 2.4330 ntdll.dll.so
http://bugs.winehq.org/show_bug.cgi?id=27973
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Abandoned?
--- Comment #5 from Ken Sharp kennybobs@o2.co.uk 2013-08-04 12:07:18 CDT --- Is this still an issue in Wine 1.7 or later?
http://bugs.winehq.org/show_bug.cgi?id=27973
--- Comment #6 from Florian florian@fkoeberle.de 2013-08-11 14:53:20 CDT --- Yes, it is still a problem with wine 1.7.0
http://bugs.winehq.org/show_bug.cgi?id=27973
--- Comment #7 from Florian florian@fkoeberle.de 2013-08-11 15:04:41 CDT --- Oh, and the Archive-Browser has changed, it no longer uses a tree view. Instead it uses a listview and it is fast.(It opens in about 1s and is responsive when you type in the filter box).
The slowness problem however remains. When you select in a trigger action tree view a node it freezes for a few seconds and you can see how the other views are updating (They seem to update multiple times - Maybe more often then they should Or maybe the update should not be drawn?).
Also adding a action in the trigger editor makes it freeze about 4s until it shows a dialog with a listview with a few thousands of rows.
http://bugs.winehq.org/show_bug.cgi?id=27973
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|Abandoned? |
https://bugs.winehq.org/show_bug.cgi?id=27973
--- Comment #8 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.37 or newer) wine? If so, please attach the terminal output in 1.7.37 (see http://wiki.winehq.org/FAQ#get_log).
https://bugs.winehq.org/show_bug.cgi?id=27973
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED
--- Comment #9 from Ken Sharp imwellcushtymelike@gmail.com --- Abandoned
https://bugs.winehq.org/show_bug.cgi?id=27973
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Bruno Jesus 00cpxxx@gmail.com --- Closing abandoned bugs.