Description: A regression I've seen in 6.0 RC2 and RC3 since stable 5.4 on Windows is if LibreOffice Writer or Calc isn't already opened and you double-click a word doc or excel spreadsheet to open it, Writer/Calc will open properly and display the file but immediately hang. LibreOffice Base being open doesn't appear to matter, only the supporting Writer or Calc itself. I initially thought this was related to network files or file synchronization apps but have been able to reproduce on files stored locally on Windows 10. Environment: Windows 10 1709 64 bit LibreOffice 6.0 32bit RC2 and RC3 Note that this never happens if appropriate Writer or Calc is already opened. This doesn't happen on LibreOffice 5.4.x OpenGL enabled/disabled has no effect. Tested on multiple Windows 10 workstations on multiple networks with multiple doc and xls files, though appears to happen more on certain files. I'll attach an example. Steps to Reproduce: 1. Be sure LibreOffice is closed 2. Try to open a file through Windows Explorer either by double click, or right click>open dialog 3. Note file opens, but high chance LibreOffice will hang if you attempt any mouse clicks. Sometimes LibreOffice opens a crash report dialog. Actual Results: LibreOffice gui hangs, sometimes crashes immediately with a crash report dialog. Expected Results: Should work fine as previous versions. Reproducible: Sometimes User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 6.0.0.3 Build ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU threads: 8; OS: Windows 10.0; UI render: GL; Locale: en-CA (en_CA); Calc: group User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0
Created attachment 139400 [details] example word doc
Confirmed in Versión: 6.0.0.3 Id. de compilación: 64a0f66915f38c6217de274f0aa8e15618924765 Subproc. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; Configuración regional: es-ES (es_ES); Calc: group
Not reproduced in Versión: 6.0.0.1 Id. de compilación: d2bec56d7865f05a1003dc88449f2b0fdd85309a Subproc. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; Configuración regional: es-ES (es_ES); Calc: group
Reproduced in Versión: 6.0.0.2 Id. de compilación: 06b618bb6f431d27fd2def25aa19c833e29b61cd Subproc. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; Configuración regional: es-ES (es_ES); Calc: group thus, regression introduced in range https://cgit.freedesktop.org/libreoffice/core/log/?h=libreoffice-6-0&qt=range&q=d2bec56d7865f05a1003dc88449f2b0fdd85309a..06b618bb6f431d27fd2def25aa19c833e29b61cd
Ah, this is weird. I can't reproduce it in Version: 6.1.0.0.alpha0+ Build ID: facfc2951ea9f4745edd4a6fb1cf97697f33f40a CPU threads: 1; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2018-01-13_23:29:02 Locale: es-ES (es_ES); Calc: group
I can't reproduce it in Version: 6.0.0.1.0+ Build ID: c66fc64e49353144a204743f900191443dbff5a1 CPU threads: 16; OS: Windows 6.3; UI render: default; Locale: en-GB (en_GB); Calc: group using the bibisect-win32-6.0 repository
@Mike, might it be related to https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-6-0&id=ca893ce3e4da351576e0d57caada57da190773f2 ?
(In reply to Xisco Faulí from comment #7) > @Mike, might it be related to > https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-6- > 0&id=ca893ce3e4da351576e0d57caada57da190773f2 ? No, definitely not...
Cannot reproduce with Version: 6.0.0.3 (x64) Build ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: ru-RU (ru_RU); Calc:
@Rodney, Do you reproduce it with http://dev-builds.libreoffice.org/pre-releases/win/x86_64/LibreOffice_6.0.0.3_Win_x64.msi ??
Crash report: crashreport.libreoffice.org/stats/crash_details/e1eb9f17-2250-4ace-b731-de62f8780666
@Jan-Marek, the crash thread in http://crashreport.libreoffice.org/stats/crash_details/fa25e85b-9799-41b4-bb28-06320a67a6b0 goes through the timer code. Could it be related to https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-6-0&id=794b6bf95f0dc2cff2b9d04651e8d14529f2f518 ?
(In reply to Xisco Faulí from comment #10) > @Rodney, > Do you reproduce it with > http://dev-builds.libreoffice.org/pre-releases/win/x86_64/LibreOffice_6.0.0. > 3_Win_x64.msi ?? I can yes, it appears just as consistent for me with the 64 bit build. Version: 6.0.0.3 (x64) Build ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU threads: 8; OS: Windows 10.0; UI render: default; Locale: en-CA (en_CA); Calc: CL
Is there a way to reproduce this without having to use windows explorer and right-click menu? (ie. having to install LO)
Created attachment 139419 [details] windows procdump of 64 bit writer hang
Hi Mike, Could the root cause be the same as in bug 115268?
*** Bug 115352 has been marked as a duplicate of this bug. ***
*** Bug 115365 has been marked as a duplicate of this bug. ***
*** Bug 115337 has been marked as a duplicate of this bug. ***
I've also started hitting this bug on Writer 6.0.0.3 (64-bit, official release) on W10 1709 64-bit. There were no issues at all on 5.4 or earlier. I did create an new profile for installing 6.0 (I do that on every major release -- 4.x, 5.x, 6.x) I've had crashed opening from explorer (mostly) with the program closed with ODT documents, as well as creating new files from templates within the program (from the start center).
And here is my crash report log: http://crashreport.libreoffice.org/stats/crash_details/c2a80db8-90d3-4442-b6ef-bbdf68d9297f
I can also confirm this. I use VirtualBox with Win 7 64-Bit Version: 6.0.0.3 (x64) Build-ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU-Threads: 4; BS: Windows 6.1; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group http://crashreport.libreoffice.org/stats/crash_details/62e091c6-701d-449e-a5b2-68c578565a3a My case is a old "Microsoft Write" file from the 90ies. I attach it.
Created attachment 139534 [details] affected doc in "Microsoft Write" format (README.WRI)
Following observation is maybe interesting: If I open this README.WRI, Writer suggests the charmap "Western Europe (Windows-1252/WinLatin 1)" If I click okay, it crashes. If I choose the charmap like "International (DOS/OS2-500), Writer won't crash. (Okay, now is the text no readable anymore. But at least Writer did not crash) May it helps? Some reports: crashreport.libreoffice.org/stats/crash_details/89eb8862-dcfd-4671-b60c-f3d05fb18280 crashreport.libreoffice.org/stats/crash_details/4c96def6-9d08-418f-834c-22e2e7b2bb81
*** Bug 115444 has been marked as a duplicate of this bug. ***
I confirm the crash with the readme.wri attached to this bug. Here is the crash report: crashreport.libreoffice.org/stats/crash_details/9b405a5b-765b-4e57-a89d-eaf2922a7522
(In reply to Rodney from comment #1) > Created attachment 139400 [details] > example word doc (In reply to Mike from comment #23) > Created attachment 139534 [details] > affected doc in "Microsoft Write" format (README.WRI) Repro both with Win 7 64-bit. Version: 6.0.0.3 (x64) Build ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU threads: 4; OS: Windows 6.1; UI render: default; Locale: fi-FI (fi_FI); Calc: CL In a Win 10 VM, I could only repro the .wri crash and Xisco said the crash sig is the same as in bug 115500
The crash should be fixed in https://dev-builds.libreoffice.org/daily/libreoffice-6-0/Win-x86_64@62-TDF/crashfix/. Could anybody with win x64 confirm it ?
(In reply to Xisco Faulí from comment #28) > The crash should be fixed in > https://dev-builds.libreoffice.org/daily/libreoffice-6-0/Win-x86_64@62-TDF/ > crashfix/. > Could anybody with win x64 confirm it ? Both files stopped crashing. Win 7 64-bit Version: 6.0.1.0.0+ (x64) Build ID: 1a915a3f2906b005770de982c78bfccb21913273 CPU threads: 4; OS: Windows 6.1; UI render: default; Locale: fi-FI (fi_FI); Calc: CL
same as for bug 115500 crash signature, duped this to bug 114815 as well With 2018-02-08 6.0 crashfix build [1] unable to reproduce. =-ref-= [1] https://dev-builds.libreoffice.org/daily/libreoffice-6-0/Win-x86_64@62-TDF/crashfix/ Version: 6.0.1.0.0+ (x64) Build ID: 1a915a3f2906b005770de982c78bfccb21913273 CPU threads: 4; OS: Windows 10.0; UI render: GL; Locale: en-US (en_US); Calc: CL *** This bug has been marked as a duplicate of bug 114815 ***
This build has resolved the problem for me.
Do we have a 32 bit windows build to test as well?
(In reply to Rodney from comment #32) > Do we have a 32 bit windows build to test as well? Yes, we do now -> https://dev-builds.libreoffice.org/daily/libreoffice-6-0/Win-x86_64@62-TDF/crashfix/LibreOffice_6.0.1.0.0_Win_x86.msi
32 bit windows build appears to be working fine as well. Thank you