Bug 149833 - LO Writer crashes immediately after opening
Summary: LO Writer crashes immediately after opening
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.3.4.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Skia
  Show dependency treegraph
 
Reported: 2022-07-03 23:06 UTC by olaf.schulze
Modified: 2022-08-10 14:55 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description olaf.schulze 2022-07-03 23:06:53 UTC
Description:
Writer 

Steps to Reproduce:
1.Starting LO Writer with a new document (or an exisiting file in Writer)
2.
3.

Actual Results:
LO crashs (closes) after a few seconds. No possibity writing or navigating in Writer in this time.

Expected Results:
Running


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
The problem only occurs with Writer. I tried to repair LO with a new installation.
Disabling hardware acceleration or restoring the user profile (manual and with the help wizzard/ safe mode) was not solution. 
But in the safe mode Writer runs/ works.
Comment 1 olaf.schulze 2022-07-03 23:28:55 UTC
report in the dump file in folder ...\AppData\Roaming\LibreOffice\4\crash:

ProductName=LibreOffice
Version=7.3.4.2
BuildID=728fec16bd5f605073805c3c9e7c4212a0120dc5
URL=https://crashreport.libreoffice.org/submit/
UseSkia=false
Language=de-DE
CPUModelName=AMD PRO A10-8700B R6, 10 Compute Cores 4C+6G   
CPUFlags=sse3 pclmulqdq monitor ssse3 fma cpmxch16b sse41 sse42 movbe popcnt aes xsave osxsave avx f16c rdrand msr cx8 sep cmov clfsh mmx fxsr sse sse2 ht fsgsbase bmi1 avx2 bmi2 lahf abm sse4a xop tbm syscall mmxext rdtscp
MemoryTotal=7252400 kB
Comment 2 Hossein 2022-07-04 18:27:36 UTC
More information is needed to understand the problem and eventually fix it. Could you please send a crash report?
<https://help.libreoffice.org/latest/en-US/text/shared/guide/error_report.html>

If you have already submitted a crash report, please provide its ID here, and that would help.

Is it possible for you to test older versions of LibreOffice, to see if this problem happens?
Comment 3 Timur 2022-07-04 19:26:03 UTC
likely a duplicate, but let's see. 

Please clarify if you tried both to start in save mode via Help menu and to rename LO user folder. 
Also paste Help-About and try to change ie turn off Skia, if in Tools-Options-View.
Also please write of you have anti-virus and try to run without it. 
If crash continues, and it's important if just with Skia or anyway, please use https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg to provide a backtrace for the crash.
Comment 4 olaf.schulze 2022-07-14 17:15:59 UTC
When starting in save mode, everything works fine. I did not rename the LO user folder nor the user name of windows 10. 

But when disableing the Skia, it works. In that case this bug report can be closed, I imagine the Skia problem is already noticed. Thanks again


just in case the output of Help->About

Version: 7.3.4.2 (x64) / LibreOffice Community
Build ID: 728fec16bd5f605073805c3c9e7c4212a0120dc5
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: default; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: threaded
Comment 5 Timur 2022-07-14 18:21:05 UTC
2 options here: to just close, or that we go after the cause. 
You should do 2 things then:
- test with LO daily master 
- get a backtrace
Comment 6 Julien Nabet 2022-07-26 09:39:10 UTC
Not sure if it's Skia or LO profile but could you upgrade to 7.3.5 and follow https://wiki.documentfoundation.org/QA/FirstSteps ?
Comment 7 Timur 2022-08-10 14:55:41 UTC
I close as Insifficient Data. 
Should you find some time to proceed, please:
1. upgrade to 7.3.last
2. test with LO daily master 7.5+ from https://dev-builds.libreoffice.org/daily/master/, it's separate to your working LO and doesn't take extensions
3. see steps for Skia test from bug 150111
4. get a backtrace peer https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg