| Summary: | Kscreenlocker takes a full minute until it is responsive | ||
|---|---|---|---|
| Product: | [Unmaintained] kscreenlocker | Reporter: | spamme |
| Component: | greeter | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | bshah, justin.zobel, mgraesslin |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
GDB backtrace
GDB backtrace (with symbols) |
||
Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install the debug packages and attach a new backtrace. Without the debug symbols we do not see where it crashes. Created attachment 105362 [details]
GDB backtrace (with symbols)
Ah, I recompiled kscreenlocker with the debug symbols, but forgot about Qt :)
Thanks for the update; it looks like a Qt issue. @Christoph Feck So should I go and file a bug on the Qt tracker? Right now it happens only with kscreenlocker though. I'll keep an eye open, see if any other Qt programs show similar behavior. It is related to QQuickWindow (from QtQuick), which is only used by a minority of applications. Is this now resolved upstream? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! I haven't had the problem for a while now, so I suppose it's been fixed. |
Created attachment 105347 [details] GDB backtrace Version: 5.9.5 (latest on Arch Linux x86_64). After my PC is up and running for a few (4~5+) hours, kscreenlocker_greet takes a full minute until it is responsive and reacts to keyboard or mouse input. And yes, I've actually timed it; the standard deviation was +/- 2 seconds. During that minute, CPU usages spikes to 100% and reserved memory (in top) eventually exceeds 500 MB. I've also noticed memory usage increases every 5 seconds or so, and by 10-20 MB increments. When the program's responsive again, CPU returns to normal, while memory usage is reduced to around 400 MB. The problem happens independent of how kscreenlocker_greet is invoked: by locking the screen; letting it happen automatically because of inactivity; or even by running it from the terminal directly (with or without the '--testing' option; it doesn't matter). Sending a HUP signal to the process or using loginctl to unlock the session is a workaround, but very annoying. GDB backtrace (attached) indicates the program is stuck waiting for... something. Since the time kscreenlocker_greet is unresponsive is so precise, I suspect it's a timeout expiring which causes it to be responsive again.