Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When I try to convert a word document using the ooextract python script from open office like

/usr/local/bin/ myDocument.doc myDocument.pdf

the open office deamon (sOffice.bin) takes 100% CPU load forever.

We are using Open Office 2.6.3 on a virtual machine running debian squeeze 2.6.32-5-amd64


We found out that this appears only with our test document, other documents can be converted without problem. But how can we find out what's wrong with our document. How can we enable traces/loggin o the sOffice.bin process?

share|improve this question

migrated from Sep 5 '11 at 19:10

This question came from our site for system and network administrators.

You may want to include file size, etc. And does the conversion ever complete? Sounds like there could be a bug in the script. – Josh M. Sep 5 '11 at 19:12
Using 100% of your CPU is the best thing a program can do. The faster it runs, the more early it will finish. Your problem is, that it takes so long to run, the absolute CPU occupation, not the relative one. – user unknown Jan 13 '12 at 7:04

I had a similar issue. To debug it, I put the test document under version control and removed significant chunks of it at a time; ensuring I took note of what structures were removed.

This let me isolate it to an issue with 2.4.1 and a Table, containing a Row, with lots of text content. The table was allowed to split across pages, the row was not. Rendering to PDF caused a similar 100% CPU usage issue.

share|improve this answer
up vote 0 down vote accepted

It seem to be related to Open Office Version 2.6.3, with Open Office 3.3.0 we do not have the problem anymore.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .