[opensuse] OpenOffice.org 3.1(and prev versions) locking up?
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@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 02 September 2009 01:09:17 am Clayton wrote:
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).
What about another user account on this same machine? There is an extensive file structure of work files in each user's directory (a hidden subdirectory) that may be corrupted for your account. -- __________________________________________________________ Somebody stoled my tag line, so now I have this rental... JSA -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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).
What about another user account on this same machine?
There is an extensive file structure of work files in each user's directory (a hidden subdirectory) that may be corrupted for your account.
Yup, tried that too. New account... deleted the user config files... rebooted... new/clean install even. No difference. Randomly in random documents... I get a lockup in OOo, but once it locks up I can consistently duplicate the lockup. The doc today... I've been working in it for about an hour, doing my usual edit, and save routine, saving every page or so of edits. On page 38 it locked up while editing a table (adjusting styles). Kill and restart... lockup before I can even get to page 38. Kill and restart... again.. lockup. Go do something else for 10 minutes.. come back.. open the document, and I can scroll to page 38. Start editing the table.. no problems... finish up edits on the table and move to editing body text... lockup. I can move on to a different document, and no problems (so a user profile corruption is unlikely since it does not affect any other documents)... I can edit that entire other document start to finish... no issues... come back to the original document and... lockup. Open that problem document in another Linux distro or in Windows (in VBox, using shares, and editing the document in-situ - ie it's not moved/copied etc.) and no problems. I've sent the problem documents to other people... and they can open edit with no issues... so a document corruption is unlikely since the document is fine for other OOo builds/installs. You might say I'm a bit baffled by this. It's not new, but hasn't been a big issue until recently when I'm trying to work on a lot of documents. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Clayton, On Wednesday 02 September 2009, Clayton wrote:
You might say I'm a bit baffled by this. It's not new, but hasn't been a big issue until recently when I'm trying to work on a lot of documents.
Could you please report the problem with all these interensting details at https://bugzilla.novell.com against the product OpenOffice.org? I do not promise anything. These "random" problems are usually hard to debug and fix. Anyway, the mentioned document looks promissing. There is something on the page 38 that helps to trigger the problem. Could you please attach the document to the bug? It might help a lot. Also please mention more details about your system, see http://en.opensuse.org/Bugs:OOo#What_to_include_in_bug_reports Do you have more CPUs? It might be a race condition. It is possible that the problem is hidden in the virtual machines. Also it might be a problem with your graphics card. Well, it would probably freeze the whole system. Anyway, such problems might be filtered by the VBox as well. Another possibility would be a problem with memory. Are you out of memory when the process freezes? You might see it by the commands "top" or "free". OOo had problems with particular fonts in the past. It is possible that the problematic font is just missing on the other systems. Yes, it is possible that there is an openSUSE-specific bug. Though, I think that it works on the other systems just by chance. For example, also Ubuntu uses the extra patches from Go-oo, ooo-build, see http://go-oo.org/= > so the Ubuntu build should not be that different. -- Best Regards, Petr Mladek software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: pmladek@suse.cz Lihovarská 1060/12 tel: +420 284 028 952 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Could you please report the problem with all these interensting details at https://bugzilla.novell.com against the product OpenOffice.org?
Done :-)
I do not promise anything. These "random" problems are usually hard to debug and fix. Anyway, the mentioned document looks promissing. There is something on the page 38 that helps to trigger the problem. Could you please attach the document to the bug? It might help a lot.
I know how hard these transient problems can be to track down.. if it is ever possible. I've linked (in the bug report) to a specific document in a before and after state. This particular document has caused a lot of trouble on my system... but annoyingly.. it's intermittent.
Do you have more CPUs? It might be a race condition. It is possible that the problem is hidden in the virtual machines.
Possible.. it's on a dual core AMD.
Also it might be a problem with your graphics card. Well, it would probably freeze the whole system. Anyway, such problems might be filtered by the VBox as well.
Hmmm I hope not :-) The problem has persisted across at least 2 possibly 3 video cards... all nVidia.
Another possibility would be a problem with memory. Are you out of memory when the process freezes? You might see it by the commands "top" or "free".
Nope, not out of memory at all. I've got 8GB RAM in this machine. Swap is never touched.
OOo had problems with particular fonts in the past. It is possible that the problematic font is just missing on the other systems.
That could be... but then again, I'd expect it to happen all the time, as opposed to just once in a while - at least in the doc set I'm working on where there are 20+ documents all from the same source, all using the same fonts... and where only some have issues. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Clayton schreef:
Could you please report the problem with all these interensting details at https://bugzilla.novell.com against the product OpenOffice.org?
Done :-)
I do not promise anything. These "random" problems are usually hard to debug and fix. Anyway, the mentioned document looks promissing. There is something on the page 38 that helps to trigger the problem. Could you please attach the document to the bug? It might help a lot.
... Hi, Sometimes I also get lockups. I have the impression that when I use the File-menu and want to go to the pdf-export and I go too far down the menu-list then the lockup occurs. Maybe some submenu tries to open but locks OOo up. I'll try if I can trigger it. -- Met vriendelijke groeten, Koenraad Lelong
Koenraad Lelong schreef:
Clayton schreef:
Could you please report the problem with all these interensting details at https://bugzilla.novell.com against the product OpenOffice.org?
Done :-)
I do not promise anything. These "random" problems are usually hard to debug and fix. Anyway, the mentioned document looks promissing. There is something on the page 38 that helps to trigger the problem. Could you please attach the document to the bug? It might help a lot.
... Hi, Sometimes I also get lockups. I have the impression that when I use the File-menu and want to go to the pdf-export and I go too far down the menu-list then the lockup occurs. Maybe some submenu tries to open but locks OOo up. I'll try if I can trigger it. Hi, Sorry it took so long. I tried to lock it up, and when I hover the mouse over Send in the File-menu it does lock up.
-- Met vriendelijke groeten, Koenraad Lelong
OOo had problems with particular fonts in the past. It is possible that the problematic font is just missing on the other systems.
I had an issue like that some years ago. According to my notes I identified different fonts being installed by running: xlsfonts | sort > $FILE on each system and diffing the resulting files. -- OpenGroupware developer: awilliam@whitemice.org http://whitemiceconsulting.blogspot.com/ OpenGroupare & Cyrus IMAPd documenation @ http://docs.opengroupware.org/Members/whitemice/wmogag/file_view -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 02 September 2009 05:51:44 am Petr Mladek wrote:
Hi Clayton,
On Wednesday 02 September 2009, Clayton wrote:
You might say I'm a bit baffled by this. It's not new, but hasn't been a big issue until recently when I'm trying to work on a lot of documents.
Could you please report the problem with all these interensting details at https://bugzilla.novell.com against the product OpenOffice.org?
I do not promise anything. These "random" problems are usually hard to debug and fix. Anyway, the mentioned document looks promissing. There is something on the page 38 that helps to trigger the problem. Could you please attach the document to the bug? It might help a lot.
Also please mention more details about your system, see http://en.opensuse.org/Bugs:OOo#What_to_include_in_bug_reports
Do you have more CPUs? It might be a race condition. It is possible that the problem is hidden in the virtual machines.
Also it might be a problem with your graphics card. Well, it would probably freeze the whole system. Anyway, such problems might be filtered by the VBox as well.
Another possibility would be a problem with memory. Are you out of memory when the process freezes? You might see it by the commands "top" or "free".
OOo had problems with particular fonts in the past. It is possible that the problematic font is just missing on the other systems.
Yes, it is possible that there is an openSUSE-specific bug. Though, I think that it works on the other systems just by chance. For example, also Ubuntu uses the extra patches from Go-oo, ooo-build, see http://go-oo.org/= > so the Ubuntu build should not be that different.
Petr, I am finally installing 3.1 as I write so I can follow up with this issue as well. I had to fight yast to install 3.1, it just kept showing 2.4, all the other languages of 3.1, but it would not let me upgrade (very strange). So I ended up just copying the OO package names and doing a zypper in -r OpenOffice <long sting of packages> and it is finally installing. I'll let you know. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Could you please report the problem with all these interensting details at https://bugzilla.novell.com against the product OpenOffice.org?
Bugzilla on this is: https://bugzilla.novell.com/show_bug.cgi?id=536235 C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bugzilla on this is: https://bugzilla.novell.com/show_bug.cgi?id=536235
Got another one... I was editing the document here: http://wiki.services.openoffice.org/wiki/Media:DevelopersGuide_OOo3.1.0_16Ja... On page 10 (of 19), one of my CPU cores jumped to 100% and OOo stopped responding. I had to kill soffice.bin to recover. I can reopen this doc, and go back to page 10... and edit the table on that page... and it'll lock up again...and again... If I take the same document into another Linux/OOo or Windows/OOo I can continue editing. The lockup does not always happen while editing a table. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Clayton wrote:
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.
Sorry, no ideas, but I am not having any such troubles with OO3.1. BC (Using 32-bit oS with KDE43.) -- Great Man reaches complete understanding of the main issues; Petty Man reaches complete understanding of the minute details." Confucius -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2009-09-02 at 10:09 +0200, Clayton wrote:
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'm running OpenOffice_org-3.1.0.6-2.1 (OOO310m21 Build:9319) and haven't had any lockup that I can recall. I do quite a bit of work in writer, calc, and impress including ~200 page documents. glibc-2.9-2.11.1.i686 Linux linux-m3mt 2.6.27.29-0.1-pae #1 SMP 2009-08-15 17:53:59 +0200 i686 i686 i386 GNU/Linux -- OpenGroupware developer: awilliam@whitemice.org http://whitemiceconsulting.blogspot.com/ OpenGroupare & Cyrus IMAPd documenation @ http://docs.opengroupware.org/Members/whitemice/wmogag/file_view -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Sep 2, 2009 at 4:09 AM, Clayton
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@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Have you tried downloading the OO from openoffice.org and seeing if it locks up on the same documents? You can install the "original" OO in parallel with that provided by OpenSuSE, the two do not seem to conflict and the original one has lately behaved better for us. Boris. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Sep 2, 2009 at 1:39 PM, Clayton
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.
Any ideas? Anyone else encountering this?
I have a similar problem when copying a HTML webpage w/ images /(eg http://www.linuxforu.com/how-to/recovering-deleted-files-easily/, [1] for actual .odt file download)/ and pasting it with images onto OpenOffice. On clicking on any of the images to resize or edit it, the application (OO-Writer) hangs temporarily, but it comes back again after a while, by itself (2-5 min, depending on document size). Generally, there is no need to kill the process (OO-Writer) when it hangs, as mostly it recovers by itself. This happens on OpenOffice (version 3.0.1 Build 9379), installed on Ubuntu 9.04 & openSUSE 11.1 (i686); on a desktop PC with Core2Duo E8500 (3.20 GHz) CPU, with 2 GB RAM, again only with documents copied over from a webpage.
C.
Jay [1] http://cid-7a88a7096e694629.skydrive.live.com/self.aspx/Linux|_Temp/Recover|_Deleted|_Files|_Linux.odt -- Linux User 483705 | openSUSE 11.1, Ubuntu 9.04 (i686) w/Windows XP -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
application (OO-Writer) hangs temporarily, but it comes back again after a while, by itself (2-5 min, depending on document size). Generally, there is no need to kill the process (OO-Writer) when it hangs, as mostly it recovers by itself.
I've considered that it might be a temp thing... I've left it running for 15 minutes after a lockup, keeping my CPU toasty warm, and nothing.... it never comes back to me. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 04 September 2009 08:31:03 am Clayton wrote:
application (OO-Writer) hangs temporarily, but it comes back again after a while, by itself (2-5 min, depending on document size). Generally, there is no need to kill the process (OO-Writer) when it hangs, as mostly it recovers by itself.
I've considered that it might be a temp thing... I've left it running for 15 minutes after a lockup, keeping my CPU toasty warm, and nothing.... it never comes back to me.
C.
I experienced this yesterday. OOo hung and did not come back after a 1/2 hour. It appeared to happened when it was trying to access my usb 120 gb drive. After killing the OOo process, I was able to access the drive the next time I tried but it had to recover the file I was accessing. Must have been saved badly the last time I used the file. I've seen this a couple of times but this is the first time I could relate it to the usb drive. Normally store documents on my hard drive. I was looking at a backup copy of a writer file when it hung. openSUSE 11.1 (2.6.27.29-0.1-default) OpenOffice 3.1.0 OOO31010m21 (build9219) Build 3.1.0.6 (from openSUSE repo's. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Sep 4, 2009 at 9:01 PM, Clayton
application (OO-Writer) hangs temporarily, but it comes back again after a while, by itself (2-5 min, depending on document size). Generally, there is no need to kill the process (OO-Writer) when it hangs, as mostly it recovers by itself.
I've considered that it might be a temp thing... I've left it running for 15 minutes after a lockup, keeping my CPU toasty warm, and nothing.... it never comes back to me.
C.
I recently upgraded to OpenOffice 3.1.1, and was getting crashes on pasting HTML-formatted text into Writer. Changing the Java version helped in my case; changed from /usr/lib/jvm/java-6-openjdk/jre to /usr/lib/jvm/java-6-sun-1.6.0.16/jre. This option is available in Tools - Options - OpenOffice.org - Java (attached picture [1]). May be worth a try if you're still facing the problem. Jay [1] http://www.imagebam.com/image/39882e49439920 -- Linux User 483705 | openSUSE 11.1, Ubuntu 9.04 (i686) w/ Windows XP Smolts Profile: http://www.smolts.org/client/show/?uuid=pub_b541a450-9bc1-45fd-beab-d46ee43a... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (10)
-
Adam Tauno Williams -
Basil Chupin -
Boris Epstein -
Clayton -
David C. Rankin -
Jay Mistry -
jsa -
Koenraad Lelong -
Petr Mladek -
upscope