Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] KDE Plasma high memory consume
Date: Sun, 13 Dec 2020 23:09:56 +0100	[thread overview]
Message-ID: <20201213220956.9xNnhXDNq8_IZlzMKiD7DiPpfqC-Wo7k25fTexne0gI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25737@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]

Closed issue by gilbertoferreira on void-packages repository

https://github.com/void-linux/void-packages/issues/25737

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  *output of ``xuname`` (part of xtools)*
Void 5.8.16-050816-generic x86_64 AuthenticAMD uptodate rrrmFFF
* package:  
  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
plasma-desktop-5.20.0_1 
### Expected behavior
Consume less memory
### Actual behavior
plasma-shell and kwin_X11 are consume high memory compare to Kubuntu, for example.

### Steps to reproduce the behavior
Using KDE Plasma 
Hi there...
I am back again using VoidLinux.
Now I had noticed that KDE Plasma consume more RAM than Kubuntu, for instance.
Without nothing open (like chromium) I had saw at least 1.6GB and when checked about what process could consume such ram, I saw plasmashell and kwin_x11 which consume near 1GB.
My laptop is a Aspire A515-41G with 16GB of ram and SSD Samsung EVO 120GB.
Is there some issue with KDE 5.19 runnig on top of VoidLinux?

  parent reply	other threads:[~2020-12-13 22:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 11:50 [ISSUE] " gilbertoferreira
2020-10-21  8:22 ` toluschr
2020-10-22 16:38 ` b1scu1t
2020-10-22 16:40 ` b1scu1t
2020-10-22 16:45 ` gilbertoferreira
2020-10-22 20:49 ` gilbertoferreira
2020-10-23  9:48 ` pullmoll
2020-12-13 22:09 ` ericonr [this message]
2020-12-13 22:09 ` ericonr
2022-01-31 13:05 ` Vistaus
2022-01-31 13:05 ` Vistaus
2022-01-31 13:06 ` Vistaus
2022-01-31 13:16 ` Vistaus
2022-01-31 15:41 ` Vistaus
2022-01-31 18:12 ` Vistaus
2022-02-01 11:35 ` Vistaus
2022-02-01 13:08 ` Anachron
2022-02-01 13:47 ` Vistaus
2022-02-01 13:56 ` q66
2022-02-01 14:49 ` Anachron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201213220956.9xNnhXDNq8_IZlzMKiD7DiPpfqC-Wo7k25fTexne0gI@z \
    --to=ericonr@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).