Description: Source LibreOffice Summary Stopped working Date 11/27/2016 4:46 PM Status Report sent Description Faulting Application Path: C:\Program Files (x86)\LibreOffice 5\program\soffice.bin Problem signature Problem Event Name: APPCRASH Application Name: soffice.bin Application Version: 5.1.5.2 Application Timestamp: 57989b31 Fault Module Name: igdrcl32.dll Fault Module Version: 20.19.15.4390 Fault Module Timestamp: 56c63332 Exception Code: c0000005 Exception Offset: 000686dd OS Version: 10.0.14393.2.0.0.768.101 Locale ID: 1033 Additional Information 1: 26e2 Additional Information 2: 26e2eaef136237d68c096d3856aec168 Additional Information 3: 9c02 Additional Information 4: 9c02287053e29b752c03719525027ff3 Extra information about the problem Bucket ID: 6545becd98f80799ea128acff2da5ecb (108349576363) Steps to Reproduce: 1.noticed in Windows 10 reliability monitor, app works properly 2. 3. Actual Results: not noticed Expected Results: none Reproducible: Sometimes User Profile Reset: No Additional Info: Source LibreOffice Summary Stopped working Date 11/27/2016 4:46 PM Status Report sent Description Faulting Application Path: C:\Program Files (x86)\LibreOffice 5\program\soffice.bin Problem signature Problem Event Name: APPCRASH Application Name: soffice.bin Application Version: 5.1.5.2 Application Timestamp: 57989b31 Fault Module Name: igdrcl32.dll Fault Module Version: 20.19.15.4390 Fault Module Timestamp: 56c63332 Exception Code: c0000005 Exception Offset: 000686dd OS Version: 10.0.14393.2.0.0.768.101 Locale ID: 1033 Additional Information 1: 26e2 Additional Information 2: 26e2eaef136237d68c096d3856aec168 Additional Information 3: 9c02 Additional Information 4: 9c02287053e29b752c03719525027ff3 Extra information about the problem Bucket ID: 6545becd98f80799ea128acff2da5ecb (108349576363) User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0
igdrcl32.dll seems to be related to the Intel OpenCL driver. As I can see, the driver is from February: http://www.geeks3d.com/forums/index.php?topic=4437.0 @Tor: could this be faulty driver and/or code, and some silent recovery because of that? Is there anything worth investigating right away, or upgrading to 5.2 should be the first step?
Ernie: please update to LibreOffice 5.2 and continue to monitor the appcrashes. Set to NEEDINFO. Change back to UNCONFIRMED, if the appcrashes persists with 5.2. Change to RESOLVED WORKSFORME, if they went away.
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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO 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 MassPing-NeedInfo-Ping-20170531
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-20170628