Bug 115500 - Opening ODF Writer Text template (.ott) via OS file manager results in crash in: LngSvcMgr::GetAvailableGrammarSvcs_Impl()
Summary: Opening ODF Writer Text template (.ott) via OS file manager results in crash ...
Status: RESOLVED DUPLICATE of bug 114815
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.0.3 release
Hardware: All Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 115505 (view as bug list)
Depends on:
Blocks: Language-Detection 113314
  Show dependency treegraph
 
Reported: 2018-02-06 21:18 UTC by V Stuart Foote
Modified: 2018-02-08 07:20 UTC (History)
6 users (show)

See Also:
Crash report or crash signature: ["LngSvcMgr::GetAvailableGrammarSvcs_Impl()"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description V Stuart Foote 2018-02-06 21:18:59 UTC
This bug was filed from the crash reporting server and is br-d43245ee-d007-4af6-b284-e68d96a36af5.
=========================================

This is hitting an old try/catch break point. [1]

STR:

1. Create a Writer document holding a single table, add some column headings.
2. save as ODF Text Template --.ott, 
3. exit LO
4. from Windows Explorer file manager--double click on the new .OTT template

Expected: a new Writer document should open containing the table drawn from the template.

Result: LO launches, crashes, and immediately goes to document recovery for an untitled Writer docuemnt "untitled.odt"

Before repeating test, or returning to normal work, check Windows Task manager to ensure soffice.bin/soffice.exe has closed. If still running end the process tree.

=-ref-=
[1] https://opengrok.libreoffice.org/xref/core/linguistic/source/lngsvcmgr.cxx?a=true#1080
Comment 1 V Stuart Foote 2018-02-06 21:40:02 UTC
If LibreOffice is open to Start Center or to a Writer document--opening from the thumbnail view or the File -> Open menu respectively--seems to cause no issues with a new untitled document based on the template opening cleanly.

Is this a Template handling, or Language/Grammar detection issue?
Comment 2 V Stuart Foote 2018-02-06 21:48:55 UTC
880+ crashes against 6.0.0.3, with a few also against 5.4.3 and 5.4.4 builds

https://crashreport.libreoffice.org/stats/signature/LngSvcMgr::GetAvailableGrammarSvcs
Comment 3 Stephan Bergmann 2018-02-06 22:01:08 UTC
This looks very much like a duplicate of 114815.  As you seem to be able to reproduce the crash, can you check whether it is indeed fixed with a nightly containing that fix?
Comment 4 Xisco Faulí 2018-02-06 23:25:52 UTC
Surprisingly, all the crash reports in 6.0.0.3 started just 3 days ago, while it was released one week ago. Besides, all crashes seem to happen on Win 10.
Was win 10 recently updated?
Comment 5 Xisco Faulí 2018-02-06 23:31:05 UTC
I can't reproduce it 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
Comment 6 V Stuart Foote 2018-02-06 23:47:47 UTC
(In reply to Xisco Faulí from comment #5)
> I can't reproduce it 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

Had you made sure there is no soffice.bin/.exe running when double clicking on the .ott template? 

Also, it does seems spurious--about 1 in 4 on Wnidows 10 ver 1709 (16299.192) with

Version: 6.0.0.3 (x64)
Build ID: 64a0f66915f38c6217de274f0aa8e15618924765
CPU threads: 8; OS: Windows 10.0; UI render: GL; 
Locale: en-US (en_US); Calc: group

actually open when Windows Explorer has been closed and Task Manager verified the soffice.bin/.exe is not running...
Comment 7 Julien Nabet 2018-02-07 10:06:27 UTC
*** Bug 115505 has been marked as a duplicate of this bug. ***
Comment 8 Xisco Faulí 2018-02-07 19:42:14 UTC
@Stuart, which crash signature do you get if you try to reproduce bug 115268?

Another reason why I can't reproduce this crash is because it only happens on x64 while my vm is x86
Comment 9 V Stuart Foote 2018-02-07 21:23:37 UTC
(In reply to Xisco Faulí from comment #8)
> @Stuart, which crash signature do you get if you try to reproduce bug 115268?

Do not reproduce bug 115268 with OPs .DOC file

Windows 10 Ent 64-bit en-US with
/a install of Version: 6.0.0.1 (x64)
Build ID: d2bec56d7865f05a1003dc88449f2b0fdd85309a
CPU threads: 8; OS: Windows 10.0; UI render: GL; 
Locale: en-US (en_US); Calc: group

or a full install of Version: 6.0.0.3 (x64)
Build ID: 64a0f66915f38c6217de274f0aa8e15618924765
CPU threads: 8; OS: Windows 10.0; UI render: GL; 
Locale: en-US (en_US); Calc: group

But I do get a crash with 6.0.0.3 [1] with the .WRI file from cmnt #23 [2], giving the "LngSvcMgr::GetAvailableGrammarSvcs_Impl()" signature rather than the "take_gil" signature. Launch with swriter.exe from CLI.

And no crash using current master build
Version: 6.1.0.0.alpha0+ (x64)
Build ID: b1069ea6f25daa268eb4358d5ea20094b46ef347
CPU threads: 8; OS: Windows 10.0; UI render: GL; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-02-06_23:49:25
Locale: en-US (en_US); Calc: group

or the 6.0.0.1 build as above.

=-ref-=
[1] 
http://crashreport.libreoffice.org/stats/crash_details/7e446f58-f629-4b05-856f-2841fef1c72c
http://crashreport.libreoffice.org/stats/crash_details/47f2c229-93bc-4941-a052-116b472fe095

[2] attachment 139534 [details]
Comment 10 Xisco Faulí 2018-02-07 22:27:20 UTC
Setting to NEW... although it seems the root cause might be the same as in bug 115268 and hopefully fixed in https://cgit.freedesktop.org/libreoffice/core/commit/?id=5357ca82846ea7147ad61e9340f25647a5934eb0
Comment 11 Stephan Bergmann 2018-02-08 07:20:00 UTC
(In reply to V Stuart Foote from comment #9)
> But I do get a crash with 6.0.0.3 [1] with the .WRI file from cmnt #23 [2],
> giving the "LngSvcMgr::GetAvailableGrammarSvcs_Impl()" signature rather than
> the "take_gil" signature. Launch with swriter.exe from CLI.
> 
> And no crash using current master build
> Version: 6.1.0.0.alpha0+ (x64)
> Build ID: b1069ea6f25daa268eb4358d5ea20094b46ef347
> CPU threads: 8; OS: Windows 10.0; UI render: GL; 
> TinderBox: Win-x86_64@42, Branch:master, Time: 2018-02-06_23:49:25
> Locale: en-US (en_US); Calc: group

...which makes it ever more plausible that this has the same root cause as bug 114815

*** This bug has been marked as a duplicate of bug 114815 ***