Bug 115444 - 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: Other Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-04 15:56 UTC by John
Modified: 2018-02-05 17:06 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John 2018-02-04 15:56:30 UTC
This bug was filed from the crash reporting server and is br-a6953ff5-5fd7-4c92-86d6-317835c4144c.
=========================================

I opened a file for reading then closed it OK.  A few seconds later, I tried to re-open the same file and the crash occurred.

My processor is Intel Core i5-3330.  I have 6.0 GB of memory (5.87GB usable). I am running Windows 10 (Home), version 1709.
Comment 1 Julien Nabet 2018-02-05 07:39:59 UTC
Could you take a look to https://wiki.documentfoundation.org/QA/FirstSteps ?

1) Try to rename your LO directory profile? (see https://wiki.documentfoundation.org/UserProfile#Windows)

2) Since it may be linked to OpenGL, try to upgrade your graphic card driver
If it crashes, you can try to disable OpenGL for the test

If it still crashes, would it be possible you attach the file?
Since it'll be made automatically public, don't forget to remove any confidential/private from it.
Comment 2 John 2018-02-05 12:29:31 UTC
I have renamed my LO Directory Profile and will monitor to see if the problem returns (copied files from autocorr & autotext to the new profile; also recreated dictionaries (by inserting text in a new file then running spell checker)).
I am not using OpenGL.

I have not had the problem again.

John
Comment 3 Xisco Faulí 2018-02-05 17:06:11 UTC
Hi John,
I think you got the crash because you reopen the document from the windows explorer. This has been reported already in bug 115268.
Thanks for reporting the issue anyway.

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