[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Static Space filling up

To: luria@renoir.berkeley.edu
Subject: Static Space filling up
From: "David L. Andre" <DLA@diamond.s4cc.symbolics.com>
Date: Mon, 21 Dec 87 19:21 EST
Cc: slug@r20.utexas.edu
In-reply-to: <8712201938.AA19559@renoir.Berkeley.EDU>
Resent-date: Mon 21 Dec 87 22:07:45-CST
Resent-from: CMP.SLUG@r20.utexas.edu
Resent-message-id: <12360396847.36.CMP.SLUG@R20.UTEXAS.EDU>
Resent-to: SLUG:;

    Date: Sun, 20 Dec 87 11:38:07 PST
    From: luria@renoir.Berkeley.EDU (Marc Luria)

    The static space starts filling up. After cold boot, show gc status
    shows 11 million, but after a week or so, this gets up to 14.
    si:full-gc gets rid of a couple thousand.  I don't think it
    is due to this broadcast process bug.  I think it has something to do
    with recompiling a lot.  From what I understand the compiled-function-area
    is a static space.  Is there anyway to gc this area?
    Or is there another area which may be filling up?

The problem cannot be compiled-function-area, since that is not
reclaimed by full-gc.  Compiled functions can be reclaimed using the
:Optimize World command.  Why don't you use the ROOM function and find
out for yourself what areas are filling up?

References:
- Static Space filling up
  - From: Marc Luria <luria@renoir.berkeley.edu>

Prev by Date: Re: Mail, Domain Names, NSLUG, and 7.2 and 8.0, and the coming ice age in Hell.
Next by Date: Hardcopy with TCP/IP? Well almost.
Previous by thread: Static Space filling up
Next by thread: Re: Static Space filling up
Index(es):
- Date
- Thread