Bug 51098 - FILESAVE: Crash while save-as MS Excel 200x
Summary: FILESAVE: Crash while save-as MS Excel 200x
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.5.5.3 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-14 15:07 UTC by Daniel
Modified: 2012-10-19 23:10 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
file with problem save as ms excel (229.17 KB, application/vnd.oasis.opendocument.spreadsheet)
2012-06-14 15:10 UTC, Daniel 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel 2012-06-14 15:07:12 UTC 
We use the attached chart file for a daily cash register in our company. This file is originally from from DATEV, a German Tax program. Every month i must convert this chart to Microsoft Excel 200x for the tax adviser.

After upgrading LibO from version 3.3(?) to 3.5.4 i can't save as MS Excel. LibO freezes and eating much RAM until it crashes.

Affected Versions, i have tested: Lib0 3.5.4 Linux and Windows, Lib0 3.6.0 beta 1 Windows.

OpenOffice 3.3.0 and 3.4.0 works fine.

Way to reproduce: Open the attached file in LibO 3.5.4 and try to safe as MS Excel 200x.

Thank you!
Comment 1 Daniel 2012-06-14 15:10:12 UTC 
Created attachment 63050 [details]
file with problem save as ms excel
Comment 2 Daniel 2012-08-15 12:58:01 UTC 
Now with release version 3.5.5.3 it is possible to save this file as 2003-xls. But the output-file have a size of 18 megabyte! (normally ~400kb). Version 3.5.5.3 still crash while save as 2007-xlsx.
Comment 3 Daniel 2012-08-29 22:20:14 UTC 
Seems to be fixed in Version 3.6.1. I will test it some days...
Comment 4 sasha.libreoffice 2012-09-21 06:29:36 UTC 
Thanks for bugreport
During reading this bugreport I was inspired on creating Bug 55174
Comment 5 Julien Nabet 2012-10-19 23:10:42 UTC 
On pc Debian x86-64 with 3.6 sources updated yesterday and a brand new LO profile, I don't reproduce this pb.

Daniel: Following my test and what you told on comment3, I put it as WFM. Don't hesitate to reopen if you can still reproduce this with a newer LO version (eg 3.6.2)