Summary: | System completly hang after opening a 144MB file with kwrite | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Isaac <isalgueiro> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | nate |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.16.3 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Resources usage
Resources usage Resources usage after killing kwrite |
Description
Isaac
2019-07-23 07:45:12 UTC
Crashing in KPackage::PackageLoader::listPackages(), called from KWin::ScriptedEffectLoader::findAllEffects() #6 QHashNode<QString, QList<KPluginMetaData> >::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? 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? Nah, don't worry about h0. It's irrelevant in our case. 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 test was made in a fully updated Neon install with kwrite 19.08.0 Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.3 Kernel Version: 5.0.0-25-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i3-7100U CPU @ 2.40GHz Memory: 15,6 GiB Created attachment 122440 [details]
Resources usage
Created attachment 122441 [details]
Resources usage
Created attachment 122442 [details]
Resources usage after killing kwrite
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. Yep, but is not a bug this memory usage from kwrite? > Yep, but is not a bug this memory usage from kwrite?
Can be. Please report this bug to kwrite developers.
OK, I'm opening a new bug to kate component. Thanks! |