Re: OpenOffice does not start when Firefox open
- From: Marty <net@xxxxxxxxxxxxxxxxxxx>
- Date: Tue, 15 Apr 2008 10:52:10 -0700
diespam wrote:
On Apr 15, 12:28 am, Marty <n...@xxxxxxxxxxxxxxxxxxx> wrote:
William L. Hartzell wrote:
Sir:
Marty wrote:
diespam wrote:
Notice that shared memory has been reduced to 79MB fro 138MB even
after OO is closed. (This value is stable even after many
openings and closings of OO so I don't think it's a memory leak)
It's an effect of address space fragmentation. The values reported are
likely the largest contiguous address ranges, even though multiple
ranges may exist.
Even still something has to remain in memory to fragment it, no? I lay
odds that the Innotek runtime is not uninstalling itself. Could not one
test this by measuring this on a slow machine to see if later load of OO
are faster? And even if this is true, what can we do about it?
I find it extremely unlikely, because once the application using the
runtime is gone, there's no reason to keep the library around. Usually
the WPS allocates something... a bitmap, pointer, or object handle...
which uses just a tiny sliver of the next available piece of shared
address space, and when the big users of the address range go away,
you're left with this small sliver dividing up the remaining space. I
often see the situation clear after a reset of the WPS. Also I've been
able to allocate a total amount of shared memory that is more than the
largest block reported, as long as I do it in separate chunks. Those
are two big clues that there is fragmentation.
Whatever is happening is really annoying. For example this morning I
opened up lots of Lucide instances and shared memory dropped to about
2.6MB and stayed there:
current free virtual address space in kB (private / shared):
128128 / 2688 below 512MB line, 1376256 / 913072 above 512MB line
And then I had to run a win32 app with PE and believe or not, shared
memory went down to 256K!!!!
current free virtual address space in kB (private / shared):
128128 / 256 below 512MB line, 1376256 / 910512 above 512MB line
Closing the win32 app brought it back to 2.6M.
At 2.6MB or less OO does not open at all (not even a beep). Is there a
way of unfragmenting shared memory with[out] a complete reboot?
Furthermore, is there a reason why developers don't use high mem
rather than shared mem?
It depends on who actually owns that shared memory. Get Theseus and look at the linear usage by process. If you see that PMShell owns some of those slivers in shared memory, you can often defragment it by resetting the WPS. XWorkplace has a tool to do this without rebooting, or you should be able to simply kill the second (higher PID) PMShell instance. It should restart automatically.
--
[Reverse the parts of the e-mail address to reply.]
.
- References:
- OpenOffice does not start when Firefox open
- From: Jеns Mаrtin Schlаttеr
- Re: OpenOffice does not start when Firefox open
- From: diespam
- Re: OpenOffice does not start when Firefox open
- From: Marty
- Re: OpenOffice does not start when Firefox open
- From: William L. Hartzell
- Re: OpenOffice does not start when Firefox open
- From: Marty
- Re: OpenOffice does not start when Firefox open
- From: diespam
- OpenOffice does not start when Firefox open
- Prev by Date: Re: OpenOffice does not start when Firefox open
- Next by Date: Re: OpenOffice does not start when Firefox open
- Previous by thread: Re: OpenOffice does not start when Firefox open
- Next by thread: Re: OpenOffice does not start when Firefox open
- Index(es):
Relevant Pages
|