From: James Stevenson <james@stev.org>
To: David Shirley <dave@cs.curtin.edu.au>
Cc: "M. Soltysiak" <msoltysiak@hotmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux BUG: Memory Leak
Date: 12 Mar 2003 18:38:57 +0000 [thread overview]
Message-ID: <1047494337.2064.1.camel@god.stev.org> (raw)
In-Reply-To: <041f01c2e86a$872520d0$64070786@synack>
On Wed, 2003-03-12 at 07:19, David Shirley wrote:
> Err for starters you should include kernel version and OS versions etc.
>
> Also how do you expect any computer to work once it has run out of
> memory? Do you have swap partition? I suspect not, or a small one in
> any case!
>
> Some of the applications you mention are notorios for memory leaks
> themselves. ie UT!
iirc UT will only run with openGL under X last time i looked about 3
months ago the only card that was fully supporting this was the nvidia
Geforce series with closed source drivers.
Tainted kernel :/
James
next prev parent reply other threads:[~2003-03-12 18:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 6:49 Linux BUG: Memory Leak M. Soltysiak
2003-03-12 7:19 ` David Shirley
2003-03-12 10:04 ` Maciej Soltysiak
2003-03-12 18:38 ` James Stevenson [this message]
2003-03-12 19:25 ` Elladan
2003-03-12 7:22 ` Mike Galbraith
2003-03-12 7:30 ` William Stearns
2003-03-13 7:13 ` William Stearns
2003-03-13 9:13 ` pd dd
2003-03-13 14:26 ` James Stevenson
2003-03-13 15:45 ` Alan Cox
2003-03-13 15:05 ` Tomas Szepe
2003-03-13 15:33 ` Damian Kołkowski
2003-03-13 16:29 ` venom
2003-03-13 14:26 ` James Stevenson
2003-03-13 14:42 ` Richard B. Johnson
2003-03-13 15:10 ` Mark Mielke
2003-03-13 15:13 ` Richard B. Johnson
2003-03-13 18:54 ` Alan Cox
2003-03-13 15:06 ` Martin Schlemmer
2003-03-13 14:27 ` James Stevenson
2003-03-13 15:43 ` Alan Cox
2003-03-12 16:49 ` Disconnect
-- strict thread matches above, loose matches on Subject: below --
2003-03-12 19:24 Felipe Alfaro Solana
2003-03-12 20:58 ` James Stevenson
2003-03-12 22:23 Felipe Alfaro Solana
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1047494337.2064.1.camel@god.stev.org \
--to=james@stev.org \
--cc=dave@cs.curtin.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=msoltysiak@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox