JSON Tools crashes Notepad++ on launch

[jmccay-work]

System information:
Notepad++ v8.6.4 (64-bit)
Build time : Feb 20 2024 - 00:12:59
Path : D:\Program Files\Notepad++\notepad++.exe
Command Line : "D:\software\notepad++\plugins\Release_x64\DSON UDL.xml"
Admin mode : ON
Local Conf mode : OFF
Cloud Config : OFF
OS Name : Windows Server 2012 R2 Datacenter (64-bit)
OS Build : 9600.21620
Current ANSI codepage : 1252
Plugins :
ComparePlugin (2.0.2)
MarkdownViewerPlusPlus (0.8.2)
mimeTools (3.1)
NppConverter (4.6)
NppExport (0.4)
XMLTools (3.1.1.13)

Unfortunately, it is hard to get the actual crash information.

[jmccay-work]

I should note the crash happens on startup of Notepad++.

[molsonkiko]

I'm sorry you're having this issue! I can't replicate this with my local installation, so my current questions are:

• Have you tried upgrading to the latest version of JsonTools? Some previously reported crash bugs were fixed by upgrading to a newer version of JsonTools.
• Have you had this issue with JsonTools on Windows 10 or 11? I suspect this issue may be related to the fact that you're using Windows Server 2012 R2 Datacenter, and while I'm currently in the process of trying to test that, I haven't done so yet. EDIT: I started a Windows Server 2012 R2 VM instance, installed a normal (AppData) installation of Notepad++ 8.6.4 and JsonTools v7.1, and I didn't observe any crashes or other unusual behavior.

[daniel-tomsu-fnt]

Happens to me every day, but only when I exit Notepad++,, just installed again the latest version of the plugin again: https://github.com/molsonkiko/JsonToolsNppPlugin/releases/download/v8.3.1/Release_x64.zip

on Notepad++ 8.8.1 with Windows 10 & 11, no admin account

[molsonkiko]

@daniel-tomsu-fnt

Thanks for reporting this issue, and my apologies. I have not observed this with any recent release, but I will see if I can replicate and fix it.

[daniel-tomsu-fnt]

any success reproducing the error, can I support? The error is annoying, because it will prevent windows from shutdown.

[molsonkiko]

@daniel-tomsu-fnt
Sorry, I'm still unable to replicate this issue. I try very hard to stress test my plugin before every release, so if I knew what caused the issue you described, I would have already fixed it.

I only can test the plugin on my home machine, although a year or so ago I did spin up a Windows Server 2012 R2 Datacenter instance on Azure and try installing and running JsonTools on the instance, and I didn't observe any unusual behavior. Because Azure is ludicrously expensive, I deleted the instance soon afterwards and have no intentions of creating a new one.

Unfortunately, this issue can probably only be fixed by somebody like you who has actually experienced the bug.