https://bugs.kde.org/show_bug.cgi?id=410129
Isaac Salgueiro changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=410129
--- Comment #11 from Vlad Zahorodnii ---
> Yep, but is not a bug this memory usage from kwrite?
Can be. Please report this bug to kwrite developers.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410129
--- Comment #10 from Isaac Salgueiro ---
Yep, but is not a bug this memory usage from kwrite?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410129
--- Comment #9 from Vlad Zahorodnii ---
Given that you don't have a swap partition or swapfile, I'm pretty sure that
kwin crashes because there's not enough free memory.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410129
--- Comment #8 from Isaac Salgueiro ---
Created attachment 122442
--> https://bugs.kde.org/attachment.cgi?id=122442&action=edit
Resources usage after killing kwrite
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410129
--- Comment #7 from Isaac Salgueiro ---
Created attachment 122441
--> https://bugs.kde.org/attachment.cgi?id=122441&action=edit
Resources usage
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410129
--- Comment #6 from Isaac Salgueiro ---
Created attachment 122440
--> https://bugs.kde.org/attachment.cgi?id=122440&action=edit
Resources usage
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410129
--- Comment #5 from Isaac Salgueiro ---
OK, after opening that 144MB file in kwrite and hitting 'Ctrl End' one of my
CPU cores spiked to 100% usage and memory usage started to raise until I killed
kwrite. I'm attaching some KSysGuard screenshots.
This
https://bugs.kde.org/show_bug.cgi?id=410129
--- Comment #4 from Vlad Zahorodnii ---
Nah, don't worry about h0. It's irrelevant in our case.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410129
--- Comment #3 from Isaac Salgueiro ---
Don't think so, but I'll try to reproduce this while keeping an eye on free
memory.
Anyway, does that h0 param means that kwrite needs more than 2GB of memory for
reading a 144MB file?
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=410129
--- Comment #2 from Vlad Zahorodnii ---
#6 QHashNode >::same_key (key0=...,
h0=2494525897, this=0x50) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:158
this looks a bit suspicious
could it be that you ran out of memory?
--
You are receiving t
https://bugs.kde.org/show_bug.cgi?id=410129
--- Comment #1 from Nate Graham ---
Crashing in KPackage::PackageLoader::listPackages(), called from
KWin::ScriptedEffectLoader::findAllEffects()
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410129
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail beca
13 matches
Mail list logo
