https://bugs.kde.org/show_bug.cgi?id=509180

[email protected] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REPORTED                    |NEEDSINFO
                 CC|                            |[email protected]
         Resolution|---                         |WAITINGFORINFO

--- Comment #2 from [email protected] ---
(In reply to guimarcalsilva from comment #0)
> Created attachment 184761 [details]
> Ram usage after fresh boot
> 
> SUMMARY
> After a fresh boot, the DiscoverNotifier process usually uses over 340MBs of
> RAM. That's more than Plasmashell, which uses around 250MBs, or even
> Discover itself, that uses around 280MBs. I don't think it makes sense for
> it to use more RAM than the entirety of Plasmashell, so there must be a bug
> somewhere.
> 
> STEPS TO REPRODUCE
> 1. Start the computer normally
> 2. Check the Details tab on System Monitor and sort by RAM usage
> 
> OBSERVED RESULT
> The DiscoverNotifier process uses more RAM than any other process on the
> system, including Plasmashell, Kwin or Discover itself.
> 
> EXPECTED RESULT
> A more reasonable RAM usage considering its function.
> 
> SOFTWARE/OS VERSIONS
> Operating System: Fedora Linux 42
> KDE Plasma Version: 6.4.4
> KDE Frameworks Version: 6.17.0
> Qt Version: 6.9.1
> Kernel Version: 6.16.4-200.fc42.x86_64 (64-bit)
> Graphics Platform: Wayland
> Processors: 4 × Intel® Core™ i3-1005G1 CPU @ 1.20GHz
> Memory: 12 GiB of RAM (11.4 GiB usable)
> Graphics Processor: Intel® UHD Graphics
> Manufacturer: HP
> Product Name: HP 246 G7 Notebook PC

Hi,

I'm not sure this is actionable by KDE developers.

I'm not exactly sure what "too much RAM" entails, but please understand that
there is a constant effort to improve things behind the scenes.

Can you share why exactly you think that ~300MB of RAM usage is an issue on a
system that has 12GB of memory?

Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to