Crash upon opening any file after a manual upgrade from 184.108.40.206
I’m trying to upgrade a ‘custom’ N++ install for a repo
I’ve upgraded from 220.127.116.11 to latest (boycott) release
It starts well, but after opening any file (even the readme.txt), it crashes
The Event Viewer tells me it dumps some data in ProgramData, what can I share?
Also debug info:
Notepad++ v8.3 (64-bit)
Build time : Feb 3 2022 - 03:39:05
Path : E:\src\svn\Notepad++\notepad++.exe
Command Line :
Admin mode : OFF
Local Conf mode : ON
Cloud Config : OFF
OS Name : Windows 10 Pro (64-bit)
OS Version : 2009
OS Build : 19042.1466
Current ANSI codepage : 1252
Plugins : AutoSave.dll DSpellCheck.dll Explorer.dll LanguageHelp.dll mimeTools.dll NppConverter.dll NppExec.dll NppExport.dll NppFTP.dll NppJumpList.dll nppplugin_solutionhub.dll nppplugin_solutionhub_ui.dll nppplugin_svn.dll NppTaskList.dll NppToolBucket.dll PythonScript.dll QuickText.dll XMLTools.dll _CustomizeToolbar.dll
I know this isn’t much but I don’t know what files to look at and give here ^^’
With -noplugin no issue, I’ll be looking into plugins then
It was NppTaskList; after updating it to lastest, it was even crashing the software upon starting up, even with no file opened…
Yes. It was known during the v8.2.2-RC process, and the subsequent v8.3 full release, that the change that was made for 8.2.2/8.3 would affect plugins. The initial tests showed only a handful, but as time went on, more plugins have proven to be affected by the change. Unfortunately, it’s up to the individual plugin authors to make fixes – and not all plugins are actively maintained.
(The fact is, the change to the plugin API was a change that should have been made back when Notepad++ originally went to having both a 32bit and 64bit version – and if it had, then all the plugins would have made the update at the same time they went to supporting 64bit plugins. Instead, because this change was overlooked way back then, it’s now causing a problem. But there’s no good way to implement this necessary change without affecting plugins.)
It was NppTaskList; after updating it to lastest
Excellent troubleshooting ++!
As @PeterJones says above it’ll take some time for plugin authors / maintainers to update. In the meantime, if you find issues, kindly report them to the plug-in authors on their respective issue pages. That would help a lot.
Just a bit of news;
I’ve submitted a pull request and it got merged in with a version bump, so it’s available to all through the Plugins Admin!