Steps to Reproduce: 1. New Calc, A1=1, A2=2, A3="=A1+A2". Save 2. Reopen with Calc version 5.1.0.2. --> Hangs. 3. Reopen with OpenCL disabled. --> Works OK, file is open within 5 seconds. ---------- Broken in: Version: 5.1.0.2 (x64) Build ID: ecd3574d51754b043f865cf5bafee286d24db7cc CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; Locale: zh-CN (zh_CN) Win 10 X64 Works OK in: Version: 5.0.4.2 Build ID: 2b9802c1994aa0b7dc6079e128979269cf95bc78 Locale: zh-CN (zh_CN) ---------- opengl_device.log: DriverVersion: 9.17.10.4101 DriverDate: 1-30-2015 DeviceID: PCI\VEN_8086&DEV_0116&SUBSYS_21FA17AA&REV_09 AdapterVendorID: 0x8086 AdapterDeviceID: 0x0116 AdapterSubsysID: 0x21fa17aa DeviceKey: System\CurrentControlSet\Control\Video\{3D9DB5D3-20A3-46C3-92CC-E63F5370C130}\0000 DeviceString: Intel(R) HD Graphics 3000
Hello, and thank you for bringing this issue to our attention. Sadly, I was unable to reproduce the described behaviour. Have you tried resetting your profile < see: https://wiki.documentfoundation.org/UserProfile#Resolving_corruption_in_the_user_profile > already? This might fix all sorts of weird behaviours. Please let us know if this resolved the issue for you. Windows 7 Professional; Version 6.1 (Build 7601: Service Pack 1) Version: 5.1.0.2 (x64) Build ID: ecd3574d51754b043f865cf5bafee286d24db7cc CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; Locale: de-DE (de_DE)
Bug exists in new uses profile. Maybe this bug is specific to certain graphic driver?
@Michael Meeks: Hi, I'm unsure on how to proceed on this OpenGL related issue. Any advice how to handle it would be greatly appreciated.
Note that OpenCL and OpenGL are not related at all. Used for totally different things. And Calc does not use OpenCL for single formulas. I could not reproduce. Kevin, did you mean OpenCL, or did you actually mean OpenGL?
(In reply to Tor Lillqvist from comment #4) I mean Tools - Options - LibreOffice - OpenCL - Allow use of OpenCL.
Today I updated my Intel HD Graphic 3000 driver to version 9.17.10.4229 (through Windows Update), this bug behaviour does not show up any more. Also, bug 97132 does not show up after my graphic driver update. I add bug 97132 as see also.
(In reply to Kevin Suo from comment #6) Sorry, my mistake. Please ignore comment #6. This bug still exists, the graphic driver update does not solve this issue.
Unfortunately it hasn't been possible for me to reproduce the crash with master build. If possible, please follow the instructions provided at this link < https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg > and submit a backtrace.
Created attachment 122183 [details] windbg backtrace I have generated a backtrace file. Set to NEW.
@mmeeks: This is yet another "calculating wrong with OpenCL" report. Any estimate if, how and in what time frame it can be fixed on your side? As an interim measure I suggest to default the OpenCL option to disabled in all releases.
Kevin, a question: Is that "Intel\OpenCL SDK\2.0" I see in your windbg log some software you have intentionally installed, separately? How old is that? It seems that LibreOffice is using the OpenCL implementation in that Intel OpenCL SDK and not from your device drivers. It is in that code that the crash (or hang) is happening when you take the windbg backtrace.
Reading https://software.intel.com/en-us/forums/opencl/topic/531074 , it seems that "Intel OpenCL SDK 2.0" is from 2014. The current SDK seems to be called "Intel® SDK for OpenCL™ Applications 2016" and is from this year.
Kevin, if you run the clinfo command (on the command line), what does it output? Please attach.
Created attachment 122246 [details] Screenshot: Intel OpenCL SDK 2.0 on my OS > Is that "Intel\OpenCL SDK\2.0" I see in your windbg log some software you have intentionally installed, separately? How old is that? See attached, it seems that the "Intel SDK for OpenCL - CPU Only Runtime Package Version 2.0.0.37149" was installed when I was installing the Intel Driver Update Utility. > if you run the clinfo command (on the command line), what does it output? I run Windows 10, seems there is no clinfo command under windows.
(In reply to Tor Lillqvist from comment #11) > It seems that LibreOffice is using the OpenCL implementation in that Intel OpenCL SDK and not from your device drivers. > It is in that code that the crash (or hang) is happening when you take the windbg backtrace. That may be true, but how come it doesn't crash when I install version 5.1.0.1 on the same machine, with the same Intel OpenCL SDK?
> That may be true, but how come it doesn't crash when I install version > 5.1.0.1 on the same machine, with the same Intel OpenCL SDK? Obviously the calls made to OpenCL APIs and the parameters passed to them differ between LibreOffice versions. A driver or system level library, like OpenCL, is not supposed to crash, no matter if you pass it expected or bogus parameters. Can you figure out if this "OpenCL SDK 2.0" is just a misleading name, and the files in there actually are as new as you would expect, if you just installed fresh Intel drivers? Or are the DLLs in there, that show up in the windbg output, really from 2014? What happens if you install the "Intel® SDK for OpenCL™ Applications 2016" instead?
(In reply to Tor Lillqvist from comment #16) I uninstalled the Intel OpenCL SDK 2.0, then no hang anymore. i rerun the Intel Driver Update Utility installer but the OpenCL SDK 2.0 is not installed with it any longer. Not sure how it was installed previously.
So can we resolve this bug as NOTOURBUG then? (It would have been great to get enough information about the apparently buggy OpenCL implementation that you uninstalled to be able to black-list it, but too late now.)
(In reply to Tor Lillqvist from comment #18) > It would have been great to get enough information about the apparently buggy > OpenCL implementation that you uninstalled to be able to black-list it I will try my best to figure it out how the buggy OpenCL SDK 2.0 was installed. Mark as NOTOUTBUG for now.
As a remedial fix - I wonder if we could black-list all but the very latest intel OCL driver version(s) ? =)