Bug 115352 - Crash if I open a Writer Document by double-clicking the file
Summary: Crash if I open a Writer Document by double-clicking the file
Status: RESOLVED DUPLICATE of bug 115268
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.0.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-31 21:15 UTC by blmorgan1
Modified: 2018-02-01 17:14 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["ntdll.dll"]

Attachments
Procdump for soffice.bin (4.25 MB, application/octet-stream)
2018-02-01 15:27 UTC, blmorgan1 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description blmorgan1 2018-01-31 21:15:03 UTC 
Description:
When opening a file by finding it w/in file system and double-clicking, LibreOffice crashes w/ a report similar to: http://crashreport.libreoffice.org/stats/crash_details/d7493e69-adaa-46e9-95ef-eb80fdbef7c7

Steps to Reproduce:
1. Find LibreOffice writer file (*.odt) and double-click to open (LibreOffice must not be open on PC)
2. LibreOffice will start, file will open, then program crashes

Actual Results:  
Program crash like report:  http://crashreport.libreoffice.org/stats/crash_details/d7493e69-adaa-46e9-95ef-eb80fdbef7c7

Expected Results:
Allow me to edit the document.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Workaround is to open LibreOffice Writer first, then use file > open to open file.  Double-click also works if LibreOffice is already open.


Help/About info: 

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



User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36
Comment 1 Xisco Faulí 2018-01-31 21:18:12 UTC 
Hi,
Thanks for reporting the issue.
It seems to be a duplicate of bug 115268

*** This bug has been marked as a duplicate of bug 115268 ***
Comment 2 Mike Kaganski 2018-02-01 09:30:38 UTC 
well... the call stack is very different from bug 115268 - but there's a similarity in that there's Python involved (thread 15 here - but here the Python thread had been successfully created; and the call stack is deep). Not sure if it's a dupe actually or not.
Comment 3 Mike Kaganski 2018-02-01 09:36:24 UTC 
Also ~all crash reports from the http://crashreport.libreoffice.org/stats/signature/ntdll.dll for v.6.0.0.3 share this property of having a Python thread with deep call stack.
Comment 4 Mike Kaganski 2018-02-01 09:53:02 UTC 
@blmorgan1@gmail.com: as you have a reliable reproducer, could you please create a procdump - using directions like these:

https://blogs.technet.microsoft.com/kristinw/2012/10/03/procdump-how-to-properly-gather-dump-dmp-files-for-crashes-and-hangs-cpu-spikes-etc-including-gathering-perf-data-for-exchange-issues/

like in the bug 115286; the procdump allows to load it into debugger and see the program memory state at the moment of the dump.

Please note that the procdump includes memory of the process, so please avoid opening files that contain sensitive information. If possible, use specially created (blank?) test files to create the dump.

Thanks.
Comment 5 Mike Kaganski 2018-02-01 10:11:51 UTC 
(In reply to Mike Kaganski from comment #4)
> like in the bug 115286

Sorry for misspelling - should have been bug 115268
Comment 6 blmorgan1 2018-02-01 15:27:34 UTC 
Created attachment 139501 [details]
Procdump for soffice.bin

Here is the procdump output when soffice.bin terminates.
Comment 7 Mike Kaganski 2018-02-01 17:14:27 UTC 
Yes, definitely a duplicate. Which means, that fixing one fixes the other.