Paul B. wrote:
Mike Fedyk wrote:
Paul B. wrote:
Paul B. wrote:
I'm not sure what's supposed to be achieved by running Quickstart in the background. When I ran it it took up some 48K of memory, as I recall, and loading documents was none too fast.
I just noticed that, not using Quickstart, I can keep an instance of swriter open (it's listed under Task Manager as Soffice.exe) and only incur a 1.4K memory hit. And opening documents is instantaneous.
So I fail to see the purpose of Quickstart, especially as it has no context menu functions.
Paul
I see now that soffice.bin also runs with a blank instance of swriter, and adds about 40K to the memory load. Not sure if that's new or I overlooked it originally. AIR, that's still less than QS was costing me, however.
With 1.1 QS runs soffice.exe. With 1.9 it starts soffice.bin. QS just keeps OOo open and adds an icon to the tray. If you had OOo using a lot of memory, it was not because of QS.
Also, it is not using 40K of memory, it is using 40000K (if you look in task manager), which roughly translates to 40MB.
Mike
You're quite right about the decimal point; thanks.
It was indeed soffice.bin that was costing 40M of memory. Oddly, later on, with no changes and no work having been done in OOo, soffice.bin was back down to, IIRC, 1.6M (again, with QS closed and a blank instance of OOo open).
That's windows asking the program to swap out when you minimize it. Be sure to look at the "VM Size" column (add it to your view in View | Columns if you don't see it). Have you tried using QS in a recent build?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
