Bug 87337 - EDITING: CALC crashes all opened spreadsheets
Summary: EDITING: CALC crashes all opened spreadsheets
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2014-12-15 17:01 UTC by Mateo
Modified: 2015-07-19 08:59 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Mateo 2014-12-15 17:01:09 UTC
I have been seeing reported crashes within CALC, andI haven't been able to pinpoint the reason.  User opens Outlook 2003, opens email(not preview mode) with an XLS attachment. User opens the attachment called "A", edits it, saves it as "B" out into their my documents.  They continue to work on "B" and all of a sudden, it crashes. When they try and launch spreadsheet "B" it wants to recover spreadsheet "A". I have heard that they were just sitting idle with it and it happens or while editing. This install is on a RDS environment Windows 2008 R2. I have wiped out their Libo folder in the user profile. Still happens. I also noticed that there will be files located in the Libo backup folder from days past as well as the the day the crash happens. It goes in spurts... No crashes and all of a sudden it happens several times in one day.Roaming profiles. Documents redirected to network server. Strangest clue:  I have about 150 users using LibreOffice on 7 different servers. It happens to  the same 12 people. 10 of them are on the same server. The other two are on two different servers. Different XLS files. I have not been able to reproduce. I only ever see the original crash message. Anything else to check?
Comment 1 Tim Lloyd 2014-12-15 21:06:34 UTC
Hi Matoe,

Thanks for all the detail. Can I just tie up some points which may help the devs?

RDS - Remote Desktop? Can you just give a bit more info pls? EG. user jumps on a Windows PC and remotely connects to Windows 2008 server? What client is being used?

Okay, the user is connected to the server and opens Outlook 2003 on that server.

- Open the email with attachment a.xls
- modify a.xls and save as b.xls (on the remote instance?)
- continue to modify b.xls. No open/close of that file - there is still the link to Outlook?

Comment 2 Mateo 2014-12-15 21:25:44 UTC
RDS..Remote Desktop Services.. also known as "Terminal Server".
Clients connect to it via a thin client which uses a built in RDP client.
They connect to the terminal server with a Windows login and get a windows desktop using MS Outlook 2003 with LibreOffice. Prior to Libre, they were using Apache OpenOffice.
They open spreadsheet "A.xls" and edit it and save it as "B.xls". This saving process makes A.xls become B.xls with the assumption that A.xls is now closed because it is no longer open. So they are now working on B.xls when all of a sudden it crashes.
The users are now manually saving the document so when this does happen, they will have the data up until they manually saved it. During the recovery process, the A.xls shows up in the recovery list to recover. They select it (inadvertantly because they don't know any different) and it fails. They go to the location of B.xls and open it and continue to work on it, manually saving in case this happens again.
Outlook opens attachments in a temporary location (users profile)so my guess is that it has a lock file somewhere for it even though it should be closed?? In Libre, it seems that when one Calc file crashes all crash so it is possible that A.xls opens in the recovery list and B.xls doesn't since they manually saved it?
Not sure.I hope this helps.
Comment 3 Tim Lloyd 2014-12-16 00:00:23 UTC
Thanks Mateo,

Some useful detail there for the devs to mull over.

Comment 4 Buovjaga 2014-12-16 11:28:11 UTC
I wonder, if it would be possible to get a backtrace of a crash: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
Comment 5 Matthew Francis 2014-12-18 15:20:14 UTC
Setting Status to NEEDINFO

As above, it would be very helpful if a backtrace could somehow be captured for this issue. Please let us know if there's any chance you could get hold of one using the linked instructions
Comment 6 Mateo 2014-12-30 17:55:16 UTC
I understand that a back trace might help, however, this process to debug is complex, never mind the fact that it is running on a terminal server where there are many users and many Libre Office processes per user running at the same time and the issue can't be reproduced. All I know for now is that my users didn't experience this issue when they had the latest or earlier versions of Apache Open Office(AOO) installed. They had been using AOO for almost 2 years without the recent issue that Libre has caused. Sorry to say. I really hope that 4.4.0 is not the same way.
Comment 7 QA Administrators 2015-07-18 17:36:16 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

This NEEDINFO message was generated on: 2015-07-18
Comment 8 Mateo 2015-07-19 01:57:13 UTC
I have since upgraded t0 4.3.6 and this problem seems to have been fixed.?? Please close.
Comment 9 Buovjaga 2015-07-19 08:59:45 UTC
Thanks for following up, I'll set to WFM.