https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #21 from 0BADC0DE ---
Even if I am setting "Scrollback file location: Custom: /tmp/konsole-backlog" I
cannot find that file while konsole is running with non-empty scrollback
content.
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #20 from 0BADC0DE ---
Created attachment 173586
--> https://bugs.kde.org/attachment.cgi?id=173586&action=edit
Output for "lsof | grep konsole > lsof-konsole2.txt"
Same as above, but with "Scrollback file location: User cache directory
(~/
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #19 from 0BADC0DE ---
Created attachment 173585
--> https://bugs.kde.org/attachment.cgi?id=173585&action=edit
Output for "lsof | grep konsole > lsof-konsole.txt"
Output for "lsof | grep konsole > lsof-konsole.txt"
With "Scrollback file l
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #18 from 0BADC0DE ---
(In reply to Waqar Ahmed from comment #16)
> That is expected I think as the file is temporary. At least thats what it
> says in the tooltip when enabling it in the settings.
I don't think so.
I am inspecting that dire
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #17 from Waqar Ahmed ---
Since you are on Arch, building konsole yourself is trivial. I would suggest
adding some printfs in the scrolling code to help might make the situation more
clear. Building konsole is just
- git clone https://invent
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #16 from Waqar Ahmed ---
That is expected I think as the file is temporary. At least thats what it says
in the tooltip when enabling it in the settings.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #15 from 0BADC0DE ---
I just checked the actual cache file size (I never did that so far).
My settings say I should be storing it into "~/.cache/konsole".
But that directory is actually empty.
I am now doubly puzzled.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #14 from Waqar Ahmed ---
I have a less powerful cpu, but can't get it to lag after running ls -l
/usr/bin about 10 times. So maybe the history is bigger than you think
--
You are receiving this mail because:
You are watching all bug change
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #13 from 0BADC0DE ---
Hmmm... I still think this is a bug.
My terminal history was at the time of my test less 64KB (likely even less than
8KB).
How can that lead to the lag on a i7 with 24GB RAM and NVME disks?
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #12 from Waqar Ahmed ---
You seem to be using file-backed scroll history. Reflowing that seems to be
quite slow.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #11 from 0BADC0DE ---
The point seems to be the terminal panel been full of text.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #10 from 0BADC0DE ---
Created attachment 173557
--> https://bugs.kde.org/attachment.cgi?id=173557&action=edit
gzipped perf.data.perfparser
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492896
0BADC0DE changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WORKSFORME |--
https://bugs.kde.org/show_bug.cgi?id=492896
0BADC0DE changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #8 from Waqar Ahmed ---
Thanks. In the attached file, I don't see anything that is taking too much
time. I can see that the resizing takes some time and it might consume 100% of
1 cpu for a short while but that is okay. Moreover, its all hap
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #7 from 0BADC0DE ---
Created attachment 173549
--> https://bugs.kde.org/attachment.cgi?id=173549&action=edit
gzipped perfparser file
This is the required perfparser file.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #6 from 0BADC0DE ---
Done. See attached file.
BTW, there has been a(n unwanted) reboot before this test and I cannot
reproduce the lagging problem anymore.
I can still see kate using close to 100% of the CPU while resizing the konsole
panlel
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #5 from Waqar Ahmed ---
Just run this on the command line directly instead (slightly modified):
perf record --call-graph dwarf,8192 --aio -z --sample-cpu --pid $(pidof kate)
It will create a perf.data file in the directory you are in. Open
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #4 from 0BADC0DE ---
[code]
$ perf record -o /home/user/perf.data --call-graph dwarf,8192 --aio -z
--sample-cpu --mmap-pages 16M --pid 7327
Permission error mapping pages.
Consider increasing /proc/sys/kernel/perf_event_mlock_kb,
or try agai
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #3 from Waqar Ahmed ---
> Maybe the problem is in how kate handle konsole during resizing.
Nothing special about that so its unlikely the problem is there.
Can you try to use perf or hotspot to profile Kate when it is slow?
- Download the
https://bugs.kde.org/show_bug.cgi?id=492896
--- Comment #2 from 0BADC0DE ---
Konsole works fine and I cannot reproduce the problem by resizing a konsole all
alone.
Maybe the problem is in how kate handle konsole during resizing.
--
You are receiving this mail because:
You are watching all bug c
https://bugs.kde.org/show_bug.cgi?id=492896
Waqar Ahmed changed:
What|Removed |Added
Assignee|kwrite-bugs-n...@kde.org|konsole-de...@kde.org
Product|kate
22 matches
Mail list logo
