LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (http://www.linuxquestions.org/questions/linux-software-2/)
-   -   OpenOffice/LibreOffice writer uses 100% CPU time, 100% memory, workaround someone? (http://www.linuxquestions.org/questions/linux-software-2/openoffice-libreoffice-writer-uses-100-cpu-time-100-memory-workaround-someone-875662/)

jlinkels 04-18-2011 11:31 AM

OpenOffice/LibreOffice writer uses 100% CPU time, 100% memory, workaround someone?
 
I am trying to open a document in LibreOffice or OpenOffice which was saved in Word 2007 by a co-worker.
We have both written some parts, and the last step was that he integrated my part in his part, saved it as .DOC and sent it to me.
When I try to open this document in LibreOffice or OpenOffice, CPU usage by soffice.bin skyrockets to 100%, all memory is being used up until the soffice.bin process is killed by the kernel.
So far I have tried to open this document in:
LibreOffice 3.3.2 Debian Unstable, kernel 2.6.32-5-686
OpenOffice 3.2.1 Debian Squeeze, kernel 2.6.32-5-686
OpenOffice 3.2.0 Debian Squeeze, kernel 2.6.32-3-686
OpenOffice 2.4.1 Debian Lenny, kernel 2.6.26-2-686

All without succes. I tried to open the document in Word 2000, where it opened all right but the layout was completely snafu.
I also tried to open it in Word 2003, and saved it again, both as DOC and DOCX.
I tried to open the DOCX in OpenOffice 3.2.1. It opens all right, but as soon as I scroll past a certain part in the document, CPU usage skyrockets.
When I open the freshly re-saved .DOC version in OO 2.4.1 CPU goes to 100% immediately.

Any suggestions as how to work around this? The file size is only 2.7 MB, and I have a bit of a problem telling my co-worker I cannot work on our file because I am using Linux. You know how it works... Besides we are 8000 km apart so there is only e-mail exchange, we can not work on each other's computer.

If someone wants to reproduce this, PM me and I'll send a link to the file in question.

--Edit: Oops forgot to mention my system. Added behind the OO versions.

jlinkels

DavidMcCann 04-18-2011 11:37 AM

Quote:

Originally Posted by jlinkels (Post 4328182)
as soon as I scroll past a certain part in the document, CPU usage skyrockets.

What is the doc doing at that point?

Have you tried rich-text format?

catkin 04-18-2011 11:42 AM

You could try opening the docx, using Ctrl+A and Ctrl+C and, if that works, pasting into a new document ...

EDIT: if you have OOo or LO on the same system as Word 2003, you could do the above on that system ...

jlinkels 04-18-2011 01:20 PM

Quote:

Originally Posted by DavidMcCann (Post 4328189)
What is the doc doing at that point?

My report was not accurate. The CPU skyrocketed when I was scrolling, not at a certain point. The time between start of the scroll and the 100% CPU was variable.
Quote:

Originally Posted by DavidMcCann (Post 4328189)
Have you tried rich-text format?

No, but I did after your post. Saved as RTF. Opened it in OOWriter 3.2.1. Took about 5 minutes 100% CPU but then the document opened. Unfortunately about half of all picture were not shown as picture but as pages of hex dump.

jlinkels

jlinkels 04-18-2011 01:24 PM

Quote:

Originally Posted by catkin (Post 4328198)
You could try opening the docx, using Ctrl+A and Ctrl+C and, if that works, pasting into a new document ...

I doesn't work. When I open the document in OOWriter 3.2.1 and don't do anything, the CPU load stays down. As soon as I do something in the document (placing my cursor in it, Menu -> Edit -> Select All) the CPU goes up full load.
Quote:

Originally Posted by catkin (Post 4328198)
EDIT: if you have OOo or LO on the same system as Word 2003, you could do the above on that system ...

I am running OO on Linux. My first post was not complete, added that information now. I don't have regular access to a Windows machine. I run a few systems with VM's but that is only to access my on-line banking with IE6...

More info in the next post.

jlinkels

jlinkels 04-18-2011 01:37 PM

OK, thinking along the lines of asking my co-worker to cut some parts from the document and resave it, I got the brilliant idea to do that myself, rather than admitting shamefully that Linux actually cannot replace Windows.

What actually happened is this:
  • My colleague created a document in Word 2007 and sent it to me. I was able to open it in OO-writer
  • Then I wrote some chapters in OO-writer which included pictures and tables
  • These chapters I saved as DOC and submitted those to my colleage
  • My colleague edited his DOC file and integrated my chapters in his file, saved it as DOC and sent it to me again
  • This time I could not open the DOC file anymore, experiencing the problems I just explained.
I had done so before, and in course of time my colleague has split the document in two as to make the size more managable. Part #1 also consists of an integration of his pieces and my chapters and I still can open that without problems, altough that file is about 8 MB in size.

What I did eventually, while I had the file open in Word 2000, I cut out the chapter I had submitted last. Saved the file again, and now I could open the file in OOWriter without any problems.

So recapitulating, we had a Word DOC, pasted some parts from another DOC created with OO-writer, saved that as DOC in Word, and then it could not be opened anymore regardless of the version of OO.

I still think this is a bug, in my mind an application should never run out of control when the input file is not consistent or contains errors.

Thanks for who answered me, I filed this bug also against the Debian bug system.

jlinkels

SaintDanBert 08-17-2012 06:02 PM

Quote:

Originally Posted by jlinkels (Post 4328182)
I am trying to open a document in LibreOffice or OpenOffice which was saved in Word 2007 by a co-worker. We have both written some parts, and the last step was that he integrated my part in his part, saved it as .DOC and sent it to me. When I try to open this document in LibreOffice or OpenOffice, CPU usage by soffice.bin skyrockets to 100%, all memory is being used up until the soffice.bin process is killed by the kernel.
...


Yet More Follow-up:
TIME+ runtime is now 23h55min... all the other values remain the same.
Can someone tell me how to force a "crash dump" or similar process "trace back" so that we know what is going on?

More Follow-up:
I let the workstation "idle" overnight. The LO-writer process now has 17h57min of TIME+ runtime. One CPU continues at 100% while the other readings -- VIRT, MEM%, SWP-bar, MEM-bar -- are unchanged.
What in Sam Hill is going on!!!

Follow-up:
After over 40 minutes "idle" at the user interface, the process continues to run at 100% CPU. Total process runtime is 1h39min. After this much elapsed time without any sort of task management intervention, I can't even guess what the code might be doing.

I am having similar problems with LibreOffice Writer v3.4.4-0ubuntu1.4 and Linux Mint-12 with Cinnamon.

In my case, I have a simple DOCX file. It consists of about 30 bullet statements without using a formal "bullet" style. Instead, they prefix each point with "* space space".

I have enabled Change Recording and then step through the document adding comments to each bullet point of the original document. On occasion I press ENTER and LO-Writer formats the preceding "* sp sp" paragraph as a "bullet" style. I press CTRL-Z to undo that formatting and continue my edits.

After a while of working with the document, I mis-format a 'graph into a formal "bullet" style and try CTRL-Z dance. The CPU goes to 100% (as reported by 'htop') and stays there. Neither the value of VIRT (885M) nor the value of MEM% (1.5) change. Both the MEM bar and the SWP bar are stable. One of the five CPU's is pegged to 100% the others are doing normally.

Thanks in advance,
~~~ 0;-Dan

SaintDanBert 08-20-2012 12:42 PM

Quote:

Originally Posted by SaintDanBert (Post 4757124)
[color=green][indent]
Yet More Follow-up:
TIME+ runtime is now 23h55min... all the other values remain the same.
Can someone tell me how to force a "crash dump" or similar process "trace back" so that we know what is going on?
...

I tried to use strace but could not discover the right things to do. However, 'strace', that is trace system calls is not really what I'm looking for. I'm really looking to discover where we are on the function call stack.

Is there some way to attach gdb to an already running program process, and then:
Code:

prompt$  ... some command to attach gdb ...

gdb>  CTRL-C
...
gdb>  bt
...
back trace output
...

100 years ago I used to know how to do this, but I've slept since then.
~~~ 0;-Dan

SaintDanBert 08-25-2012 01:44 PM

Bump!!!

This problem happened again.
I still cannot get a back trace or stack dump from a running process.

Can anyone tell me how to do that?
~~~ 0;-Dan

SaintDanBert 08-28-2012 03:21 PM

I guess no one really cares about Libre Office mis-behavior...

Sadly,
~~~ 0;-< Dan

terry-duell 08-29-2012 06:57 PM

Quote:

Originally Posted by SaintDanBert (Post 4766761)
I guess no one really cares about Libre Office mis-behavior...Dan

I hope they do!
I can't be sure, but this bug report <https://bugs.freedesktop.org/show_bug.cgi?id=39006> looks like a similar problem to the one you are experiencing.
Have you been able to try another version to see if behaves differently? I note that LibreOffice 3.6 is available from the LO website for download...it might be worth a try.

Cheers,
Terry

SaintDanBert 08-30-2012 01:50 PM

Quote:

Originally Posted by terry-duell (Post 4767807)
I hope they do!
I can't be sure, but this bug report <https://bugs.freedesktop.org/show_bug.cgi?id=39006> looks like a similar problem to the one you are experiencing.
Have you been able to try another version to see if behaves differently? I note that LibreOffice 3.6 is available from the LO website for download...it might be worth a try.

Cheers,
Terry

I'm aware of newer editions of LO, but I'm running Mint-12 (Ubuntu 11.10) and they are not in the repositories. In a prior life, I side loaded LO over and older edition of Ubuntu without joy. As a result I'm shy to FUBAR again.

Thanks for the bug-report link. I'll go and read.
~~~ 0;-Dan


All times are GMT -5. The time now is 07:52 PM.