Why does the Xorg server reset the output when last client disconnects?

[Joel Feiner]

Memory leaks are NOT a thing of the past.  I have a serious one right now,
where using Firefox and visiting pages with a lot of images causes the X
server to leak a huge amount of heap memory, to the point that it uses up
approximately 800 MB of my 1 gig of RAM and I have to restart the X server
frequently.  There are other leaks that are slower, but they're still
there.

On 5/2/07, Barry Scott <barry.scott at onelan.co.uk> wrote:
>
> Stuart Kreitman wrote:
> > Barry Scott wrote:
> >> Michel Dänzer wrote:
> >>> On Wed, 2007-05-02 at 10:58 +0100, Barry Scott wrote:
> >>>
> >>>> I'm wondering if it is reasonable to prevent the server from doing
> >>>> the reset
> >>>> when the last client disconnects?
> >>>>
> >>>
> >>> Try it for yourself:
> >>>
> >>> Xorg -noreset
> >>>
> >>>
> >> Thanks I've added to my X service startup.
> >>
> >> But I'd still like to know why the reset is there at all?
> >>
> > 21 years ago, it was effective in covering up memory leaks and other
> > crud giving the
> > appearance of great uptime.
> >
> > Stuart K
> >
> I suspected something like this. I'll sleep happy that -noreset is safe
> to use.
>
> Is there any reason why Xorg should not have noreset as the default now
> that
> the memory leaks etc are a thing of the past?
>
> Barry
>
> _______________________________________________
> xorg mailing list
> xorg at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xorg
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg/attachments/20070502/cf744ee4/attachment.html>