linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John T. Williams" <jowillia@vt.edu>
To: Glynn Clements <glynn.clements@virgin.net>
Cc: jtwilliams@vt.edu,
	Wen Guangcheng <wen.guangcheng@cnt.sp.qnes.nec.co.jp>,
	linux-c-programming <linux-c-programming@vger.kernel.org>
Subject: Re: Newbie question on malloc()
Date: Wed, 02 Jun 2004 13:52:32 -0400	[thread overview]
Message-ID: <1086198752.29988.21.camel@localhost> (raw)
In-Reply-To: <16574.4399.288522.256729@cerise.nosuchdomain.co.uk>

What you never had win98 crash on you after running for an hour? ;) 

May statement is based on something I remember vaguely from my OS class
2 years ago, so I'm quite happy to believe I'm wrong.  I remember there
was some major issue with how win98 handled dynamic allocated memory,
but I can't exactly remember what.  

After googling a little I seems that win95 had some problems with
Garbage Collection not win98.
 

On Wed, 2004-06-02 at 13:41, Glynn Clements wrote:
> John T. Williams wrote:
> 
> > As I understand it, that is entirely up to the operation system.  Linux
> > and NT Kernel systems do reclaim unfreed memory, however I believe one
> > the major problems with Win98 was that it did not.
> > 
> > Anyone with more information feel free to correct me
> 
> I very much doubt that the above is accurate.
> 
> It may be that Win98 had some specific memory leaks, but any OS which,
> in the general case, failed to recover a process' memory upon
> termination would run out of memory very quickly.


  reply	other threads:[~2004-06-02 17:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-02 11:48 Newbie question on malloc() Wen Guangcheng
2004-06-02 17:08 ` John T. Williams
2004-06-02 17:41   ` Glynn Clements
2004-06-02 17:52     ` John T. Williams [this message]
2004-06-03  7:41       ` Glynn Clements
2004-06-03 11:32         ` Micha Feigin
2004-06-04  2:11           ` Glynn Clements
2004-06-04 12:31             ` Micha Feigin
2004-06-02 18:37     ` Jan-Benedict Glaw
2004-06-03  1:34       ` Micha Feigin
2004-06-03 19:42         ` Jan-Benedict Glaw
2004-06-03 23:44           ` Micha Feigin
2004-06-04  8:06             ` Jan-Benedict Glaw
2004-06-02 17:18 ` Glynn Clements
2004-06-03  1:28 ` Micha Feigin
2004-06-03  7:23   ` Luciano Moreira - igLnx
2004-06-03  7:59   ` Glynn Clements
2004-06-03 22:25     ` John T. Williams
2004-06-03 23:24       ` Paul Gimpelj
2004-06-04  0:14         ` John T. Williams
2004-06-04  2:35         ` Glynn Clements
2004-06-03 23:53       ` Glynn Clements

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=1086198752.29988.21.camel@localhost \
    --to=jowillia@vt.edu \
    --cc=glynn.clements@virgin.net \
    --cc=jtwilliams@vt.edu \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=wen.guangcheng@cnt.sp.qnes.nec.co.jp \
    /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;
as well as URLs for NNTP newsgroup(s).