Interesting find. I can reproduce this on multiple distro's using GTK+ version 3.18, if you add at least one network to the list. The more networks you add the more cpu gets used.
When I have more time I will try to locate what GtkTreeView property or method within Haguichi is triggering this, by disabling things one by one (search, pixmaps, etc). Whatever there is to find I hope there's a way around, otherwise the solution lies in the hands of the GTK+ developers, whom are mainly good for creating new stuff and breaking existing stuff... not so much fixing old stuff like ol'treeviews.
Interesting find. I can reproduce this on multiple distro's using GTK+ version 3.18, if you add at least one network to the list. The more networks you add the more cpu gets used.
Using GTK+ version 3.16 everything works normal. So I suspect one or more of these GtkTreeView changes is the root cause of the problem: /git.gnome. org/browse/ gtk+/log/ ?h=gtk- 3-18&qt= grep&q= treeview
https:/
When I have more time I will try to locate what GtkTreeView property or method within Haguichi is triggering this, by disabling things one by one (search, pixmaps, etc). Whatever there is to find I hope there's a way around, otherwise the solution lies in the hands of the GTK+ developers, whom are mainly good for creating new stuff and breaking existing stuff... not so much fixing old stuff like ol'treeviews.