> > 3)[BUG] This may be related to the error above, but in certain circumstances,
> > when you *keep doing* mergemem on two apps, it just keeps finding
> > pages to share, although in reality there aren't anymore after the first
> > time. As a nasty side effect, though, the RSS of the second instance
> > keeps decreasing until it wraps and becomes really high again :).
> > Luckily, this doesn't crash neither kernel nor application,
> > but it sure isn't healthy.
> >
> > Try this:
> >
> > Create two rxvt's (or xterm) and find their pid. Leave one of them alone,
> > and in the other one, start the following:
> >
> > $ while true; do mergemem -p pid1 -p pid2; done
> >
> > This will cause this instance of rxvt to change its contents a lot.
> > The mergemem output shows it keeps on finding 376 KB to share every time.
> > Running top or ps -aux tells a different tale. Notice what happens to the
> > RSS of the other instance...
>
> Hmm, the strange thing is, that this only happens to rxvts, kvts, xterms
> etc...
> No idea jet...
Hmm, rxvts and similar X stuff will probably use sysV shared
memory. How do _YOU_ handle sysV shared memory?
(just an idea)
Pavel
-- I'm really pavel@atrey.karlin.mff.cuni.cz. Pavel Look at http://atrey.karlin.mff.cuni.cz/~pavel/ ;-).- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu