Apache OpenOffice (AOO) Bugzilla – Issue 56408
"double free or corruption (fasttop)" when navigating whithin the attached document
Last modified: 2013-08-07 14:40:21 UTC
The attached document has been created with OO-1.1.3 without any problems or limitations. Importing this document works in OO-1.9.129 but scrolling pages beyond page 15 is freezing writer immediately.
Created attachment 30713 [details] document created by writer (OO-1.1.3), (c) 2005 by me
No problems with OOo 2.0 and WinXP.
*** Issue 56409 has been marked as a duplicate of this issue. ***
No freeze while scrolling through entire document (by page down or by mouse) on OOo 2.0.0 rc {1,2} on Linux (Fedora Core 4). Observation: On page 47 (or nearby), there is a linked (not embedded) image that does not display.
It should be easy to reproduce this bug with any recent Live-CD of (K)Ubuntu 5.10 "Breezy Badger" > http://www.kubuntu.org Some hours ago, I have found a similar bug report at the official Ubuntu Bugzilla website http://bugzilla.ubuntu.com/show_bug.cgi?id=18171
I also cannot reproduce the problem on Windows and SUSE 9.2. you please have a look on your distribution, please. Maybe the key the Times New Roman Font, which is used in the document. On certain systems with a certain Font Substitution - maybe this leads to a loop situation sometimes.
no freeze on a mandrake based system. Got a live-CD from ubuntu, but did not find a system that will run it. (Starting fails during hardware-detection...) Maybe I'll unplug my working machine and give it a spin..
confirming on ubuntu 5.10 - This is related to glibc. When running OOo on ubuntu 5.10 scrolling through the attached document results in the following error on the console: *** glibc detected *** double free or corruption (fasttop): <some hex> *** When exporting MALLOC_CHECK_=1 then no freeze occurs, but no error-message is printed to the console either. The error occurs both with the OOo that came with ubuntu and with OOo 2.0 Since a workaround is available (export MALLOC_CHECK_=0) and this problem doesn't occur with other distros, I don't raise prio.
forgot the crash-keyword.
interestingly my comments from this issue have somehow vanished; afair I wasn't able to reproduce this one either. @cloph: I wouldn't call the mentioned environment variable a workaround but consider it harmful and evil. Anyway a crash, deadlock or loop should always be worth a P2. Raising Prio. But admittedly the question remains why this happens on Ubuntu only and what's the meaning of the assertion: "*** glibc detected *** double free or corruption (fasttop): <some hex> ***" US->MCI: were/are you able to reproduce this one on your Ubuntu box? Thx. for your help in advance.
Hi All... I'm working on Ubuntu5.10 using OOom139 from ftp.linux.cz. I get the described effect on page 11/78 by scrolling from page 11 to page 12... All images on page 1 to 11 are visible, I can't see anything unusual... the output on the console: xyz@home:~$ soffice *** glibc detected *** double free or corruption (fasttop): 0x0858a870 ***" output of ps -ef | grep soffice: xyz@home:~$ ps -ef | grep soffice xyz 13769 13690 0 09:26 pts/1 00:00:00 /bin/sh /usr/bin/soffice xyz 13785 13769 5 09:26 pts/1 00:00:15 /etc/openoffice.org-2.0/program/soffice.bin xyz 14694 14608 0 09:31 pts/2 00:00:00 grep soffice I suggest to remove the keyword "crash" since OOo doesn't crash but "hangs"... Using KSysGuard I can see that OOo is still running consuming ~190MB of RAM (Vm-size) and 0% CPU... I hope this helps a little...
Thanks MCI for your support! > I suggest to remove the keyword "crash" since OOo doesn't crash but "hangs"... kind of an academic debate isn't it? consider a heap corruption and as a consequence a dying thread (just a theory); what would you call it? anyway, similar error message as in issue 55090 if not dupe. but I hesitate to close as dupe as we seem to have a reproducible scenario here (but only on Ubuntu sofar). need to get me an Ubuntu box myself.
Hi us, yes , this may be an academic debate... ;) I did my tests using KDE 3.4.3... anyway, I tried this again using m143 from ftp.linux.cz on KDE and I get the same result as in m139... Just for the records: This is not the Ubuntu-version of OOo!
Well, it is an academic debate when one focuses on the word "crash" itself, but in IZ-terminology, the "crash"-keyword just specifies anything that ends up in OOo being in an unrecoverable state. Be in an abnormal abortion, a freeze, a loop, or just a "hang". If you cannot access OOo anymore, it is worth the crash-keyword. See also the description of the keyword "crash: This keyword can be used for any crash, freeze, hang, that occurs."
that was also my understanding. thx. for clarification.
failed to reproduce on Ubuntu 5.04 (Hoary Hedgehog).
Even with an upgrade to OO-2.0 and "export MALLOC_CHECK_=0" Writer frezzes while navigating. [(K)Ubuntu breezy badger]
unable to reproduce in the current Ubuntu development branch (dapper), with packages based on m143.
*** Issue 59355 has been marked as a duplicate of this issue. ***
set target.
Might this be related to issue 55090? Also, cross reference this Ubuntu bug: http://bugzilla.ubuntu.com/show_bug.cgi?id=18201
I reproduced the bug with OO Impress on Ubuntu 5.10 with Openoffice 2.0.0 (from Automatix) and 2.0.1 (from http://people.ubuntu.com/~doko/OOo2/). Error Message is: *** glibc detected *** double free or corruption (fasttop) 0x085c0598 *** regards Dirk
Hi all, I installed the "official" files (m152 in rpm format) from ftp.stardiv.de and I get the same error here on Ubuntu Linux 5.10: mci@home:~$ /opt/ooo-dev2.0/program/soffice *** glibc detected *** double free or corruption (fasttop): 0x083bdca8 *** BTW: This document (Skriptum 2005.sxw) hangs SO7PU5, too! BTW 2: I have another document (a ppt-file) which hangs OO02.x/SO7PU5 in the same way... This powerpoint file hangs SO7PU5, too! I try to get the permission from the author to attach the file here...
An Error-Report has been sent. The ID of the error report is rcq928.
us->pl: could you pls. take over, there should be an Ubuntu box inhouse (ask FPE) where this should be reproducible. Thx.
Having installed Kubuntu 5.10 and reproduced the bug i can finally say that this is duplicate to issue 55090 which is in turn duplicate to issue 58249 *** This issue has been marked as a duplicate of 58249 ***
closing duplicate