<![CDATA[SQLinForm x64 crashes with N++ 8.5.5]]>Hello,
my SQLinForm Plugin (64bit) crashes with N++ 8.5.5 (64bit).
SQLinForm Plugin (64bit) works fine with N++ 8.5.4 (64bit)
SQLinForm Plugin (32bit) works fine with N++ 8.5.5 (32bit)

The Plugin is written in C# using the NppPluginNET

Any idea what could be the reason for the crash in N++ 8.5.5 (64bit) and where I could start identifying the reason for the crash?

REgards
GuidoMarcel

]]>https://community.notepad-plus-plus.org/topic/24810/sqlinform-x64-crashes-with-n-8-5-5RSS for NodeFri, 10 Jul 2026 23:25:57 GMTFri, 11 Aug 2023 22:41:20 GMT60<![CDATA[Reply to SQLinForm x64 crashes with N++ 8.5.5 on Mon, 14 Aug 2023 19:19:16 GMT]]>@rdipardo @Alan-Kilborn it looks like there is a fix now available. https://community.notepad-plus-plus.org/post/88610

Thanks for all your feedback!

]]>https://community.notepad-plus-plus.org/post/88612https://community.notepad-plus-plus.org/post/88612Mon, 14 Aug 2023 19:19:16 GMT<![CDATA[Reply to SQLinForm x64 crashes with N++ 8.5.5 on Mon, 14 Aug 2023 05:42:14 GMT]]>@rdipardo thanks! This sounds as it could be related to my issue. Just wondering how I could change this CETCOMPAT Flag myself.

Guido

]]>https://community.notepad-plus-plus.org/post/88593https://community.notepad-plus-plus.org/post/88593Mon, 14 Aug 2023 05:42:14 GMT<![CDATA[Reply to SQLinForm x64 crashes with N++ 8.5.5 on Mon, 14 Aug 2023 03:51:01 GMT]]>

Have a look at https://community.notepad-plus-plus.org/post/88577.

One more thing to note: the commit that @Fruchtzwerg94 mentioned also enabled large address awareness for x64 builds of N++. There’s a classic post on Stack Overflow explaining how that can pull the rug out from under third-party DLLs, which suddenly have to cope with 64-bit pointers.

It should be irrelevant if the only faulting DLL is 64-bit, which obviously addresses memory with “large” ordinals all the time. In fact the new build option is supposed to be enabled by default for 64-bit targets.

But then there’s the whole .NET Framework to think about. The C# plugin template is basically a 32-bit module, with some “support” for x64 bolted on rather recently.

]]>https://community.notepad-plus-plus.org/post/88589https://community.notepad-plus-plus.org/post/88589Mon, 14 Aug 2023 03:51:01 GMT<![CDATA[Reply to SQLinForm x64 crashes with N++ 8.5.5 on Mon, 14 Aug 2023 02:22:18 GMT]]>@Guido-Thelen said in SQLinForm x64 crashes with N++ 8.5.5:

I will need probably more info from other plugin-users to identify the real issue.

Have a look at https://community.notepad-plus-plus.org/post/88577.

]]>https://community.notepad-plus-plus.org/post/88587https://community.notepad-plus-plus.org/post/88587Mon, 14 Aug 2023 02:22:18 GMT<![CDATA[Reply to SQLinForm x64 crashes with N++ 8.5.5 on Sun, 13 Aug 2023 20:29:51 GMT]]>@Alan-Kilborn said in SQLinForm x64 crashes with N++ 8.5.5:

There actually can be different versions of 8.5.5. What makes a notepad++.exe unique is its Build time.

BTW, this would only actually happen because of the “release candidate” versions of Notepad++. Each RC for a specific version has the “real” version number on it (in case it is proven out and actually becomes the release).

]]>https://community.notepad-plus-plus.org/post/88578https://community.notepad-plus-plus.org/post/88578Sun, 13 Aug 2023 20:29:51 GMT<![CDATA[Reply to SQLinForm x64 crashes with N++ 8.5.5 on Sun, 13 Aug 2023 20:26:23 GMT]]>@Alan-Kilborn , thanks for this hint. The Build Time of N++ did not change in-between. Then this proves that a miracle happened ;-)
I will need probably more info from other plugin-users to identify the real issue.

]]>https://community.notepad-plus-plus.org/post/88575https://community.notepad-plus-plus.org/post/88575Sun, 13 Aug 2023 20:26:23 GMT<![CDATA[Reply to SQLinForm x64 crashes with N++ 8.5.5 on Sun, 13 Aug 2023 11:12:53 GMT]]>@Guido-Thelen said in SQLinForm x64 crashes with N++ 8.5.5:

Maybe there was a new version of N++ 8.5.5 published in the meantime.

There actually can be different versions of 8.5.5. What makes a notepad++.exe unique is its Build time. So if you are really suspecting something like what you mentioned, have a look at that in your and your user’s debug info.

]]>https://community.notepad-plus-plus.org/post/88564https://community.notepad-plus-plus.org/post/88564Sun, 13 Aug 2023 11:12:53 GMT<![CDATA[Reply to SQLinForm x64 crashes with N++ 8.5.5 on Sun, 13 Aug 2023 08:35:57 GMT]]>@rdipardo Many thanks for your answer. Indeed I can’t reproduce the error anymore myself. The error was reported by one of the plugin users and Friday I was able to reproduce the error. But now, after re-installing N++ 8.5.5 again from fresh the error seems to have disappeared. Maybe there was a new version of N++ 8.5.5 published in the meantime.

Regards
Guido

]]>https://community.notepad-plus-plus.org/post/88560https://community.notepad-plus-plus.org/post/88560Sun, 13 Aug 2023 08:35:57 GMT<![CDATA[Reply to SQLinForm x64 crashes with N++ 8.5.5 on Sat, 12 Aug 2023 21:08:54 GMT]]>Without access to the source code, the only reply anybody can make will be a shot in the dark.

The most I can say is that it’s not reproducible in the following environment:

Notepad++ v8.5.5   (64-bit)
Build time : Aug  7 2023 - 18:44:22
Path : C:\Users\Public\Downloads\npp.8.5.5.portable.x64\notepad++.exe
Command Line :
Admin mode : OFF
Local Conf mode : ON
Cloud Config : OFF
OS Name : Windows 10 Pro (64-bit)
OS Version : 22H2
OS Build : 19045.3324
Current ANSI codepage : 65001
Plugins :
    mimeTools (2.9)
    NppConverter (4.5)
    NppExport (0.4)
    SQLinFormNpp64 (6.23.3.24)
]]>https://community.notepad-plus-plus.org/post/88553https://community.notepad-plus-plus.org/post/88553Sat, 12 Aug 2023 21:08:54 GMT