[konsole] [Bug 367882] FileFilter implementation cause konsole cpu usage to go to 80-100%

https://bugs.kde.org/show_bug.cgi?id=367882 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO

[konsole] [Bug 367882] FileFilter implementation cause konsole cpu usage to go to 80-100%

https://bugs.kde.org/show_bug.cgi?id=367882 --- Comment #10 from Bug Janitor Service --- 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

[konsole] [Bug 367882] FileFilter implementation cause konsole cpu usage to go to 80-100%

https://bugs.kde.org/show_bug.cgi?id=367882 Kurt Hindenburg changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED

[konsole] [Bug 367882] FileFilter implementation cause konsole cpu usage to go to 80-100%

https://bugs.kde.org/show_bug.cgi?id=367882 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail

[konsole] [Bug 367882] FileFilter implementation cause konsole cpu usage to go to 80-100%

https://bugs.kde.org/show_bug.cgi?id=367882 Alexander changed: What|Removed |Added CC||alex3...@mail.ru --- Comment #8

[konsole] [Bug 367882] FileFilter implementation cause konsole cpu usage to go to 80-100%

https://bugs.kde.org/show_bug.cgi?id=367882 Michael Palimaka changed: What|Removed |Added Keywords||regression -- You

[konsole] [Bug 367882] FileFilter implementation cause konsole cpu usage to go to 80-100%

https://bugs.kde.org/show_bug.cgi?id=367882 --- Comment #7 from Michael Palimaka --- I'm experiencing the same issue, bisecting it to the same commit as mentioned in comment #0. The lag/delays are bad enough to make Konsole basically unusable for me, so I'm more than happy

[konsole] [Bug 367882] FileFilter implementation cause konsole cpu usage to go to 80-100%

https://bugs.kde.org/show_bug.cgi?id=367882 andreas.sturmlech...@gmail.com changed: What|Removed |Added CC||andreas.sturmlechner@gmail.

[konsole] [Bug 367882] FileFilter implementation cause konsole cpu usage to go to 80-100%

https://bugs.kde.org/show_bug.cgi?id=367882 Michael Palimaka changed: What|Removed |Added CC||kensing...@gentoo.org

[konsole] [Bug 367882] FileFilter implementation cause konsole cpu usage to go to 80-100%

https://bugs.kde.org/show_bug.cgi?id=367882 --- Comment #6 from John Stanley --- (In reply to Martin Sandsmark from comment #5) > Sorry, I meant line 546, and «qDebug().noquote() << regex;» is probably > better. Sorry for the delay; here's the regex:

[konsole] [Bug 367882] FileFilter implementation cause konsole cpu usage to go to 80-100%

https://bugs.kde.org/show_bug.cgi?id=367882 --- Comment #5 from Martin Sandsmark --- Sorry, I meant line 546, and «qDebug().noquote() << regex;» is probably better. -- You are receiving this mail because: You are watching all bug changes.

[konsole] [Bug 367882] FileFilter implementation cause konsole cpu usage to go to 80-100%

https://bugs.kde.org/show_bug.cgi?id=367882 --- Comment #4 from Martin Sandsmark --- I think the issue is that Konsole::ScreenWindow::outputChanged() is emitted every time a mouse button is clicked or the selection changes, which invalidates the current filter results,

[konsole] [Bug 367882] FileFilter implementation cause konsole cpu usage to go to 80-100%

https://bugs.kde.org/show_bug.cgi?id=367882 Martin Sandsmark changed: What|Removed |Added Ever confirmed|0 |1

[konsole] [Bug 367882] FileFilter implementation cause konsole cpu usage to go to 80-100%

https://bugs.kde.org/show_bug.cgi?id=367882 --- Comment #2 from Kurt Hindenburg --- Git commit 07cbdbcd128781fe77d78533436ef2172dcc5993 by Kurt Hindenburg. Committed on 03/09/2016 at 21:34. Pushed by hindenburg into branch 'Applications/16.08'. Change the default to

[konsole] [Bug 367882] FileFilter implementation cause konsole cpu usage to go to 80-100%

https://bugs.kde.org/show_bug.cgi?id=367882 --- Comment #1 from Kurt Hindenburg --- Martin, do you think we should have the profile setting to show these links disabled by default? Or do you have any other suggestions/opinions? -- You are receiving this mail because: