Dale:
I really don't know what's causing the crash/lockup problem (memory or disk activity) with OOO3. I can say that the frequent program crashes come without any warning; that is, OOO seems generally to be doing fine, no significant slowdown, followed by a total crash, the OSX message about an application crash, and the aforementioned inability to actually close soffice. I often have mulitple programs running, including Thunderbird, Firefox, and some of the OSX apps (addressbook, iCal). Like I said, I haven't investigated the issue because I'm happy using the NeoOffice implementation of the OOO software. You're right, something has clearly gone wrong. The behavior on the Mac OOO version is way too reminicsent of M$ software behavior (locking up, slowing down, inexplicable crashes) for me to mess with it. That's one of the reasons I switched to a Mac to begin with. The need to use the power button to force a shutdown is especially disturbing. I highly recommend NeoOffice for people using Macs (it's free, donations appreciated) and it looks like you'd expect OOO to look and runs without all these issues.

-Michael

On 12/7/08 [EMAIL PROTECTED] wrote:
I'm running OpenOffice 3.0.0 (build 9358) under OS X 10.4.11 on an old PowerBook (867 MHz/ 640 MB). Although I find the program sluggish at times, I haven't had anything like the problems discussed below. I do find it necessary to shut down Oo by hand when shutting down the computer. A minor "tune-up" (running the daily, weekly, and monthly maintenance programs and DiskWarrior) seemed to help quite a bit. I also try to keep the number of programs that are active lower when Oo is running, and occasionally stop and restart the browser. Safari in particular seems to slow down over time, and shutting it down and restarting it seems a good idea, Something has clearly gone wrong, as the machine described below has a lot more horsepower than mine. Is the probram choking on memorym CPU or disk activity? (Have a peek with Activity Monitor).
Dale
On Dec 7, 2008, at 1:02, Michael Reich wrote:


I also have encountered similar problems with 3.0 on my MacBook running OSX 10.4.11. I've used NeoOffice for a couple years instead of the X11 version of OOO, and I tried OOO Ver.3, but have pretty much abandoned it. I experienced fairly frequent crashes in addition to the symptoms you described. The worst part of the crashes is that OOO never completely shuts down, even after attempting to Force Quit using Finder. It still remains in the Dock and the only way I have found to get rid of it is to reboot. Even rebooting is a problem, because Finder still can't gracefully shut down soffice. The only solution I've found is to hit the power button force shutdown. I've never had such severe issues with NeoOffice, so I see no reason (nor do I have the time or energy) to struggle with OOO Ver. 3.

On 12/6/08 [EMAIL PROTECTED] wrote:
Subject:
Problems running 3.0.0 on Mac
From:
"Maggie Koerth" <[EMAIL PROTECTED]>
Date:
Sat, 6 Dec 2008 13:32:31 -0600

To:
users@openoffice.org


I recently replaced the X11 Mac version with 3.0.0 and it's been horrid for
me since day 1. The program operates like molasses half the time, like
delayed typing and having to wait for things to execute for a few seconds
after I make the command. Then there's the freezing. The thing has frozen on me two or three times this month alone. It's really frustrating and I don't know any other Mac users who are having these kind of problems with 3.0.0.

Has this happened to anyone else? Any suggestions for getting better
performance out of it? Should I uninstall and reinstall?

For the record, I'm using a MacBook 2 Ghz Intel Core 2 Duo with 1 GB 667 MHz
DDR2 SDRAM and running OSX version 10.4.11.

Any thoughts and help would be appreciated. Particularly if you can keep it
dumbed down. You can assume my computer knowledge is only about a step or
two above that of your mom.  :)


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to