Summary: | [Wayland] Konversation blocks the GUI thread causing Wayland socket buffer fill up | ||
---|---|---|---|
Product: | [Applications] konversation | Reporter: | Germano Massullo <germano.massullo> |
Component: | general | Assignee: | Konversation Developers <konversation-devel> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | justin.zobel, kde, magiblot, meven29, rdieter, simonandric5 |
Priority: | NOR | Keywords: | wayland |
Version: | 1.7.4 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | WAYLAND_DEBUG=1 konversation |& tee output.out |
Description
Germano Massullo
2017-04-12 17:37:50 UTC
Created attachment 104995 [details]
WAYLAND_DEBUG=1 konversation |& tee output.out
Please report that crash to Qt (In reply to David Edmundson from comment #2) > Please report that crash to Qt Which Qt component? qtwayland component (I assume) I am insisting in upstream bugreport, since it happens also on Qt 5.9. Previously the bugreport did not get much attention due older Qt release I just had a talk with Qt developer Johan Helsing. He found out what is the problem and I do confirm his analysis <johanhelsing>if the client blocks the ui and then the compositor keeps sending mouse move events until the socket fills up and breaks <johanhelsing> the solution is probably to move whatever is blocking the ui for several seconds to a separate thread. See https://bugreports.qt.io/browse/QTBUG-66997 *** Bug 418730 has been marked as a duplicate of this bug. *** Seems this one was closed as a duplicate of https://bugreports.qt.io/browse/QTBUG-66997 but that was closed as "Out of scope". Germano, can you please check if this crash still happening for you? I am not able to reproduce the crash konversation 1.7.6 Thanks Germano. I'm going to mark this bug as resolved, if the issue returns for yourself or others feel free to reopen this report. |