Re: Memory leak in nxagent, with patch

> I forgot to mention, I use nxclient 1.5.0-141, nxagent
Version 1.5.0 and 
> freenx 0.5 ... I haven't tried with different versions
of the client and
> the 
> server and I didn't try the patch yet ...

Okay. I dunno if its already present in 15..0, but it might
be as at that time the lazy image encoding was started.

> What is the meaning of 
> this "backing store" option, what does it
change and how it affects the 
> problem with memory leak?

Okay, let me explain that.

An Xserver has a backingstore to cache images in itself. (as
far as I remember)

Disabling the backingstore might hurt performance a bit, but
as the proxies already do memory limited caching of
compressed images that backingstore should not be needed
...

Just try it the option flag to the original X server is
-bs.

cu

Fabian
____________________________________________________________
____
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX
Wiki/FAQ:
  http://openfacts.berlios.de/index-en.phtml?title=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

I tried the backing store option on my client side X server
but with no effect 
at all ... the simple test I run shows that the memory fills
again ... I open 
a pdf viewer (kpdf) and began to scroll a long pdf document
... with every 
page displayed on the screen the memory of the thin client
(Xorg binary) 
becomes bigger ... when I scroll back, the pages are open
very fast which 
means that they are cached in memory ... when I close the
pdf viewer the 
memory is released back to initial state ... the question is
why X server 
keeps this pixmaps (from the pdf document) in its memory ...
I tried this on 
a normal debian based workstation with local X (no freenx
and nomachine) and 
the memory did not moved a bit! I guess that this memory
management has 
nothing to do with the backing store option ... and I wonder
why the X org 
binary uses so much memory instead of the nxclient/nxssh
which seem more 
logical ... 

> > I forgot to mention, I use nxclient 1.5.0-141,
nxagent Version 1.5.0 and
> > freenx 0.5 ... I haven't tried with different
versions of the client and
> > the
> > server and I didn't try the patch yet ...
>
> Okay. I dunno if its already present in 15..0, but it
might be as at that
> time the lazy image encoding was started.
>
> > What is the meaning of
> > this "backing store" option, what does
it change and how it affects the
> > problem with memory leak?
>
> Okay, let me explain that.
>
> An Xserver has a backingstore to cache images in
itself. (as far as I
> remember)
>
> Disabling the backingstore might hurt performance a
bit, but as the proxies
> already do memory limited caching of compressed images
that backingstore
> should not be needed ...
>
> Just try it the option flag to the original X server is
-bs.
>
> cu
>
> Fabian
>
____________________________________________________________
____
>      Were you helped on this list with your FreeNX
problem?
>     Then please write up the solution in the FreeNX
Wiki/FAQ:
>   http://openfacts.berlios.de/index-en.phtml?title=Free
NX_FAQ
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com
/kb/
>
>
____________________________________________________________
____
>        FreeNX-kNX mailing list --- FreeNX-kNXkde.org
>       http
s://mail.kde.org/mailman/listinfo/freenx-knx
>
____________________________________________________________
____
____________________________________________________________
____
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX
Wiki/FAQ:
  http://openfacts.berlios.de/index-en.phtml?title=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

> I tried the backing store option on my client side X
server but with no
> effect 
> at all ... the simple test I run shows that the memory
fills again ... I
> open 
> a pdf viewer (kpdf) and began to scroll a long pdf
document ... with every
> page displayed on the screen the memory of the thin
client (Xorg binary) 
> becomes bigger ... when I scroll back, the pages are
open very fast which 
> means that they are cached in memory ... when I close
the pdf viewer the 
> memory is released back to initial state ... the
question is why X server 
> keeps this pixmaps (from the pdf document) in its
memory ... I tried this
> on 
> a normal debian based workstation with local X (no
freenx and nomachine)
> and 
> the memory did not moved a bit!

Because it was using SHM, shared pixmaps. So the Xserver is
pointed directly to the kpdf pixmamps ...

You have to at least try it over the network, but I must
admit that I'm not that familiar with that parts of X11,
yet.

cu

Fabian
____________________________________________________________
____
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX
Wiki/FAQ:
  http://openfacts.berlios.de/index-en.phtml?title=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____