Notepad++ 8.8.8 release
-
@Sinsearach said in Notepad++ 8.8.8 release:
Just updated after quite a long while, and on Windows 10, TextFX (NppTextFX2) plugin will not work …
It might be that it was caused specifically by Notepad++ v8.8.8… but more likely, it’s a setup issue on your side, or a bug in the plugin as it relates to your setup and v8.8.8.
But there needs to be some debug work, so I will duplicate your post to a separate Topic in Help Wanted (I will crosslink this post
to there in a few minutes: new post here), and the discussion can happen there, until we can prove whether it’s really a bug/regression in v8.8.8, or whether it’s just something that should be handled by fixing something on your side, or by fixing something in the plugin itself.
Update: Wait, you said “after quite a long while”, so that means it wasn’t just v8.8.8 that you had the problem with. Please only use the “Notepad++ x.y.z release” announcement topics for changes between immediately-previous version and this version. For example, this v8.8.8 topic should only mention regressions that changed behavior between v8.8.7 and v8.8.8. Any other problems you find when you jump from v8.1.5 (for example) to v8.8.8 should go in “help wanted”, and if can be confirmed as a bug in Notepad++, we will direct you on where to put in the official bug report. But it’s not an immediate regression with v8.8.8, so doesn’t belong in this discussion.
-
I auto-upgraded from 8.8.5 to 8.8.8 64bit about a week ago and today I experienced very high and persistent (ongoing) CPU load caused by NPP in a Windows 10 VM. NPP caused 18% load on a 6 core VM, i.e. full single-core load. The NPP user interface was very unresponsive, but I managed to close it normally (using the X in top right).
I had 40 files open, mostly JavaScipt files, but also some JSON, JSON-Lines, HTML and SVG files. Also a large yarn.lock file, maybe cause by this one.
I have a bunch of plugins installed, but didn’t try to turn them off:
Compare 2.02
HEX-Editor 0.9.12
JSTool 1.2502
Mime tools 3.1
Npp Converter 4.6
NppExport 0.4Downgrading to 8.8.5 solved the issue for me, but I wanted to let you know there is an issue somewhere.
-
Yes we are seeing this in our Enterprise install testing of the MSI. We had to build a script to uninstall the executable and then install the MSI. And package the scrip & MSI in an Intune package. Seems to have solved the problem.
-
D donho referenced this topic on
-
I have noticed going from the executable to the MSI, when installing from Intune, that remnents of the old version get left behind.
Also, when we deployed 8.8.8 and the program updates to 8.8.9 that it doesn’t clean up and you see two versions.
These are registry entries which should have been cleaned up in both events. I probably should have stuck with the original executable. 😕
-
@Andrea-Gaviraghi More results from allowing updates on MSI package. The 8.8.8 MSI pulls the update from Notepad++ and it then installs the 8.8.9 executable. So again, the computer shows 2 installs, when only the newest is really installed. This process should be a lot cleaner…
