Bug 1114480 - Memory usage seems to be quite big for nm-applet
Summary: Memory usage seems to be quite big for nm-applet
Keywords:
Status: CLOSED DUPLICATE of bug 1128766
Alias: None
Product: Fedora
Classification: Fedora
Component: network-manager-applet
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-30 07:47 UTC by Zdenek Kabelac
Modified: 2014-08-13 17:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-13 17:46:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
smaps of nm-applet (245.43 KB, text/plain)
2014-06-30 07:47 UTC, Zdenek Kabelac
no flags Details
Plain maps (48.22 KB, text/plain)
2014-06-30 07:47 UTC, Zdenek Kabelac
no flags Details

Description Zdenek Kabelac 2014-06-30 07:47:03 UTC
Created attachment 913278 [details]
smaps  of nm-applet

Description of problem:

I'm looking at top - and nm-applet seems to occupy front positions -
it takes  75MB or resident memory -  for an applet??

(I still remember days my whole running Linux with running web browser used to fit in 16MB....)

--
 1043  0.0  1.9 877452 75692 ?        Sl   čen29   0:03 nm-applet
--

Looking at smaps list - icon-theme.cache seems to be primary mem-eater here...
So feel free to reassign to other packages if nm-applet can't do better.

Attaching   smaps & maps of running  nm-applet process.


Version-Release number of selected component (if applicable):
network-manager-applet-0.9.9.0-12.git20140424.fc21.x86_64

How reproducible:


Steps to Reproduce:
1. ps aux | grep nm-applet
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Zdenek Kabelac 2014-06-30 07:47:37 UTC
Created attachment 913279 [details]
Plain maps

Comment 2 Zdenek Kabelac 2014-08-13 17:46:55 UTC

*** This bug has been marked as a duplicate of bug 1128766 ***


Note You need to log in before you can comment on or make changes to this bug.