My girlfriend's OpenOffice has been freezing up on a regular basis since
sometime in December.  

Jan 11 16:28:48 xxxxx [0x0-0x35b35b].org.openoffice.script[17581]: 
2009-01-11 16:28:48.137 soffice.bin[17582:10b] 
*** -[NSStatusBarWindow containsMouse]: unrecognized selector sent to instance
0x18895a80

The error message is similar to bug 96654 which was closed "worksforme" due to
insufficient information, forcing me to open a new issue from scratch.  

The log message time stamp is consistent with the last freeze this afternoon. 
There are many such messages in the log file, which most likely correspond with
many previous freezes.  

The freeze is not sufficiently predictable to reproduce exactly, but the general
scenario is consistent.  

My girlfriend has two OpenOffice documents open side by side on the same screen
(might be partially overlapping).  She wants to cut and paste many selections
from the source document to the target document.  Sometimes the source or target
originated as MS Word docs and were later converted to ODT.  At first we
suspected bad conversion, but lately we're not so sure.  

Eventually a cut and paste effort locks up the UI (from a practical perspective,
more on that later).  A mouse selection is made in one window, then a copy
action (usually via the right click menu), then a focus change to the alternate
window, which fails to display a cursor, and won't respond to a paste event.  In
fact, at this point, no open Writer window will respond to interior mouse
clicks.  OpenOffice must be killed and restarted.  

I've been a software developer for 20 years, though I have only basic skills
under OSX.  I sat down to examine the nature of the freeze, which is one of the
strangest I've seen.  

The document windows will respond to window drags and focus changes, keeping the
window contents updated.  The document interior and scroll bars are
unresponsive.  No cursor is displayed.  Most selected menu items go blink/blink
on mouse release and then do nothing.  There are some exceptions.  The
"preferences" menu item brings up a working preferences dialog.  I think "about"
also worked.  Nothing interior to the document works.  

I was unable to find any toolbar icon which worked.  The window min/max controls
work.  I was able (once) to close a toolbox (moments later, Writer had a major
fault and all I had was a white window with a rainbow pinwheel.) 

Controls on the bottom right corner of the frame continue to respond, but don't
do anything.  I was able to interact with the page layout and zoom controls.  

Here's where it gets interesting.  The lower right window resize drag continues
to work.  The surprise is it often manages to update the contents of the window
with respect to operations that hadn't appeared to do much.  Double page layout,
zoom, and increment clicks on the vertical scroll wheel now suddenly take effect
in the redrawn content, but *only* during resize drag.  

Sometimes the resize-drag is extremely laggy and sometimes when you stop to let
it catch up, it doesn't fully catch up (e.g. the lickable vertical scroll
antifreeze blob never appears on the scroll bar).  It catches up again at the
next movement.  

The yellow tool tip on the mouse wheel is also interesting.  Vertical mouse
scroll becomes clearly evident when the next resize-drag is performed.  Also,
during mouse scroll, the yellow tool tip *does* correctly update according to
the section you are scrolling over, *but* the window contents don't reflect this
until the next resize-drag.  

I tried to make changes to the document contents with the tool bar and then
reveal those changes with a subsequent resize-drag, but never achieved this.  

This Mac is a fully updated 10.5.6 with a 99% stock configuration.  I once
applied one nasty under-the-hood patch to NeoOffice which I've since forgotten.
 I have no idea why this Mac is afflicted when so many other identical
configurations out there don't seem to be.  

This freeze has happened dozens of times.  There was one case where a certain
paragraph when selected was freezing every time.  Strangely, when I suggested
trying a drag-and-drop interaction, this worked fine.  We no longer have the
document with the reproducible problem.  At that point I still believed it was
just a doc to odt translation error.