Open kennylevinsen opened 3 years ago
Inspecting the layout, it would appear that there are two problems:
The end-result is that there are N M k widgets, where N is the number of buffers, M is the number of messages, and k is the number of widgets per message. This very quickly gets out of control, leading to terrible performance: Srain is unresponsive for a long period of time when connecting to my bouncer, has long delays when animating the "got focus"/"focus lost" animation, and is also pretty unusable when the Gtk debugger is active.
Possible solutions:
Number 3 can already be implemented, and so can number 1 if there are any ideas for simplification. Number 2 would be part of a Gtk4 port (and, with 3.99 out, it's time to play with that anyway).
Thanks for pointing out this.
The simplest way may be take a taste of GTK4, I will have a try when I have time.
As GTK4 is released, we are starting to migrate to GTK4 :)
clear
command, may be helpful to this.
Here is a backtrace from GDB while analyzing some significant performance issues:
This call stack is 2580 frames deep, and appears caused by recursively visiting sibling nodes for which there are many. This ends up running for every
I imagine this is caused by a bad widget layout or unfortunate CSS, but I haven't analyzed it further. Tested on 1.1.2.