https://bugs.kde.org/show_bug.cgi?id=392376
--- Comment #5 from Martin Kostolný <clearmar...@zoho.com> --- Thanks for investigating! And sorry for my late response. This is more an informative update. I've tried a few things recommended by Johan Helsing (https://bugreports.qt.io/browse/QTBUG-66997). 1) Increasing max_dgram_qlen seemed not to help 2) Proposed temporary fix in qtwayland improved the situation but not entirely Just for info: I'm sure the issue is happening on Weston as well. I also agree it is application's responsibility to stay responsive. But I fear even though all heavy lifting is done outside GUItar:) thread there may still be situations when this use-case happens. For example I get crashes when I open bigger text file in Kate. It gets worse when CPU is already under load because of different hungry processes - and in such situation if one performs GUI demanding tasks like moving mouse up/down on Kate minimap, which constantly generates tooltip with text preview, Kate crashes as well. But maybe that can also be fixed by the proposed QtConcurrent::run & qfuturewatcher usage. I'm not sure. Anyway it seems I'm the only Wayland user hit by this issue so we can probably wait if somebody else will complain. I was merely trying to tell about this issue before Plasma Wayland hits more audience :). -- You are receiving this mail because: You are watching all bug changes.
