Mailinglist Archive: opensuse (1702 mails)

[Clayton <smaug42@xxxxxxxxx>]

Periodically, and on random documents, OOo 3.1.0 (latest build from
the openSUSE repos) on openSUSE drives one CPU core to 100% and OOo
locks solid.  I cannot pin this down to any one thing/event or
document style/content.  When this happens OOo stops responding, and
the only way out is to force-kill the soffice.bin process.

I've tested this over and over, and I can duplicate it on openSUSE...
I've sent other people the same documents, and they can open/edit them
no problem.  If/when a document acts up, then even simply opening up
the document (after a kill and restart of OOo) and scrolling down one
page can duplicate the problem... that exact same document in say...
Ubuntu 9.04 with the Ubuntu build of OOo works fine.  In some cases, I
can no longer work on the document in OOo on openSUSE... but I can
fire up a VM and edit the document just fine using OOo Windows or OOo
in another Linux distro install (so I'm assuming the document is not
corrupted).

This is not new to me with OOo on openSUSE... I've had similar
problems in previous releases of OOo.

I've not yet installed the vanilla OOo from OO.o to compare to the
Novel version.

All documents I'm working on start their life as ODT docs and stay as ODT docs.

Any ideas?  Anyone else encountering this?

C.
-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx