Bug 135119

Summary:	LO7.0 RC2: Crash loop (Writer) - Python/Lightproof related?
Product:	LibreOffice	Reporter:	Mike <bugzilla>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	bugzilla
Priority:	medium
Version:	7.0.0.1 rc
Hardware:	All
OS:	All
Whiteboard:
Crash report or crash signature:		Regression By:
Attachments:	Sandboxie logs after crash of Writer Sandboxie logs after another crash of Writer

Description Mike 2020-07-25 04:12:03 UTC

Description:
When I start Writer of LO7.0 RC2, I get a crash loop. Draw, Calc and Impress don't crash at start.
It did not help, that I restarted LO in safe mode (enabled "reset user profile" and "disable hardware acceleration").

When I start another LO app, like Draw, open the options, change the UI language and restart, I also get a crash. Because LO does not restart Draw. It always launches Writer at the restart (which will crash).

I started SWriter.exe with Sandboxie. Writer crashed and I saved the logs from sandboxie in a RAR. The logs contain Phyton scripts.
The foldernames of the log contain the names NVIDIA, Phython and Lightproof. I will attach the file.

Sometimes after a crash I get a loop at the start of LO. There is the LO logo and once the black progress bar below is full, the bar fills again (a loop, once a second). Then I have to kill soffice.bin with the task manager. The info below the LO logo says in German "Sources of extensions are checked".

Sandboxie's usage csv logged two things:
Document Type;Command;Count
TextDocument;.uno:UpdateInputFields;1

SBIE2224 Sandboxed program has crashed: soffice.bin [DefaultBox]
SBIE2101 OpenProcess (C0000022) access=001FFFFF initialized=1
SBIE2101 OpenProcess (C0000022) access=001FFFFF initialized=1

There are some reports of my crashes
https://crashreport.libreoffice.org/stats/crash_details/c4412838-7a02-4d2f-b3d1-585f7b58faaf
https://crashreport.libreoffice.org/stats/crash_details/b4df7f0b-827f-4ed0-ad94-9177d9ab5c29
https://crashreport.libreoffice.org/stats/crash_details/c7cde305-1ca9-4f5f-a383-8172cd470b39
https://crashreport.libreoffice.org/stats/crash_details/d58bec35-df0d-4c8f-b516-511c6f55c291
https://crashreport.libreoffice.org/stats/crash_details/8e1f275d-919d-42c3-8540-e2ca72f9c5b1

Steps to Reproduce:
1. Open Writer

Actual Results:
Writer crashs

Expected Results:
Writer does not crash

Reproducible: Always

User Profile Reset: Yes

Additional Info:
IMHO this issue could be a regression.
The crashing started after I updated from 6.4 to 7.0 RC2. Writer crashed right from the start.

Version: 7.0.0.2 (x64)
Build ID: c01aa64b6c3d89ebe5fe69c28c7adb24eb85249c
CPU-Threads: 4; BS: Windows 10.0 Build 18363; UI-Render: Skia/Vulkan; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: CL

Comment 1 Mike 2020-07-25 04:12:57 UTC

Created attachment 163498 [details]
Sandboxie logs after crash of Writer

Comment 2 Mike 2020-07-25 04:13:29 UTC

Created attachment 163499 [details]
Sandboxie logs after another crash of Writer

Comment 3 Mike 2020-07-25 04:37:46 UTC

Several of my crash reports refer to a source
C:\cygwin64\home\buildslave\source\libo-core\cppu\source\uno\copy.hxx:65

I have no such c:\cygwin64\ folder on my system

Like in this report
https://crashreport.libreoffice.org/stats/crash_details/bb335cee-3cb5-4425-83e6-7d0a90795cf6

Comment 4 Mike 2020-07-25 05:41:46 UTC

A crash report from a boot process loop (with the LO logo shown), that I got after I started Impress

https://crashreport.libreoffice.org/stats/crash_details/9e4edda6-8631-426b-b381-d4b57f41e021

1. I start Writer
-> Writer crashs
2. I start Impress
-> Impress offers document recovery
3. I dismiss
-> Boot loop, task manager shows 5 - 6 tasks: 1 or 2 are simpress.exe, 4 are soffice.bin, one soffice.bin task has a CPU load of 38 - 52 percent and 188 MB RAM, the others LO related tasks use almost no CPU and RAM resources.
4. Kill this soffice.bin
5. Start Impress again
-> works

Comment 5 Telesto 2020-07-25 07:11:17 UTC

Sometimes after a crash I get a loop at the start of LO.

-> You launch manually I assume. Problem s previous process isn't killed

Comment 6 Mike 2020-07-25 19:13:02 UTC

I edited the file "registrymodification.xcu" in the user profile and now Writer starts without problem.
I followed my gut feeling and changed "IsUseDictionaryList" to 'false'. Writer started. I opened the xcu again. It was changed back to 'true'.
Pure luck, but every dog has it's day. :)