Undo/Redo (CTRL+Z/CTRL+Y) behaves unexpectedly after a few hours (NppFTP, NPP 64-bit, Win11)
-
Hi everyone,
I’ve been a happy Notepad++ user for over 15 years. About a month ago, I switched to a new computer running Windows 11, and at the same time I did a clean install of the 64-bit version of Notepad++ instead of the previously used 32-bit version.
Since then, I’ve noticed an issue that seems to be affecting others too, based on posts I’ve seen here.
I mostly use Notepad++ to edit remote files via the NppFTP plugin — probably in 95% of cases. Everything works fine initially, including common shortcuts like CTRL + Z and CTRL + Y for undo/redo.
However, after a few hours of work, something strange starts happening: the undo/redo history gets messed up. Instead of undoing just the last change, CTRL + Z undoes large chunks of code — sometimes entire blocks or functions — but not all the way back to the file’s opening state. It feels like part of the change history is lost or corrupted. When I restart Notepad++, things work properly again for a while. So far, I haven’t been able to pinpoint any specific action or condition that causes the issue.
This never happened with the 32-bit version, using the same plugins and workflow.
Has anyone else experienced this? Any idea what might be causing it or how to fix it?
Thanks in advance!
Notepad++ v8.8.3 (64-bit)
Build time : Jul 9 2025 - 01:39:59
Scintilla/Lexilla included : 5.5.7/5.4.5
Boost Regex included : 1_85
Path : C:\Program Files\Notepad++\notepad++.exe
Command Line :
Admin mode : OFF
Local Conf mode : OFF
Cloud Config : OFF
Periodic Backup : ON
Placeholders : OFF
Scintilla Rendering Mode : SC_TECHNOLOGY_DIRECTWRITE (1)
Multi-instance Mode : monoInst
File Status Auto-Detection : cdEnabledNew (for current file/tab only)
Dark Mode : ON
Display Info :
primary monitor: 3840x2160, scaling 100%
visible monitors count: 1
installed Display Class adapters:
0000: Description - NVIDIA GeForce GT 1030
0000: DriverVersion - 32.0.15.7680
OS Name : Windows 11 Pro (64-bit)
OS Version : 24H2
OS Build : 26100.4652
Current ANSI codepage : 1250
Plugins :
CodeAlignmentNpp (14.1.107)
JSMinNPP (1.2503)
mimeTools (3.1)
NppConverter (4.6)
NppExport (0.4)
NppFTP (0.29.13)
QuickText (0.2.5.1)
WebEdit (2.7) -
I have often used 64-bit NppFTP, but I’ve never used it for hours at a time, so I don’t know for sure that it doesn’t have a memory leakage that would eventually corrupt the undo history… but given how popular that plugin is, it would surprise me if it did.
But you’ve got a few plugins in your Debug Info that I don’t have much experience with, and there are times when plugin X interferes obscurely with plugin Y.
I know that you likely have that list of plugins for good reason to help you with your workflow, but the best advice I have for you to debug the problem is to either start with just the NppFTP plugin, and see if it has the problem after a few hours; if so, then you have found the culprit, and can put in a bug report; if not, you can add one plugin at a time until the problem does arise. But that might make your workflow too unwieldly during the experiment, so maybe start with removing one at a time (which will thus hopefully only take one part of your workflow away at a time, which might be workable) – so, for example, have all the plugins installed except WebEdit (you can follow the directory-rename suggestion in this FAQ to disable one plugin without truly uninstalling it), then try it for a few hours: if it doesn’t crash, maybe it was WebEdit or some interfererence between that and another plugin; if it does crash, you know that WebEdit wasn’t the sole culprit, so you can re-enable it, then move on to disabling the next (for example, QuickText).
I know it’s not an ideal solution, since each experiment will at least partially inhibit, and each takes a few hours, and unless there is a crash, you won’t ever be truly sure you’ve tested it long enough. But it’s the best idea I can come up with to narrow things down.
-
@PeterKee said in Undo/Redo (CTRL+Z/CTRL+Y) behaves unexpectedly after a few hours (NppFTP, NPP 64-bit, Win11):
Has anyone else experienced this?
Sounds similar as the infamous GitHub issue #9426.
This never happened with the 32-bit version,
Oldest report there is for Notepad++ v7.9 (32-bit), so some users had it even for the 32-bit N++.
I fixed one such problem but users still report occasionally occurrences of it, so it’s clear that there should be more code to fix. Unfortunately, so far I could not reproduce (so cannot fix it…) and the users have not been able to describe 100% reproducible steps. So if you find such a STR, it will be great.
-
@xomx
Note, in above, STR means “Steps To Reproduce”. -
I fixed one such problem but users still report occasionally occurrences of it, so it’s clear that there should be more code to fix. Unfortunately, so far I could not reproduce (so cannot fix it…) and the users have not been able to describe 100% reproducible steps. So if you find such a STR, it will be great.
@xomx I don’t have a 100% foolproof way to reproduce yet, but if I use the “alt” key to highlight a chuck of text on multiple lines, then delete that section and continue working. The next time I “ctrl+z” to undo (no matter how long it’s been, right now it’s been about 15 minutes of working), it goes back to when I highlighted the chuck of text. I experience this more often than not when I use that method to select. It’s not 100% of the time, but it’s often enough that I can reproduce it if I try long enough.
-
@Justin-Goodell said in Undo/Redo (CTRL+Z/CTRL+Y) behaves unexpectedly after a few hours (NppFTP, NPP 64-bit, Win11):
use the “alt” key to highlight a chuck of text on multiple lines, then delete that section
Yep, there was that “alt” column mode +DEL undo regression (from N++ v8.8.9), some details & STR in the fix-PR:
https://github.com/notepad-plus-plus/notepad-plus-plus/pull/17307
The fix is in the already released v8.9 but due to some other problems in that version, it hasn’t been triggered for a N++ autoupdate (so if you wanna use it, you have to dl & run the v8.9 installer yourself).
@PeterKee
Do you also use N++ macros?Currently I’ve identified another such (this time a longstanding) bug in the N++ codebase (PR fix is still in progress, it’ll be hopefully in the next version, for a STR look here).
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login