reassigning to porting....
You may have a look at http://porting.openoffice.org/mac/support.html
for other resources...

We need more info about your hardware and software configuration. For 
example, does your machine have Dual CPUs?

Please use the Console application to see if any relevant error messages are 
written to the Console, and if any crash logs are created, when you have 
problems - if so, post the information here.

Are these documents new documents you have created in OOo, or are they 
documents imported from another application? - if the latter, if it is possible, 
please attach the documents here.

Your problem appears to be unique to your configuration.

Created attachment 8091 [details]
Output from Apple System Profiler's Console Log

Created attachment 8092 [details]
The file referred to in console.log

Okay...
It's a single processor 800MHz PowerPC G4 with 256MB RAM, running OS X version 
10.2.6.
I've posted the log; I reproduced the bug again, so the 
log shouldn't be polluted by anything else - all I did was start a word processing 
document, type a couple of words, and try to save it!

I don't know whether it's significant or not, but it always seems to take nearly 5 
minutes to start up (even after starting X11 first).  I looked at "top -u" and soffice.bin 
(the n isn't visible!) took 4.5 minutes of CPU time (at about 80%) before I even saw the 
OOo splash screen.  It's not a slow Mac...

The slow startup time is a clue - normal OOo startup on a machine of your 
class should only take 30-60 seconds.

This is usually a sign of a corrupted or unsupported font, such as the Asian 
fonts. This could lead to the kind of crashes you are seeing (although usually 
things crash much sooner).

Suggest removing all fonts from :

path_to_OOo_103_installation/share/fonts/truetype

and start adding back the fonts 1 at a time until you find the offending font (if 
any).

Please report back your findings. You might also want to visit the online 
support forums at <http://ooodocs.sourceforge.net> or <http://
trinity.neooffice.org>.

FYI, the console.log you attached was helpful, but was not the Apple System 
Profiler log (if you do a Save or Save As in ASP for Mac OS X 10.2.6, the 
default ASP report name will be "Apple System Profiler").

The crash log was also helpful, but it doesn't seem to point to corrupted fonts 
as being the cause, so there might be something else going on.

Thanks.

Removing those fonts (some of which have unicode filenames - a surprise - and 
some of which begin with #s) seems to have done the trick for the startup speed.  I've 
now only got the fonts that start with an upper-case letter, and it starts in just over a 
minute (which includes starting X11). 

I didn't do a "save as" for the ASP, by the way: I just cut-and-pasted the relevant 
chunks of output!

I tried saving a simple word processor file in the default forat again, just in case, and 
it still takes 100% CPU.  I didn't mention before that it does create a temporary file, 
but that never exceeds 0 bytes.

I'll have a look at the forums you suggested.

Thanks again,

Richard

reassigned.

One of the users suggested in the support forums, to remove the 
following cache file :

Library/Preferences/OpenOffice.org1.0.3/user/psprint/pspfontcac
he

in your home directory.

The file will be automatically re-generated when necessary.

how about try using the latest OOo 1.1 Rc5, 
Your version already old enough, and many bug fixes since your version 
and 1.1 RC5. If the problem still happend in 1.1 RC5 please report back

Utomo - I know you are just doing your job, but versions of OOo 
1.1 haven't been released to end users for the Mac OS X 
platform,  so unless "rmwiseman" is in a position to download 
the 1.1 sources and build them himself, he can't verify this bug.

I suggest that "rmwiseman" try again with OOo 1.0.3 now that he 
has removed the pspfontcache file, and see if the problem 
persists.

Otherwise I suggest we close this issue as UNCONFIRMED if 
we don't hear back from him in a couple of weeks.

utomo> Terry Teague:
Ooops Sorry. 

Utomo> rmwiseman:
Please try again as suggested, and report back. otherwise we close
this issue if didnt hera from you anything

I tried deleting that cache file, but it didn't work.  (That is, I deleted the file, but it 
made no difference to whether I could save my work!)

The latest downloadable version seems still to be 1.0.3, which is what I've got.  :-(

Thanks for the suggestion anyway.

OK, we kind of have a build of 1.1.0 at
http://mirror.aarnet.edu.au/pub/openoffice/contrib/MacOSX/OOo_1.1.0_031006_MacOSX_install_en.tar.gz


This is not "released" per se, but it would be nice to see if the problem occurs
or disappears for you.

This issue has been UNCONFIRMED for quite a while now, its worth looking at
1.1.0 and seeing if there's any improvement.

I've tried the suggested URL a number of times over a number of days and my browser never 
manages to contact the server.  Is there an alternative download location I could try...?

Grab it at your local mirror. mymirror.asiaosc.org has it too. Follow on with
the same tree though (i.e. openoffice/contrib/...)

I've now installed OOo 1.1.0 - thanks for the help with that.

It doesn't crash anymore.  Unfortunately, it also doesn't save files.  Or load them.

When I try to save (I've tried the default format and Word 97), I get an error saying:


Error saving the document Untitled1:
Write Error.
The file could not be written.


...and that's regardless of what I decide to call the file.

When I try to load a file (which I believe is in Word 97 format), I get the error:


Error loading document file://Users/richard/Desktop/test.doc:
Error creating object.
The file could not be created.


:-(

Although I couldn't say for sure that the version of OOo 1.1.x you downloaded 
is bug-free, I am pretty sure it should be capable of opening/saving OOo native 
format documents, just as OOo 1.0.3GM was.

There is obviously something unique to your configuration that is causing the 
problem, and you are going to have to help provide more information if we are 
to get to the bottom of this problem.

For example, do you have any Fink-built software installed, or any Unsanity 
haxies/APE installed?

Do you have problems with any other applications? Do you have any RAM upgrades 
installed?

I haven't knowingly installed any Fink-built software or any Unsanity haxies/APE
- I don't even know what these are!  I've not installed much at all, really, but
what I have installed I've more or less understood (e.g., Brickhouse firewall,
Emacs, Photoshop Elements, and various bits of Apple software, which are updated
automatically).  My version of X11 is the Apple one, which, last time I checked,
didn't have a newer version available.

I haven't had any problems with other software, and I've not made any hardware
changes to my Mac.  Really, my Mac's more or less as it was out-of-the-box, but
with the newest versions.

I don't suppose any of that helps much...

Thanks for the info - it at least gives us a direction to go in. I know the 
firewall stuff should have no effect, but could possibly try a test with it 
disabled (disconnect physically from the network if security is an issue) or 
uninstalled?

As I stated earlier, what you provided as an attachment was the Console log 
from ASP - while helpful, what I really need is an ASP report of your system 
(look in the File menu for options for saving/exporting a report - depending on 
your version of ASP).

How was your Mac OS X installed - 10.2 from CD, then upgraded with web updates 
to 10.2.6? Knowing the sequence of installation of Mac OS X and its updates 
might be helpful.

I'm at work now, so I can't check everything you ask immediately, but I'll do it
this evening when I get home.

My OS X was, if I remember correctly, installed as 10.1 from CD; subsequent
upgrades were done using automatic update facility.

Two probably-unimportant things I neglected to mention before: (1) the
installation of OOo was entirely smooth, with no warnings or anything to suggest
anything was wrong (which I'm mentioning as a good thing!); and (2) I've got
Apple's developer tools (just Unixy things like gcc, make, Perl, etc., from what
I recall).

I'll have a try with the firewall diabled (though I can't think why that would
affect OOo).

Created attachment 12936 [details]
My system profile (logs removed as irrelevant and large!)

Thanks for the ASP report. One slight thing I noticed - you have a 2 GB volume 
called "swap" - do you in fact use this as Mac OS X swap space, and therefore 
you customized your system to do this?

Are you logged in as the same account that you installed OOo with?

Perhaps you could type the following into a Terminal session, and paste the 
results here :

cat ~/.sversionrc

Yes, the 2GB called 'swap' is indeed swap space.  I'd bought myself the O'Reilly "Missing Manual" 
book on OS X, and I believe that was one of the things they recommended doing (on OS X 
installation).

The .sversionrc file contains the following:

[Versions]
OpenOffice.org 1.1.0=file:///Users/richard/OpenOffice.org1.1.0

FYI, my previous one (which I got rid of (by renaming) as per the OOo instructions) contained:

[Versions]
OpenOffice.org 1.0.3=file:///Users/richard/Library/Preferences/OpenOffice.org1.0.3

I haven't uninstalled the previous version, as I understand that it won't interfere with the new one 
(being installed elsewhere).  I installed OOo using the network server method, so installed the main 
of it as root, then ran the newly-created setup (in my case in /opt/OpenOffice.org1.1.0) for the 
logged-in user that created the profile.

Can you try this with the latest Technology Preview release thats available?
1.1.1 that is.

Apologies, my previous email address disappeared, so I didn't see that last message.

However, I've just installed 1.1.2 and it works splendidly!  No problems at all.  Many thanks for all 
efforts in solving my problem.  (For a while recently, I thought I was going to have to fork out for 
Microsoft Office!)

So should we resolve this bug as "works for me"?

Done, closed as WORKSFORME, with a newer release

close issue.