Bug 141991 - libreoffice cause windows 10 crash APC_INDEX MISMATCH due probably to .lock file corrupted
Summary: libreoffice cause windows 10 crash APC_INDEX MISMATCH due probably to .lock f...
Status: RESOLVED DUPLICATE of bug 140952
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.1.2.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-30 12:17 UTC by pier andre
Modified: 2021-04-30 12:49 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
windows crash screen (109.67 KB, image/jpeg)
2021-04-30 12:19 UTC, pier andre
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pier andre 2021-04-30 12:17:30 UTC
Description:
On my laptop clicking on a libreoffice (version 7.1) file cause a windows 10 crash with
this informations:
Codice di interruzione: APC_INDEX MISMATCH (in english is interruption code)
Elemento che ha causato il problema: win32full.sys (in english is Element
that caused the problem)
this happens both in local files and in files in AFS network storage, also
if I open a working libreoffice file, libreoffice works but when I click on
the-non-working-file windows 10 crash, I checked that there aren't errors in
the disks.

In a previous post in:
http://document-foundation-mail-archive.969070.n3.nabble.com/libreoffice-crash-on-windows-10-related-to-a-lock-file-td4298039.html
I attributed this crash to a corrupted .lock file (the first times windows
said this).
Now it (the advice that a .lock file is corrupted) doesn't happen and
windows 10 crash brutally.

I also reset twice my Libreoffice user profile

1) The first solution I found has been to:
1.1) copy the "libreoffice-that-crash-windows file" in an USB stick;
1.2) open it in a linux laptop to see if it works;
1.3) change the filename;
1.4) copy the "libreoffice-that-crash-windows-new-name file" in the windows 10 laptop;
1.5) delete the old "libreoffice-that-crash-windows-old-name file";
1.6) delete the ".lock file" in the folder where the "libreoffice-that-crash-windows file" was and the ".lock file" in C:\Users\<user
name>\AppData\Roaming\libreoffice\4;
1.7) reboot windows;
and it works. (I tried also to delete only the .lock files but it didn't works)

2) I also copyed the "libreoffice-that-crash-windows-old-name file" and the
".lock-in-the-folde-where-the-file-was file" in a linux laptop, try to open
the "libreoffice-that-crash-windows file" and an advice popup saying:
"Document file 'libreoffice-that-crash-windows' is locked for editing by:
LAPTOP-NH65QF38/username-in-windows10(date and time)
Open document read-only or open a copy of the document for editing.
You may also ignore the file locking and open the document for editing."
and four buttons "Open Read Only" "Open Copy" "Open" "Cancel"
If I click "Open Read Only" it works
If I click "Open Copy" it works
If I click "Open" it works but delete the
".lock-in-the-folde-where-the-file-was file"

Yesterday with libreoffice (version 7.1.2.2) it happened again and I tried the same solution on windows 10 instead of linux; following the same steps as in 1) copying in an USB stick included

I don't know if the bug is in windows 10 or libreoffice but this doesn't
allow to use libreoffice easily in windows 10, it never happened in windows
7 neither in linux, and it's not good that libreoffice cause windows crashes :-).

is there a way to solve in a better way tha the one I used?

manythanks, ciao

Steps to Reproduce:
1.click on a libreoffice file
2.
3.

Actual Results:
windows 10 crashes

Expected Results:
no crash


Reproducible: Sometimes


User Profile Reset: Yes



Additional Info:
happens only in windows 10
Comment 1 pier andre 2021-04-30 12:19:35 UTC
Created attachment 171527 [details]
windows crash screen
Comment 2 pier andre 2021-04-30 12:22:06 UTC
I think the importance/severity of this bug should be chenged to critical or major
Comment 3 Mike Kaganski 2021-04-30 12:49:47 UTC

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