XLS File Crashes LibreOffice for One User on One Computer but Not Others

We have one computer/user that is having problems with a particular XLS file. When the user tries to open it, it crashes LibreOffice. From then on, the document recovery tries to run when you open the file, but neither cancelling it nor letting it recover ever fixes anything. If the file is e-mailed to someone else and opened with LibreOffice (same version) there is no problem. If the file is opened off the same computer with a different user, there is no problem. The issue is isolated to that user on that particular computer and that particular file. The user can open up other XLS files with no problems.

System Details:

  1. Win 7 Pro 64 bit
  2. LibreOffice

Attempted fixes that have not worked:

  1. Deleted all XML items dealing with “Recovery” from the user’s registrymodifications.xcu file
  2. Rename the file/move the file to a different location to try to trick LibreOffice into thinking it is a different file
  3. Fully uninstalled LibreOffice, deleted user’s AppData\Roaming\LibreOffice folder to remove all existing settings, cleaned registry/deleted temp files, and reinstalled LibreOffice

There are only two things I know left to try. One is to upgrade to version x64, but since attempted fix #3 didn’t work, I don’t see why upgrading would. The other is to save the file in a different format from a computer that can open the file; however, I’d rather not do that because we will probably switch back to Microsoft Office since we’ve had nothing but headaches since switching to LibreOffice.

Does anyone have any other suggestions on anything I can try?

New versions of LibreOffice habe many bug fixes. I would recommend to updated definetly. Second, experiment with enablimg/ disabling: OpenCL, Hardware Acceleration, OpenGL from Settimgs menu.

@Ljiljan, I will check.

Another possibility beside user profile problems could be an extension installed on the other computer that somehow interfered with this specific document. However, as a conversion to ODF .ods format helped, that’s the best cure :wink:

End result, I changed the file to an open document format. The user has not reported any additional problems.

This is very strange. One would think it was a LO profile problem but you have eliminated this.

It suggests that the spreadsheet is trying to use some link to an external program etc that is not present or corrupted in that users Windows account.

Does the spreadsheet contain anything other than simple data? Does it use any Macros or user defined functions?

You could try this. Get one of those who can open the spreadsheet to open it. Then create a new spreadsheet, copy the data from the problem spreadsheet to the new spreadsheet and save under a new name. this is efectively a new spreadsheet that contains the same data. Can it now be opened by the problem user?

Good suggestion. I’ve made a new copy of the spreadsheet by copy/pasting the data out of the old into a new document. It is literally the simplest type of spreadsheet possible, nothing but data and some row colors, borders, and font changes. As soon as I hear back from the user I’ll update on whether or not this worked.

Creating a new file from the data in the problem file did not work. The user has the same issue with the newly created file.

Did you find a solution to this problem?

UPDATE 2016.0519

@chdwck, your recent reply gives me some additional information – and with it, additional ideas and recommendations. Try these tests as well:

  1. Delete all but a few lines of data from the spreadsheet.
  2. If the client's computer can successfully work with the file from step 1, continue to increase the lines of data until you find the point of fail.
  3. Remove all borders, font changes, colors, etc. in the data set from step 2.
  4. If the client's computer can successfully work with this file, continue to add back these enhancements until you find the point of fail.
Working through these steps may help you pinpoint a problem with memory, graphics card, drivers, etc.

Here is another idea. I realize you used cut & paste to create a new file, but this COULD have picked up invisible trash hiding in some cell that COULD be causing the problem. Try this:

  1. Save/export to a CSV file.
  2. Open the CSV file with LO Calc.
  3. Save it as an ODS and see if your client's computer can successfully work with this file.

Working through these steps may help you to eliminate any stray trash hiding in the data cells.

Hope this helps.


@peterwt, perhaps I misunderstand your comment, but I don’t believe your approach will address any of the possibilities you suggest. You would certainly create a new spreadsheet file, but any call to an external app will not be changed and neither will any link or reference to an external file.

@chdwck, here is what I would recommend. A processor issue is my first suspicion. A Windows Registry error is my second suspicion. Try these steps:


  1. Save the XLS in ODS format using one of the computers that do NOT exhibit this problem (let's call it the "GOOD machine").
  2. Transfer the file to the computer in question (let's call it the "BAD machine").
  3. Open the file on the BAD machine and see if the problem is still present. If so, continue below.


  1. Install the most recent version of LO 32-bit on the BAD machine.
  2. Open the ODS file in LO 32-bit version.
  3. Test the BAD machine to see if the problem is still present. If so, continue below.


  1. Make sure the OS is up-to-date on the BAD machine.
  2. Inspect and clean the Windows Registry for the BAD machine. There are a lot of apps out there to do this. Do your research and get a credible one from a credible source.
  3. Test the BAD machine to see if the problem is still present. If so, continue below.


  1. Create a detailed hardware and software spec list for the BAD machine.
  2. Repeat the previous step for the GOOD machine.
  3. Compare the specs between the two computers. Note the differences. If possible, test to determine if any of the differences between the BAD machine and the GOOD machine could be causing the problem.

Because we don’t have a complete hardware and software spec list for your computers, and because we don’t have a copy of the spreadsheet in question to examine and test, any of the following could be possibilities:

  • A processor issue on the BAD machine.
  • A memory issue on the BAD machine.
  • A Windows Registry issue on the BAD machine.
  • A video card or driver issue on the BAD machine.
  • A call to an app that is not present or is corrupt on the BAD machine.

I hope the foregoing gives you some actionable food for thought. Good luck.

Please click the check mark next to the response you believe best answers your question.

As a note, I did run a registry cleaner (CCleaner) as part of what I have tried previously. That said, I will try to follow your instructions; however, a processor or memory issue ought to create more problems than just a single file. A corrupted driver could also be possible, but, again, there ought to be additional issues cropping up if that is the case. I will check it out and let you know.