bug : "{file} doesnt exist any more. Keep file in editor?"
-
its happened again, i killed the process as it had hung. re-opened it after a few minutes, then made some changes, saved the changes. then a bit later made another change and tried to save it, then it locked up, and shortly after it popped the dialog message up about “the file no longer exists, do you want to keep it in the editor”
it wouldnt let me save the file basically, and has locked up again, heres the contenbts of the log file you asked for2025-03-07 16:53:04 C:\code\fbpurity\builds\gm\fbpurity.user.js in Buffer::updateTimeStamp(), getFileAttributesExWithTimeout returned FALSE, its worker thread had to be forcefully terminated due to timeout reached!
2025-03-07 16:53:14 C:\code\fbpurity\builds\gm\fbpurity.user.js in Buffer::checkFileState(), getFileAttributesExWithTimeout returned FALSE, its worker thread had to be forcefully terminated due to timeout reached!
2025-03-07 16:53:38 C:\code\fbpurity\builds\gm\fbpurity.user.js in Buffer::checkFileState(), getFileAttributesExWithTimeout returned FALSE, its worker thread had to be forcefully terminated due to timeout reached!
2025-03-07 16:53:44 C:\code\fbpurity\builds\gm\fbpurity.user.js in Buffer::checkFileState(), getFileAttributesExWithTimeout returned FALSE, its worker thread had to be forcefully terminated due to timeout reached! -
@st333v i am regretting updating npp now. its definitely not the nppopenai plugin as im still getting the error. i knew there was a reason why i was holding off updating. i think ive had problems with updated versions of software before. maytbe i should downgrade to the previous version?
another datapoint. it seems to be going throught the “file does not exist, keep in editor” for each open file. its just going really slowly. after iclick “yes” on one dialog box, the system locks up for ages, then a few minutes later, the popup will show for the next open file, its going through them systematically… oh gosh, i think im going to need to either switch to a different editor or just downgrade to a previous version.
-
@st333v said in bug : "{file} doesnt exist any more. Keep file in editor?":
i should downgrade to the previous version?
You can, of course, whenever (if we do not solve your problem better, then use any version 8.7 or older).
@st333v said in bug : "{file} doesnt exist any more. Keep file in editor?":
the log file you asked for
Thanks. This confirmed my suspicion - your PC cannot answer the GetFileAttributesEx WINAPI call within a time-period given! This is very odd for any local file, as that system call is computationally inexpensive & fast (it usually can take few milliseconds to complete) and your filesystem cannot answer in 3 secs! I’ve seen some users report this problem before, but it was always with network files when the network was really slow or had outages.
Could you please test the same with a fresh N++ portable version (to rule out the possibility of corrupted/misconfigured N++ settings)? Just download 32-bit version here and unzip to any writable folder and run there the notepad++.exe.
-
@xomx i installed the portable version 8.7.7 and not had any problems so far. with it. but only have one file open.
is there a config file i can copy over from the installed version that will make it open all the files that i had opened, to make it a like for like comparison?
-
%APPDATA%\Notepad++\session.xml(copy it to the same dir where your portable notepad++.exe is). -
@xomx thanks, i will try it
-
@xomx after working ok for a couple of days. im just now getting the same problem with the portable version. i double checked it was the portable version by examining the properties of the process in the windows task manager.
-
@st333v i was going to give up and try out vscode, but found they dont support 32bit anymore, so have gone back to NPP 8.7 as recommended
-
@st333v said in bug : "{file} doesnt exist any more. Keep file in editor?":
after working ok for a couple of days. im just now getting the same problem with the portable version
Hmm, IMO it looks like the problem is somewhere on your comp (and not in N++, otherwise it could not work for few days ok and then not…). I bet on some antivirus like SW or corporate spyware or similar.
-
I just remembered similar “file does not exist” issue in the N++ v8.7.1+ caused by an interfering SW (in that case by the corporate telemetry spyware Teramind, monitoring all the files opened by user):
https://community.notepad-plus-plus.org/topic/26462/file-does-not-exist
