Bug 100289 - Sporadic crashes within MSVCR120.dll
Summary: Sporadic crashes within MSVCR120.dll
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.1.3.2 release
Hardware: x86 (IA32) Windows (All)
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace
: 101418 108340 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-06-09 11:47 UTC by Yuriy Chudnovskiy
Modified: 2019-12-27 03:28 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
Backtrace (178.54 KB, text/plain)
2016-06-09 11:47 UTC, Yuriy Chudnovskiy
Details
another backtrace with page heap with traces (10.94 KB, text/plain)
2016-09-23 09:22 UTC, Timur
Details
another backtrace with page heap and MSVCR120.dll (23.99 KB, text/plain)
2016-09-23 09:42 UTC, Timur
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yuriy Chudnovskiy 2016-06-09 11:47:56 UTC
Created attachment 125570 [details]
Backtrace

I'm not sure when the crash is occurring and aware of a reason, but this crash repeats about once per day of active work.
More strange, crash occurs only on one computer, while on other LO works fine.

Hardware: AMD socket AM1 system, integrated video card Radeon R3, 2GB RAM, hdd.
Software: M$ Windows 8.1, Firefox, LO.

I'm tried to take backtrace of a crash but not sure it is useful. WinDbg was running under user rights. I forget to set symbols path for this user, so first analyze is a trash. After this, I set symbol path and tried to analyze again, but get symbol error again. I set 'reload' checkbox at symbol path dialogue, and it seems to work for third analyze attempt.
If it is still unusable - I can wait for new crash, running WinDbg under administrator rights.
Comment 1 Buovjaga 2016-06-11 14:25:23 UTC
Do you have this enabled: Tools - Options - LibreOffice - View - Use OpenGL for all rendering?
If yes, what is the content of your C:\Users\User\AppData\Roaming\LibreOffice\4\cache\opengl_device.log

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the information.
Comment 2 Yuriy Chudnovskiy 2016-06-13 07:58:55 UTC
OpenGL, and even OpenCL are both disabled completely. That options do not matter.
BTW, this crash is not LO version depended. Occurs at least 5.0.x and maybe 4.x.x
Now running WinDbg under admin rights, waiting for another crash.
Comment 3 Julien Nabet 2016-07-04 20:19:43 UTC
Also you may upgrade to recent LO 5.1.4.
Comment 4 mahfiaz 2016-08-10 11:22:57 UTC
*** Bug 101418 has been marked as a duplicate of this bug. ***
Comment 5 mahfiaz 2016-08-10 11:28:19 UTC
Marking this as new since two people have reported it.

Bug 101418 added the following debug info:

here is the event log at the time of crash

Faulting application name: soffice.bin, version: 5.0.6.3, time stamp: 0x572b0738
Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f7ce6
Exception code: 0x40000015
Fault offset: 0x000a7676
Faulting process id: 0x11ec
Faulting application start time: 0x01d1ec89a52027e3
Faulting application path: C:\Program Files (x86)\LibreOffice 5\program\soffice.bin
Faulting module path: C:\Windows\system32\MSVCR120.dll
Report Id: 973998d0-58bb-11e6-be60-28924accd45e


-	System
		-	Provider
			[ Name] 	Application Error

		-	EventID	1000
			[ Qualifiers] 	0

			Level	2

			Task	100

			Keywords	0x80000000000000

		-	TimeCreated
			[ SystemTime] 	2016-08-02T14:15:41.000000000Z

			EventRecordID	6689

			Channel	Application

			Computer	PC-28217.out.co.za

			Security
	 
-	EventData
			soffice.bin
			5.0.6.3
			572b0738
			MSVCR120.dll
			12.0.21005.1
			524f7ce6
			40000015
			000a7676
			11ec
			01d1ec89a52027e3
			C:\Program Files (x86)\LibreOffice 5\program\soffice.bin
			C:\Windows\system32\MSVCR120.dll
			973998d0-58bb-11e6-be60-28924accd45e
Comment 6 Aron Budea 2016-08-10 11:55:37 UTC
Setting severity to critical, as it's a crash.
Comment 7 Timur 2016-09-23 09:22:51 UTC
Created attachment 127571 [details]
another backtrace with page heap with traces

I don't know if attached backtrace with salhelper3MSC.dll is of some use, I got it with LO 5.2.1.2 while testing page heap with traces. 
I attach here because I think it's the same as error message: Fault Module Name:	MSVCR120.dll,   Fault Module Version:	12.0.21005.1. 
Version is not clear to me, if I look in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\12.0\VC\Runtimes\x86, that's that version, but if I open Add/remove Programs, it says version 12.0.30501.0.
Comment 8 Timur 2016-09-23 09:42:06 UTC
Created attachment 127572 [details]
another backtrace with page heap and MSVCR120.dll

I hope attached backtrace with MSVCR120.dll can be of some use.
Comment 9 robert 2016-09-29 12:23:40 UTC
Start Calc, close it, boom...

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	soffice.bin
  Application Version:	5.2.2.2
  Application Timestamp:	57e399d1
  Fault Module Name:	MSVCR120.dll
  Fault Module Version:	12.0.21005.1
  Fault Module Timestamp:	524f83ff
  Exception Code:	40000015
  Exception Offset:	0000000000074a46
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	2057
  Additional Information 1:	ac68
  Additional Information 2:	ac6812545a2a9ff74f0a033c081e9227
  Additional Information 3:	c044
  Additional Information 4:	c04444acacd3004eb07e59c4e22a174a

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt
Comment 10 Julien Nabet 2016-09-29 13:33:24 UTC
(In reply to robert from comment #9)
> Start Calc, close it, boom...
>...
For the test, could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Windows) and give a new try?
Indeed, your problem might be unrelated.
Comment 11 Caolán McNamara 2016-10-03 20:07:32 UTC
The original crash was a crash on attempting to create a tooltip window. I rather suspect we are running out of window handles under Windows, i.e. we are leaking handles somehow
Comment 12 Timur 2017-07-26 09:07:08 UTC
*** Bug 108340 has been marked as a duplicate of this bug. ***
Comment 13 Julien Nabet 2018-01-29 15:32:19 UTC
Any better with last stable version 5.4.4?
Indeed, lots of leaks have been fixed meanwhile (at least concerning gdi)
Comment 14 Julien Nabet 2019-05-29 13:57:18 UTC
Could you give a try to last LO version 6.2.4?
There have been lots of fixes about resource leaks since about 3 years
Comment 15 QA Administrators 2019-11-26 03:32:22 UTC Comment hidden (obsolete)
Comment 16 QA Administrators 2019-12-27 03:28:37 UTC
Dear Yuriy Chudnovskiy,

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-FollowUp