Subject: Re: bug#46293: Windows 10: emacs freeze on kill emacs

From: Eli Zaretskii <[email-masked]>
Date: Thu, 04 Feb 2021 17:21:07 +0200

> Date: Thu, 04 Feb 2021 10:00:55 GMT
> From: [email-masked]
> 
> If an file name is used, which is obviously invalid for some operations,
> the following can happen:
> 1. The file gets opened anyway, although an error message states
> otherwise:
> - File exists, but cannot be read
> - File mode specification error: (file-error Unlocking file Invalid argument
> //collaboration.dummyname.com@SSL/DavWWWRoot/subjects/foo bar.docx)
> 2. Trying to close the buffer triggers simmilar errors
> 3. Trying to exit emacs leads to a question wheter the file shall be saved.
> - Selecing No now again leads to similar error message, but now emacs also freezes (is unresponsive and
> GUI is no longer updated).
> - Emacs must be killed via task-manager.

Thanks, but we need a more concrete test case to see what happens in
these cases and how to fix that.  Could you please provide a full
detailed recipe to reproduce this starting from "emacs -Q"?