https://bugs.kde.org/show_bug.cgi?id=489952
TraceyC changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #25 from pallaswept ---
(In reply to Zamundaaa from comment #24)
> Can you still reproduce this issue in Plasma 6.3?
I'm afraid so. Thanks for checking. I saw a few of your timing changes, some I
even got excited enough to cherry pick and p
https://bugs.kde.org/show_bug.cgi?id=489952
Zamundaaa changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=489952
TraceyC changed:
What|Removed |Added
CC||kde...@tlcnet.info
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #23 from pallaswept ---
(In reply to pallaswept from comment #22)
> That appears to stop this glitch, too. For testing consistency I also tried
> this with firefox, just resized it to smallest, and left it in the corner.
> Like this, the who
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #22 from pallaswept ---
(In reply to Zamundaaa from comment #21)
> for now you could get a more accurate reading by leaving glxgears running on
> the screens while doing the testing.
That appears to stop this glitch, too. For testing consi
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #21 from Zamundaaa ---
(In reply to pallaswept from comment #14)
> Hmm, I'm not so sure that's the same issue I'm seeing - In this timeframe on
> the 120Hz monitor I would have had in the region of hundreds of frames where
> it should have d
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #20 from pallaswept ---
(In reply to pallaswept from comment #14)
> The immediately most interesting thing about this is that yes, that's a 0
> byte file, for the desktop (no firefox) scenario, on the 120Hz monitor (my
> secondary).
I trie
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #19 from pallaswept ---
(In reply to pallaswept from comment #14)
> only thing that seems to have any effect is what the cursor is being drawn
> above.
Sorry, I forgot about the 'shake cursor' effect. If I draw these test circles
too fast,
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #18 from pallaswept ---
Created attachment 172332
--> https://bugs.kde.org/attachment.cgi?id=172332&action=edit
firefox 120Hz
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #17 from pallaswept ---
Created attachment 172331
--> https://bugs.kde.org/attachment.cgi?id=172331&action=edit
firefox 60Hz
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #16 from pallaswept ---
Created attachment 172330
--> https://bugs.kde.org/attachment.cgi?id=172330&action=edit
desktop 120Hz
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #15 from pallaswept ---
Created attachment 172329
--> https://bugs.kde.org/attachment.cgi?id=172329&action=edit
desktop 60hz
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #14 from pallaswept ---
(In reply to Zamundaaa from comment #13)
> Okay, there's 58 frames dropped because of late atomic commits in the log of
> the 60Hz monitor (vs. only 10 on the 120Hz one), which would also affect the
> cursor. I think
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #13 from Zamundaaa ---
Okay, there's 58 frames dropped because of late atomic commits in the log of
the 60Hz monitor (vs. only 10 on the 120Hz one), which would also affect the
cursor. I think the fix for bug 490358 should help here too.
--
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #12 from pallaswept ---
Created attachment 172319
--> https://bugs.kde.org/attachment.cgi?id=172319&action=edit
kwin log 120Hz display
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #11 from pallaswept ---
Created attachment 172318
--> https://bugs.kde.org/attachment.cgi?id=172318&action=edit
kwin log 60Hz display
(In reply to Zamundaaa from comment #10)
> Just set it for KWin, and it should put some csv files with p
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #10 from Zamundaaa ---
Yeah, that's very weird.
We have an environment variable to debug performance issues in general, though
I'm not sure if it'll help here, it's worth a shot:
https://invent.kde.org/plasma/kwin/-/wikis/Environment-Variabl
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #9 from pallaswept ---
In addition to the observation above, I just captured a trace which had the
mouse moving in circles over the desktop, and then over firefox (about:blank).
When the mouse was over firefox, I see the drm_vblank_event_de
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #8 from pallaswept ---
(In reply to David Edmundson from comment #7)
> gpuvis: https://github.com/mikesart/gpuvis
Cheers! I had seen this one, but wasn't sure it applied to either KDE or the
nvidia card.
Do you know any magic for tracing
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #7 from David Edmundson ---
gpuvis: https://github.com/mikesart/gpuvis
we have some docs at:
https://invent.kde.org/plasma/kwin/-/wikis/Using-FTrace-Markers
but it's still quite overwhelming .
--
You are receiving this mail because:
You a
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #6 from pallaswept ---
Hi Zamundaaa,
I hope you might be so kind as to lend me some advice. I hope this is not too
far off-topic, although I would use this to troubleshoot this issue.
I haven't done anything like this on linux yet. On Wind
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #5 from pallaswept ---
(In reply to Zamundaaa from comment #4)
> What NVidia driver version are you on?
550.100
> Do you still see this if you set the kernel boot argument
> nvidia.NVreg_EnableGpuFirmware=0
I do.
Thanks again for checki
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #4 from Zamundaaa ---
What NVidia driver version are you on? Do you still see this if you set the
kernel boot argument
> nvidia.NVreg_EnableGpuFirmware=0
?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #3 from pallaswept ---
(In reply to pallaswept from comment #2)
> It's not the sort of thing everyone would notice. Very subjective
I just noticed this very poorly worded description. My apologies for any
confusion I may have caused. To cla
https://bugs.kde.org/show_bug.cgi?id=489952
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org,
|
26 matches
Mail list logo
