Results 1 to 8 of 8

Thread: looks like Xorg leak

  1. #1

    Default looks like Xorg leak

    Hi ppl!
    Is it normal:
    cat /proc/`pidof Xorg`/smaps | grep "drm mm" | wc -l
    587
    and xorg mem use steady increasing...


    xorg-x11-libICE-7.6-21.1.x86_64
    xorg-x11-libX11-32bit-7.6-47.2.x86_64
    xorg-x11-libXp-7.6-8.1.x86_64
    xorg-x11-7.6-146.1.x86_64
    xorg-x11-libxcb-7.6_1.7-19.1.x86_64
    xorg-x11-libXt-7.6_1.0.9-25.1.x86_64
    xorg-x11-libXprintUtil-7.6-8.1.x86_64
    xorg-x11-libXau-7.6_1.0.6-13.1.x86_64
    xorg-x11-driver-video-radeonhd-1.3.0_20100325_f6c9991-34.2.x86_64
    xorg-x11-libX11-ccache-7.6-8.1.x86_64
    xorg-x11-libSM-32bit-7.6-20.1.x86_64
    xorg-x11-libxkbfile-32bit-7.6-12.1.x86_64
    xorg-x11-libXmu-7.6-20.1.x86_64
    xorg-x11-libXrender-7.6_0.9.6-13.1.x86_64
    xorg-x11-libXv-7.6-13.1.x86_64
    xorg-x11-libXpm-32bit-7.6-13.1.x86_64
    xorg-x11-libfontenc-7.6-13.1.x86_64
    xorg-x11-libs-32bit-7.6-60.1.x86_64
    xorg-x11-libXfixes-32bit-7.6_4.0.5-13.1.x86_64
    xorg-x11-driver-video-7.6-174.1.x86_64
    xorg-x11-fonts-core-7.5-1.4.noarch
    xorg-x11-fonts-7.5-1.4.noarch
    xorg-x11-libSM-7.6-20.1.x86_64
    xorg-x11-libxkbfile-7.6-12.1.x86_64
    xorg-x11-libs-7.6-60.1.x86_64
    xorg-x11-libXfixes-7.6_4.0.5-13.1.x86_64
    xorg-x11-libfontenc-32bit-7.6-13.1.x86_64
    xorg-x11-libXdmcp-7.6-20.1.x86_64
    xorg-x11-libICE-32bit-7.6-21.1.x86_64
    xorg-x11-libXext-32bit-7.6_1.2.0-15.1.x86_64
    xorg-x11-libXp-32bit-7.6-8.1.x86_64
    xorg-x11-xauth-7.6-146.1.x86_64
    xorg-x11-driver-input-7.6-94.1.x86_64
    xorg-x11-libxcb-32bit-7.6_1.7-19.1.x86_64
    xorg-x11-Xvnc-7.5_1.8.0-10.3.1.x86_64
    xorg-x11-libXau-32bit-7.6_1.0.6-11.1.x86_64
    xorg-x11-libXt-32bit-7.6_1.0.9-25.1.x86_64
    xorg-x11-libXext-7.6_1.2.0-15.1.x86_64
    xorg-x11-libXprintUtil-32bit-7.6-8.1.x86_64
    xorg-x11-libXpm-7.6-13.1.x86_64
    xorg-x11-libX11-7.6-47.2.x86_64
    xorg-x11-libXmu-32bit-7.6-20.1.x86_64
    xorg-x11-libXrender-32bit-7.6_0.9.6-13.1.x86_64
    xorg-x11-server-7.6_1.9.3-121.1.x86_64

  2. #2
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: looks like Xorg leak

    On 02/15/2011 01:06 PM, seleko wrote:
    >
    > and xorg mem use steady increasing...


    is your problem xorg mem not staying constant, or is it with how the
    memory is being used?

    it hard to give you an answer until you give us some more information,
    like

    -over what period of time have you seen xorg use how much more memory?

    -during that time xorg rose from XX% to YY% each hour/day/month, what?

    -and, during those times you saw the memory use increase, were any new
    applications opened or were there otherwise other demands in xorg,
    like loading any of the new libraries into memory (like those you listed)?

    -your operating system and version?

    -you desktop environment and version?

    -the status of your system (fully updated)?

    -what version kernel and X?

    -are you experiencing any other problems?

    --
    DenverD
    CAVEAT: http://is.gd/bpoMD
    [NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
    173.14.28 3D, Athlon 64 3000+]
    "It is far easier to read, understand and follow the instructions than
    to undo the problems caused by not." DD 23 Jan 11

  3. #3

    Default Re: looks like Xorg leak

    DenverD wrote:
    > On 02/15/2011 01:06 PM, seleko wrote:
    >> and xorg mem use steady increasing...

    >
    > is your problem xorg mem not staying constant, or is it with how the
    > memory is being used?
    >
    > it hard to give you an answer until you give us some more information,
    > like


    +1

    > -and, during those times you saw the memory use increase, were any new
    > applications opened or were there otherwise other demands in xorg,
    > like loading any of the new libraries into memory (like those you listed)?


    Or even, were any applications that continually increase resource usage,
    such as Firefox, running during this time?

    X increases memory usage when clients create new resources on the server
    (pixmaps etc) so you first need to eliminate that as a cause.

  4. #4

    Default Re: looks like Xorg leak

    It doesnt stay constant, day by day usage grows by around 2Mb.
    I have very limited number of application.
    I noted the most visible growth after use of Okular for pdf viewing.
    Env:
    libqt4-4.7.1-139.1.x86_64
    kdebase4-runtime-4.5.4-2.4.x86_64
    with all deps.
    But this started to happen long before. ~ KDE 4.4 times.

    What do you mean fully updated? I posted Xorg related packages.
    2.6.34.7-0.4-desktop #1 SMP PREEMPT 2010-10-07 19:07:51 +0200 x86_64 x86_64 x86_64 GNU/Linux

    and yes: lack of money

    PS.
    I greped for "drm mm object (deleted)".

  5. #5
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: looks like Xorg leak

    On 02/15/2011 03:06 PM, seleko wrote:
    >
    > It doesnt stay constant, day by day usage grows by around 2Mb.


    not much...i assume you are you saying that this growth goes for days
    during which you neither boot nor suspended/hibernate the
    machine...correct?

    > I have very limited number of application.


    might you on any particular day open any application that you didn't
    on the day before?

    once you open an app, do you leave it open? or close it prior to
    opening another?

    > I noted the most visible growth after use of Okular for pdf viewing.
    > Env:


    do you realize that when you open a PDF that X org _must_ have
    sufficient RAM space to contain _that_ PDF?

    and, do you understand the Linux method of using memory? that is,
    unlike some other systems (cought: windows) which strive to release
    memory back to the system as quickly as possible, linux does just the
    opposite....

    that is, taking the position that empty RAM is wasted RAM linux tried
    to keep as much in memory as possible *because* there is a chance that
    the stuff in RAM at this instant might be needed again in the next
    second....and, if it is, it is so very much faster to just fetch it in
    RAM again (rather than flush, go to the disk and fetch and load it
    into RAM again)..

    so, i do not know how what tool you are looking at to track the amount
    of RAM being used by X, but i guess you know your total use of RAM is
    probably sitting around something over 98% most of the time....and, so
    it doesn't really matter if 2mb is tagged against X today, or not..

    > libqt4-4.7.1-139.1.x86_64
    > kdebase4-runtime-4.5.4-2.4.x86_64
    > with all deps.
    > But this started to happen long before. ~ KDE 4.4 times.


    i guess all of that is to answer my questions system/DE, you would
    have made it easier on me had you simply said 11.3/64 and KDE4.4.4

    > What do you mean fully updated?


    i mean do run the updater either by using zypper, YaST or YOU..
    (the reason i ask is because sometime folks complain about problems
    and after we ask questions we learn all that is needed is to run the
    updater which applies the patched needed to take away the problem.


    > I posted Xorg related packages.


    you expect me to know numbers in the names of the Xorg packages for a
    how many different systems currently supported?


    > and yes: lack of money



    ok, how much should i send you :-)

    >
    > PS.
    > I greped for "drm mm object (deleted)".


    and?

    --
    DenverD
    CAVEAT: http://is.gd/bpoMD
    [NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
    173.14.28 3D, Athlon 64 3000+]
    "It is far easier to read, understand and follow the instructions than
    to undo the problems caused by not." DD 23 Jan 11

  6. #6

    Default Re: looks like Xorg leak

    I appreciate your efforts to help me.

    About updated system...
    As I understand concept we cant talk about "my system fully updated"... I just can you level of updates/version that installed on MY system.
    I dont install ALL updated that Novell recommends via its updater. I choose what to install myself.

    qt -- 4.7.1
    KDE -- Platform Version 4.5.4 (KDE 4.5.4) "release 9"
    Xorg -- 7.6
    x11 server -- 1.9
    libdrm-2.4.23-49.1.x86_64
    video -- i915

    I fully understand how X caches bitmaps, and how it frees memory when they are not required.
    But on my understanding Xorg just doesnt free memory allocated, when I use something graphics-intensive.

    Try to run Okular, view 5 PDF at least 10 pages with pictures, and you see whats going on.
    I NEVER seen Xorg memory usage shrinks. NEVER. Nither top nor System activity in KDE.

    And I suspect that this memory becomes blocked in that "drm mm object (deleted)" chunks.
    There's no way to tell x-server to release cached bitmaps.

    cheers.

  7. #7
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: looks like Xorg leak

    On 02/16/2011 08:06 AM, seleko wrote:

    > And I suspect that this memory becomes blocked in that "drm mm object
    > (deleted)" chunks.
    > There's no way to tell x-server to release cached bitmaps.


    if you have found an Xorg bug **please** report it, here:
    http://en.opensuse.org/Submitting_Bug_Reports

    mentioning it here will _not_ get the information need to either the
    openSUSE nor Xorg developers--it _must_ go into bugzilla..

    --
    DenverD
    CAVEAT: http://is.gd/bpoMD
    [NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
    173.14.28 3D, Athlon 64 3000+]
    "It is far easier to read, understand and follow the instructions than
    to undo the problems caused by not." DD 23 Jan 11

  8. #8

    Default Re: looks like Xorg leak

    I was not sure its bug so decided to discuss here...
    As I see here not much interest.

    I will wait till 11.4 to report bug, if it appear again.
    thanks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •