Re: Memory leak in Office 2008?
- From: "Norman R. Nager, Ph.D." <nnager@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 24 Jan 2008 20:42:04 -0800
On 1/24/08 8:04 PM, in article C3BFAAFC.EC49%john@xxxxxxxxxxx, "John McGhie"
<john@xxxxxxxxxxx> wrote:
Hi Norman:
On 25/01/08 10:35 AM, in article
C3BE60BA.1A08%nnager@xxxxxxxxxxxxxxxxxxxxxxxxxx, "Norman R. Nager, Ph.D."
<nnager@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I wonder whether there might be a *second* memory leak? I don't use the
Progress Window and I just checked and re-closed it. Could there be
another Office 2008 process that takes hours and hours to develop a memory
leak?
Of course, there "could", but I don't think there "is". However, I am on
Intel, so your case will be different.
Yes it could. And remember that uninstalling and reinstalling ANY Mac
application will rarely do anything. Unlike windows, Mac programs do not
seem to get corrupted.
Does that apply to the applications' processes that operate in the
background?
Bob was trying to save himself some typing :-)
Re-install never fixes anything on a Mac. There are two reasons for this:
1) The files that corrupt are "generated" files that are not on the
installation media. They are generated when the application first runs. So
if you re-install, you simply overwrite existing files that had nothing
wrong with them.
But when the application re-starts, it looks, sees that the generated files
are already there, and "uses" them, instantly restoring the problem :-)
2) If you use the Installer, the installer checks to see if each file it is
about to write exists. If it does, the Installer checks the date to see if
the file on your disk is newer than the file on the CD. If it is, the
installer skips writing that file.
That prevents the re-installation overwriting patched or upgraded
components.
It also prevents it fixing any problems if they exist :-)
On Windows, the damage tends to happen in the Registry (Windows' version of
the Preferences) and the Windows installer is a bit smarter than the Mac
one: it not only checks that the registry entries are present, it checks
that they make sense. And re-writes them if they don't. So a re-install on
Windows can fix a wide range of problems it can't on the Mac.
Aha! Thanks very much, John, for saving me a lot of wasted effort and for
an explanation that makes this retired emeritus professor of communications
envious of your capacity for such clear, concise and interpretive writing.
Now: Going back to your original problem, you said the KERNEL task was
growing. So we must assume that it is a component of he kernel that is in
trouble.
It could be ANYTHING that is in the kernel, or is running as a child of the
kernel. I don't know enough about Unix to work out what it's likely to be.
But I would be tempted to perform an Archive and Install of OS X round about
now.
I did an Archive-and-Install two days ago. How likely do you think it might
be that my selection of the check-box for importing settings also imported
the corruption as well?
Your disk space is being eaten by the ever-growing paging file, which inYou've been of great help, John. Thanks for the education and your
turn is being inflated by the ever-increasing demand for memory.
So the system is pretty unusable, and it's time for serious intervention.
Sorry to be not much help...
contributions to the newsgroup.
Respectfully, Norm
Ah, there's the rub!, to plagiarize a phrase from Shakespeare. I agree with
you but I can't figure out how to determine which file or couple need to be
deleted.
And, I've been following this thread, but am confused about the memory leak.
Are you seeing RAM getting consumed? . . .
My second set of advice is
to put Activity monitor away, and don't worry about things until there is a
definite problem.
I have had a Force Quit Applications dialogue appear a number of times over
the last couple weeks that says not enough memory. That's when I started
watching Activity Monitor and noticing the "free" and "used" memory meters
moving in the wrong direction up to the point of 30 to 70 MB of memory left
and then not enough to shutdown except with Mac tower power button. On a
couple occasions, I've left the machine alone running a diagnostics or
cloning operation with more than 1 GB "free" showing in the Activity Monitor
to return an hour or couple later to find that the machine had apparently
drained the last of the memory and turned itself off. There is no memory
leak whatsoever when I operate in shift-down startup mode.
In an earlier post I thought you
mentioned that disk space was getting consumed.
That, TOO. I just noticed in the last couple days Get Info on the boot
volume is showing hundreds of thousands more "used" bytes each day. (Its
capacity is 39.88 GB of which 12.25 GB is used.)
I just checked and a Retrospect Duplicate clone on an external hard drive I
made 2 days ago, shows 11.99 GB used. A clone made a day before that shows
11.002 GB used. Something is doing a lot of writing to the boot volume on
my internal hard drive. I wish I knew what. It is NOT documents because
all of them, including the MUD folder, are aliased from a 2nd/OS-free volume
on my hard drive.
I'll be patient, but it's a pain to have to re-start in normal startup mode
or operate without the convenience of some extensions, as I'm now doing, in
shift-down startup mode.
Respectfully, Norm
.
- Follow-Ups:
- Re: Memory leak in Office 2008?
- From: John McGhie
- Re: Memory leak in Office 2008?
- References:
- Re: Memory leak in Office 2008?
- From: John McGhie
- Re: Memory leak in Office 2008?
- From: Norman R. Nager, Ph.D.
- Re: Memory leak in Office 2008?
- From: Bob Greenblatt
- Re: Memory leak in Office 2008?
- From: Norman R. Nager, Ph.D.
- Re: Memory leak in Office 2008?
- From: John McGhie
- Re: Memory leak in Office 2008?
- Prev by Date: Re: No copy-paste between Word 2008 and ChemDraw
- Next by Date: Re: Office 2008 won't launch!!! :-(
- Previous by thread: Re: Memory leak in Office 2008?
- Next by thread: Re: Memory leak in Office 2008?
- Index(es):
Relevant Pages
|
