*BSD News Article 18747


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!decwrl!usenet.coe.montana.edu!bsd.coe.montana.edu!nate
From: nate@bsd.coe.montana.edu (Nate Williams)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: "persistent object not clean"
Date: 22 Jul 1993 21:10:33 GMT
Organization: Montana State University
Lines: 27
Message-ID: <22mvo9$7op@pdq.coe.montana.edu>
References: <1993Jul22.164535.20962@qualcomm.com>
NNTP-Posting-Host: bsd.coe.montana.edu

In article <1993Jul22.164535.20962@qualcomm.com> karn@servo.qualcomm.com writes:
>Whenever I exit GNU Emacs version 19.16 (a very large program with the
>sticky bit set) I get logged messages of the form
>
>Jul 22 09:21:47 unix /386bsd: vm_object_dealloc: persistent object fe3ec600 isn't clean
>
>Nothing bad seems to happen, but I was wondering if this might
>indicate some more latent problem, like a memory leak...?

I *think* (some VM guru interject here) that is might be the Copy On
Write problem recently fixed in FreeBSD (aka interim aka 0.1.5).

A good way to check this is to make a fresh copy, cksum the file, and
the run it.  If it changes, then you are experiencing the COW problem.

The fix will be in the release, which went into ALPHA test earlier this
week.


Nate


-- 
nate@bsd.coe.montana.edu     |  In the middle of it ........ again. 
nate@cs.montana.edu          |  Running/supporting one of many freely available 
work #: (406) 994-4836       |  Operating Systems for [34]86 machines.
home #: (406) 586-0579       |  (based on Net/2, name changes all the time :-)