Apache OpenOffice (AOO) Bugzilla – Issue 111666
calc open excel 2003 xls save as 2003 xml fails
Last modified: 2021-03-02 09:09:14 UTC
start calc open budget.xls optionally save as budget.ods save as Excel 2003 XML budget2.xml program waits for 2-3 minutes messing with disk, then error dialog: "Error saving the document budget2. Write error. The file could not be written." balderdash! 300GB of space left no no file permissions problems. it took 2-3 minutes to do the save, so my only guess is it got stuck in a forever loop writing something and hit a 32-bit 2GB limit. that's about how long it takes to write 2GB. please make available a usable office 2007 format file export. the files are in a different format than the old .doc/ppt/xls
Created attachment 69489 [details] budet.xls, the offending excel 2003 file
removed URL so I don't have to use my web site
Reproducible with DEV300m77, ubuntu 9.10. Duplicate of issue 71689 ?
Created attachment 69497 [details] 1-sheet excel 2003 file with ifs and sums fails to export as excel 2003 xml. 2GB size problem?
Created attachment 69501 [details] sparse simple OOo excel 2003 xml output file untitled 6.xml
Created attachment 69502 [details] sparse simple OOo excel 2003 xml output file untitled 6.xml
Created attachment 69503 [details] untitled 6.ods, in case you wanted it VERY sparse simple spreadsheet
yes, same error as with the bug you found the duplicate of. but you will find more information and test cases/useful files in this bug report than there. I learned that smaller, simpler 4-entry spreadsheets do not have the problems that my 50-and 200-row spreadsheets did. so the problem has really big output for really small files. as I stated in the other bug report, it takes me 0 days, 00:01:25.593 to write a 2000000000 byte file. so multiply that by at least 2 minutes and you get a 4GB file minimum. that's about the size of a 32-bit unsigned int's maximum range. the actual elapsed time it takes to process my busget.xls file is 0 days 00:04:35.297 minus a few seconds. C:\t>prtime -exec createfile -s 2000000000 -f zapp filename=zapp filepath=zapp fillbyte=0x0. size=2000000000. Time estimate: 0 days, 0 hours, 1 minutes. double on a busy computer. Creating file, please wait... elapsed time: 0 days, 00:01:51.437 which is 2e9/(1*60+51.437)=17,947,360.392 bytes/second. at 4:35.297 minus about 5 seconds=4:30 here's the kicker: total file size is around 2e9/(1*60+51.437)*(4*60+30)=4,845,787,305.84 bytes which is close enough to the unsigned 32-bit limit 2^32=4,294,967,296 which is enough to make me suspect that OOo has tripped over an unsigned integer (int). If it were actually that limit, it would have taken 3:59.185 which is only 31 seconds off. this can be caused by the fact that I was running a very busy mcafee scan at the time and it was continually accessing the hard disk, so both programs were competing for disk writes. don't know which won the most time. so check your code base.
see 111780 for what I think is the cause of this problem.
Calc Rev. 1518439 not responding when save attachment 69489 [details] as xml. Win 7
Already reported *** This issue has been marked as a duplicate of issue 96852 ***