Bug 99380 - Calc crashes when switching to specific tabs or when saving
Summary: Calc crashes when switching to specific tabs or when saving
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.0.5.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: OpenCL
  Show dependency treegraph
 
Reported: 2016-04-18 18:46 UTC by Matthias
Modified: 2017-05-31 10:46 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
This document crashes LO (999.46 KB, application/vnd.oasis.opendocument.spreadsheet)
2016-04-18 18:46 UTC, Matthias
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias 2016-04-18 18:46:03 UTC
Created attachment 124478 [details]
This document crashes LO

The attached document crashes LO when you switch to the tabs "Bike", "Run", "Alternativ" or "Rolle". All other tabs work fine.

The attached document also crashes LO when you want to save the file. 
It also crashes LO when you want to save the file as xlsx.

The crash also occured with LO 4. I then switched to LO 5 but the problem is still there.
Comment 1 Julien Nabet 2016-04-18 19:18:00 UTC
On pc Debian x86-64 with LO Debian package 5.1.2, I don't reproduce this.

1) Could you try after having renamed your LO directory profile? (see https://wiki.documentfoundation.org/UserProfile#Windows)
2) Could you try to disable OpenCL? (see menu Tools/Options/OpenCL, uncheck both checkboxes)
3) Could you give a try to last stable LO version 5.1.2?

If you still reproduce the crash, could you try to retrieve a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace)
Comment 2 Usama 2016-04-18 19:24:05 UTC Comment hidden (obsolete)
Comment 3 Matthias 2016-04-18 19:36:24 UTC
The rename of the LO directory profile didn't solve the problem, but the
disablement of OpenCL worked just fine.

Thanks for the fast responsees.
Comment 4 Julien Nabet 2016-04-18 21:47:45 UTC
About OpenCL, it may be a pb with LO.
Could you check if there could be an update for your graphic card (since OpenCL uses it if I don't mistake)?
And still, a backtrace could be useful.
Comment 5 Michael Meeks 2016-07-14 13:17:22 UTC
Almost certainly an OCL issue - marking to the tracker. We've done a chunk of work recently to detect and disable OpenCL on first-start if the device changes - which should ensure that bad drivers are caught early, and CL disabled for them.

I'd love to get some feedback on a 5.1.5.1 build from you, when used with a clean profile.

Thanks !
Comment 6 How can I remove my account? 2016-07-28 07:58:47 UTC
Matthias, any news? Have you tried with more recent builds?
Comment 7 How can I remove my account? 2016-08-22 07:13:37 UTC
Matthias, unless you tell otherwise, we will assume this bug has been fixed by recent changes.
Comment 8 Alan Curtis 2016-10-14 22:11:01 UTC
This seems to be related to this thread - OpenCL is getting disabled when it should not be:

I am running on an iMac running OS-X El Capitan with an AMD Radeon R9 M390 and LO 5.1.5 and LO 5.2.2 disable OpenCL on opening  Trying to set OpenCL to true does not stick as it gets disabled on the next launch.  As a result, if I try to render a large PDF file it takes about 35 seconds.  

However, if I drop back to LO 4.4.7.2 OpenCL works fine, is not disabled, and the same document on the same machine takes 0.44 second to render.  This same behavior is repeatable on a MacBook running MacOS Sierra and an NVIDIA GeForce GT.
Comment 9 How can I remove my account? 2016-10-14 22:21:54 UTC
OpenCL has nothing to do with PDF export.
Comment 10 QA Administrators 2017-05-02 11:36:43 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2017-05-31 10:46:02 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20170531