| Summary: | resource leak: the number of threads increases over time, boundlessly | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Julien Muchembled <jm> |
| Component: | platform-x11-standalone | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kde, qydwhotmail |
| Priority: | NOR | ||
| Version First Reported In: | 5.27.5 | ||
| Target Milestone: | --- | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| URL: | https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037268 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | strace output just after kwin_x11 has started | ||
|
Description
Julien Muchembled
2023-06-11 09:46:38 UTC
How did you see how many threads were being used? Could you reproduce this with firefox going fullscreen and back? (In reply to David Edmundson from comment #1) > How did you see how many threads were being used? With `ls |wc -l` within the `/proc/<pid>/task/` folder of kwin_x11 process. > Could you reproduce this with firefox going fullscreen and back? No issue with Firefox. I even tried a youtube video. BTW, I only mentioned mpv as an example but there's also vlc. To get more information, I can try patches against 4.27.5 if you have any. Created attachment 159609 [details]
strace output just after kwin_x11 has started
During the capture, I used mpv and went/left fullscreen twice. If I look at correctly, leaked threads are stuck at a futex syscall so it may not be useful.
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! Cannot reproduce 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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |