Apache OpenOffice (AOO) Bugzilla – Issue 110595
oocalc crash when loading xls with links to second xls
Last modified: 2017-05-20 10:20:27 UTC
Oocalc crashes after eating all memory when loading a xls file containing links to a second xls file. I have seen this happening on all 3.x versions I tried on linux. The steps to reproduce the crash: - put "crashoo.xls" and "uren bron 2009.xls" in one directory - open crashoo.xls - wait till all the memory is used When the second file "uren bron 2009.xls" is renamed the file crashoo.xls does open, shows empty, but asked if links have to be updated. On windows 7 using OpenOffice.org 3.2 there is no problem. I will upload the xls files.
Created attachment 68730 [details] document with links
Created attachment 68731 [details] reference document
Modified Version due to report. Indeed, no problem with "Ooo 3.1.1 WIN XP DE[OOO310m19 (Build 9420)]" opening crashoo.xls from WIN Explorer
I do not reproduce the crash with OOo 3.2.0 (FR) under Ubuntu 8.04. @pimbollen: are you using vanilla build from this site or the version provided by your linux distribution ? Please try with the most recent official version. Regards. JBF
I have used builds from openSUSE. The main problem is the amount of memory used. The file crashoo.xls is a trimmed version of another file, and after loading it I see it uses more then 1GB of memory. The original file uses all the memory there is (including swap). I can send you that file, but it contains data not meant for everyone. On openSUSE 11.2 using OOo 3.2.0 it does not crash on crashoo.xls, but it does on the original file. This machine has 1.5GB on board + 1GB swap. Closing the file does not release the memory used.
On OOo 2.4 crashoo.xls only uses 33MB and loads a lot faster.
Now I have built my own version of OpenOffice.org from svn and it is working great. My version is OpenOffice.org 3.2.0 OOO320m12 (Build 9483) OOO320m12 is also the latest tag in svn. However the version from OpenSUSE is OpenOffice.org 3.2.0 OOO320m21 (Build 9319) built by Novell.Inc. (Build 3.2.0.7) is failing, so it looks to me Novell has reintroduced an old bug. I think the best thing is to report this issue to Novell.
confirmed. You can repro this using the koheiextref01 cws too.
Link to the downstream bugzilla page.
I'll keep this for now.
This shares the same root cause with Issue 107693.
To fix this, I have to fix Issue 109169 first.
BTW, in the interest of correctness >it looks to me Novell has reintroduced an old bug. This is not correct information.
Actually this can be fixed without waiting for Issue 107693.
Fixed in the koheiextref01 cws. http://hg.services.openoffice.org/cws/koheiextref01/rev/21c26773591b
Re-assigning to oc for verification.
Re-assigning to Yi Fan for verification.
Verified on SLED 11 sp1 and Windows xp sp3.