mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: "M. Soltysiak" <msoltysiak@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux BUG: Memory Leak
Date: Wed, 12 Mar 2003 08:22:55 +0100	[thread overview]
Message-ID: <5.2.0.9.2.20030312080410.00c94ea8@pop.gmx.net> (raw)
In-Reply-To: <F44Bre5NuYqYYDleNlx00025ecc@hotmail.com>

At 06:49 AM 3/12/2003 +0000, M. Soltysiak wrote:
>I sent this here because i don't know which author screwed up.

I note that diplomacy isn't your strong suite.

>System specs:
>1 GBytes RAM
>duel CPU system; 1 Ghz each.
>IDE disk system, 133 Mhz bus speed, DMA.
>USB mouse.
>PS/2 Keyboard.
>Creative Labs emu10k1-based sound card.  (LIVE!)
>Asus Motherboard.

Which kernel version, and how much swap (0?).

>Problem:
>
>When I boot the system, run X11 with KDE--totalling 100 M at most--things 
>are fine.
>
>When I run applications that use quite a bit of memory -- those that use 
>500 Megs of RAM -- Linux keeps on allocating memory until it's full.  When 
>full, system acts dead, as expected from the bad VM design.  But why does 
>the system allocate memory until the RAM is full?  User applications are 
>NOT leaking memory.

What are you basing these assertions upon?

>Example: Installing Unreal Tournament 2003 -- from the CD drive, IDE -- 
>for example, playing mp3 files and browsing the web with Mozilla, and the 
>system will eventually allocate memory until the system freezes.  All of 
>RAM is allocated, and the system is frozen.

Please post a detailed report including kernel version, process sizes and 
/proc/slabinfo just prior to live-lock.  This report is useless.  (not to 
mention arrogant)

         -Mike 


  parent reply	other threads:[~2003-03-12  7:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12  6:49 M. Soltysiak
2003-03-12  7:19 ` David Shirley
2003-03-12 10:04   ` Maciej Soltysiak
2003-03-12 18:38   ` James Stevenson
2003-03-12 19:25     ` Elladan
2003-03-12  7:22 ` Mike Galbraith [this message]
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
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=5.2.0.9.2.20030312080410.00c94ea8@pop.gmx.net \
    --to=efault@gmx.de \
    --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

all inboxes | Powered by JetHome®