https://bugs.kde.org/show_bug.cgi?id=442659
Ash Blake changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=439873
--- Comment #27 from Ash Blake ---
(In reply to Zamundaaa from comment #21)
> The patch should "fix" that but I'd still like to find the actual source of
> the problem.
The stability has definitely improved with that patch, b
https://bugs.kde.org/show_bug.cgi?id=439873
--- Comment #26 from Ash Blake ---
Created attachment 141964
--> https://bugs.kde.org/attachment.cgi?id=141964&action=edit
KWin DRM log messages from full Plasma session
I got some of these errors in my wayland-session.log now.
They'
https://bugs.kde.org/show_bug.cgi?id=439873
--- Comment #23 from Ash Blake ---
Created attachment 141956
--> https://bugs.kde.org/attachment.cgi?id=141956&action=edit
KWin DRM log from another machine (AMD GPU)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439873
--- Comment #22 from Ash Blake ---
Created attachment 141955
--> https://bugs.kde.org/attachment.cgi?id=141955&action=edit
KWin DRM log messages
(In reply to Zamundaaa from comment #21)
> You likely have some lines with something like &q
https://bugs.kde.org/show_bug.cgi?id=439873
--- Comment #19 from Ash Blake ---
(In reply to Ash Blake from comment #18)
> and these multiple deletions may be normal
Unfortunately, there is something wrong anyways even though it is not multiple
deletion.
Right before the crash, a pipeline t
https://bugs.kde.org/show_bug.cgi?id=439873
--- Comment #18 from Ash Blake ---
(In reply to Ash Blake from comment #17)
Nevermind, I totally forgot allocation could just happen at the same address
after deleting something there and these multiple deletions may be normal.
I'll redo it,
https://bugs.kde.org/show_bug.cgi?id=439873
Ash Blake changed:
What|Removed |Added
Attachment #141922|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=439873
--- Comment #16 from Ash Blake ---
This crash is also quite unpredictable, sometimes I can switch a lot of times
between two sessions with no crash, and sometimes it will crash on the first
try. Usually if the crash already occurs in one of the
https://bugs.kde.org/show_bug.cgi?id=439873
--- Comment #15 from Ash Blake ---
(In reply to Zamundaaa from comment #14)
> Sounds a lot like https://bugs.kde.org/show_bug.cgi?id=442677
It really does, but I already have the commit that fixed that bug in my KWin
build.
Seems like there
https://bugs.kde.org/show_bug.cgi?id=439873
--- Comment #13 from Ash Blake ---
And with the crash from the getProp call in KWin::DrmPipeline::setSyncMode,
m_crtc has been a null pointer in at least two backtraces
(gdb) p *m_pipeline
$2 = {
m_output = 0x5592ffd79a3b,
m_gpu = 0x5597a695a010
https://bugs.kde.org/show_bug.cgi?id=439873
--- Comment #12 from Ash Blake ---
(In reply to Ash Blake from comment #11)
> Created attachment 141939 [details]
The contents of m_gpu look odd - cursor size of 262147x458757, insanely high
file descriptor and some suspicious looking addresses.
https://bugs.kde.org/show_bug.cgi?id=439873
--- Comment #11 from Ash Blake ---
Created attachment 141939
--> https://bugs.kde.org/attachment.cgi?id=141939&action=edit
Another backtrace, crash in DrmPipeline::populateAtomicValues
Another crash on VT switch. obj pointed to an unr
https://bugs.kde.org/show_bug.cgi?id=438010
Ash Blake changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=442852
--- Comment #4 from Ash Blake ---
Proposed fix that also fixes the original warnings:
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1081
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=442852
Ash Blake changed:
What|Removed |Added
CC||telepath...@tutanota.com
--- Comment #2 from Ash
https://bugs.kde.org/show_bug.cgi?id=439873
--- Comment #9 from Ash Blake ---
Created attachment 141923
--> https://bugs.kde.org/attachment.cgi?id=141923&action=edit
Screen recording showing the problem
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439873
--- Comment #8 from Ash Blake ---
Created attachment 141922
--> https://bugs.kde.org/attachment.cgi?id=141922&action=edit
Backtrace (git master)
The old user's and new user's backtraces look the same.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=439873
Ash Blake changed:
What|Removed |Added
CC||telepath...@tutanota.com
--- Comment #7 from Ash
https://bugs.kde.org/show_bug.cgi?id=438010
--- Comment #13 from Ash Blake ---
This happened because there was no check if the resource is valid before
calling sendButton.
I created a merge request:
https://invent.kde.org/plasma/kwin/-/merge_requests/1461
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=438010
--- Comment #12 from Ash Blake ---
I attached GDB to KWin and checked where the null pointer came from in
TabletToolV2InterfacePrivate::targetResource().
m_surface was not null, but later resourceMap().value(*client) returned 0x0.
--
You are
https://bugs.kde.org/show_bug.cgi?id=438010
--- Comment #11 from Ash Blake ---
I rebuilt libwayland with debug symbols.
Resource was a null pointer:
#0 wl_resource_post_event (resource=0x0, opcode=17) at
../wayland-1.19.0/src/wayland-server.c:248
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=438010
Ash Blake changed:
What|Removed |Added
CC||telepath...@tutanota.com
--- Comment #10 from Ash
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #37 from Ash Blake ---
(In reply to Vlad Zahorodnii from comment #36)
> Created attachment 141876 [details]
> Potential solution (untested)
>
> If you apply the attached patch, does the issue go away?
Yes, I just tested
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #34 from Ash Blake ---
(In reply to Vlad Zahorodnii from comment #33)
> Thanks for the great analysis, Ash! This is definitely very strange. At
> quick glance, I don't see how file descriptors can be leaked in kwin.
Well, it d
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #32 from Ash Blake ---
Created attachment 141875
--> https://bugs.kde.org/attachment.cgi?id=141875&action=edit
A Python script that parses strace output for FD information
I wrote a script to parse strace output and abbrev
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #31 from Ash Blake ---
(In reply to Ash Blake from comment #30)
> break PlasmaWindow::Private::iconChangedCallback
> commands
> silent
> printf "hello\n"
> end
Oops, forgot a continue there.
br
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #30 from Ash Blake ---
> The short burst length of 2 was motivated by observing the popup windows
> flicker without any content sometimes, before the actual popup appeared.
Post scriptum: in fact, when GDB is attached to plasmashell
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #29 from Ash Blake ---
Created attachment 141874
--> https://bugs.kde.org/attachment.cgi?id=141874&action=edit
A C program that reproduces the bug
I figured out which behaviour of the Jetbrains IDEs causes the bug to occur and
I
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #27 from Ash Blake ---
The file descriptor flood comes from PlasmaWindow::Private::iconChangedCallback
(kwayland/src/client/plasmawindowmanagement.cpp:655, master branch).
This can be easily verified by catching pipe2 in the plasmashell
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #25 from Ash Blake ---
This is pretty weird. I just tried running IDEA in KWin only, started from a
TTY.
The file descriptor amount does not skyrocket, and everything is stable.
It also works fine in nested KWin inside a Plasma session
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #24 from Ash Blake ---
Created attachment 141808
--> https://bugs.kde.org/attachment.cgi?id=141808&action=edit
Timelapse of lsof count, after increasing the open fd limit to 8192
This shows the test running for much longer (5
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #23 from Ash Blake ---
Created attachment 141807
--> https://bugs.kde.org/attachment.cgi?id=141807&action=edit
Outputs of lsof -p $KWIN_PID taken every second, from the test start to KWin
crash
Additional logs for #22
--
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #22 from Ash Blake ---
Created attachment 141806
--> https://bugs.kde.org/attachment.cgi?id=141806&action=edit
Screencast demonstrating the rising amount of open files by KWin
Regarding the previous error about too many open files
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #21 from Ash Blake ---
This time KWin didn't crash completely, but entered a weird state.
Plasmashell stopped working, but most of the applications were still running,
including IDEA. I stopped the test, because if it continued it
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #20 from Ash Blake ---
This short script can be used to trigger a crash:
#!/bin/bash
win_id=$(sort <(xdotool search --name "Content window") <(xdotool search
--class "jetbrains-idea") | uniq -d)
sleep 10
while :
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #19 from Ash Blake ---
Created attachment 141801
--> https://bugs.kde.org/attachment.cgi?id=141801&action=edit
Code completion popup window IDs in the debug console
Update: It appears that the crashes are highly correlated w
https://bugs.kde.org/show_bug.cgi?id=438097
Ash Blake changed:
What|Removed |Added
Version|5.22.1 |5.22.90
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #18 from Ash Blake ---
I didn't get a crash so far, but I revisited the previous coredump, as it seems
weird that the EffectWindow was at least a bit intact this time.
Disassembly of the current instruction and the one befo
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #17 from Ash Blake ---
This time, however, it seems EffectWindow was not completely destroyed.
Unlike in the last crash, the data inside EffectWindow is not complete garbage.
For instance, the addresses in toplevel and EffectWindow
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #16 from Ash Blake ---
Okay, it crashed again. The backtrace looks the same as the last one.
The crash is again in kwin4_effect_fade:
(gdb) p this
$3 = (KWin::ScriptedEffect * const) 0x55f805fa1440
(gdb) set $data_start = (char
https://bugs.kde.org/show_bug.cgi?id=438097
--- Comment #15 from Ash Blake ---
Additional information about that EffectWindow, as I forgot it's actually an
instance of EffectWindowImpl and didn't dump members of the latter.
Both the toplevel and sw pointers lead to inaccessible memory
https://bugs.kde.org/show_bug.cgi?id=438097
Ash Blake changed:
What|Removed |Added
CC||telepath...@tutanota.com
--- Comment #14 from Ash
43 matches
Mail list logo
