Bug 115337 - Crash in: ntdll.dll
Summary: Crash in: ntdll.dll
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: corruptProfile
Depends on:
Blocks:
 
Reported: 2018-01-31 16:30 UTC by Stephen Rose
Modified: 2018-02-26 11:01 UTC (History)
2 users (show)

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


Attachments
Requested registrymodifications.xcu (deleted)
2018-01-31 17:08 UTC, Stephen Rose
Details
test document (36.00 KB, application/msword)
2018-02-01 16:20 UTC, Stephen Rose
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen Rose 2018-01-31 16:30:35 UTC
This bug was filed from the crash reporting server and is br-aaaea9d0-924e-4404-b54f-4239e7e7dcae.
=========================================
Writer crashes while opening a relatively simple .doc file.  I can submit the file, but I'd rather not do this publicly.  This is a fresh default install of LibreOffice.  I am able to open the document in safe mode, oddly enough.  After the crash, I have to kill the LibreOffice process to use it again.
Comment 1 Julien Nabet 2018-01-31 16:46:45 UTC
For the test, could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Windows) and give a new try?
Comment 2 Stephen Rose 2018-01-31 16:55:22 UTC
I renamed cache, crash, and user to a subdirectory.  After that, I was able to open the file without problems.  I hope this helps.
Comment 3 Julien Nabet 2018-01-31 17:00:05 UTC
The main file is registrymodifications.xcu present in user subdirectory.

Your brand new profile contains a brand new registrymodifications.xcu

For the test, could you:
- close LO
- put again the former in registrymodifications.xcu in your user subdirectory
- try again

If it crashes, it means the pb is in registrymodifications.xcu. In this case, could you attach it?
Comment 4 Stephen Rose 2018-01-31 17:08:46 UTC
Created attachment 139469 [details]
Requested registrymodifications.xcu
Comment 5 Julien Nabet 2018-02-01 12:48:08 UTC
I'm a bit stuck because I retrieved your file and tried to open a random doc file found on Internet, I don't reproduce the crash but perhaps because I'm on Linux not Windows.
I suppose other people may help here.
Comment 6 Stephen Rose 2018-02-01 14:59:39 UTC
I am willing to send you the .doc file that causes this, if you like.  I'd just not like to post it publicly.  Would you like me to send it to you?
Comment 7 Julien Nabet 2018-02-01 15:02:51 UTC
(In reply to Stephen Rose from comment #6)
> I am willing to send you the .doc file that causes this, if you like.  I'd
> just not like to post it publicly.  Would you like me to send it to you?

What about removing old confidential/private part with a non corrupted registry file then give a try with the corrupted registry file.
If you still reproduce this with the file without confidential/private part, you may attach it directly.
If it's really impossible to remove confidential/private, feel free to send it to me on my private email.
Comment 8 Stephen Rose 2018-02-01 16:20:11 UTC
Created attachment 139506 [details]
test document

Here's a test document that I managed to create from the original file that caused the crash.  All personal information has been redacted.  This file causes the crash in a similar manner to the original file.  Does this point at the problem?
Comment 9 Xisco Faulí 2018-02-01 16:30:12 UTC
Hi Stephen,
using the document attached, it crashes for me if I open it from the navigator with a double click ( bug 115268 ) but it's not if the document is open inside LibreOffice.
Does it happen to you as well ?
Comment 10 Stephen Rose 2018-02-01 16:36:40 UTC
Yes, that's how it works for me as well.  I had not tried to open it that way before.  Up to now, I've been right clicking on the file and used the "open with" dialog.  I'm considering switching to LibreOffice as my main office suite, but I haven't pulled the trigger yet.  I assume that you're getting ready to call this a duplicate of that other bug.  Hopefully, this will help get it resolved.
Comment 11 Xisco Faulí 2018-02-01 16:39:36 UTC
Yes, let's close this as dupe of bug 115268. Anyway, thank you very much for reporting it and helping us to triage it.

*** This bug has been marked as a duplicate of bug 115268 ***
Comment 12 Xisco Faulí 2018-02-26 11:01:31 UTC
The content of attachment 139469 [details] has been deleted