I’ve taken the issue upstream, but even if NppPlugin.NET gets patched (a new version has been in pre-release for over a year), there’s no telling when/if the dependent plugins will upgrade. (At least the migration path looks easy enough.)

Don’t forget the x64 plugins that target .NET Framework, for example:

Good point and I’ve looked at some. I think (correct me if I’m wrong) the crash only manifests if you actually use a Scintilla call that would return a Sci_TextRange object and looking on Scintilla Docs, there seem to be only 2:

• SCI_GETTEXTRANGE
• SCI_GETSTYLEDTEXT

I checked my version of Markdown Panel and although the “bad” Scintilla interface code is there, the plugin never uses / calls it and in my daily use of Notepad++ (using the latest dev build) Markdown Panel has not crashed for me.

On the other hand, CsvQuery does crash Notepad++ and it does indeed make a getTextRange() call here and here. An issue has been opened.

I can’t speak for the rest as I don’t use them nor do I know C# programming in the least.

Cheers.

Don’t forget the x64 plugins that target .NET Framework, for example:

• CS-Script
• CsvQuery
• JSFunctionViewer
• Markdown Panel
• MarkdownViewer++
• NppGist
• WakaTime

These are based on a .NET plugin template that re-implements the Scintilla interface in C#.

Looking at the template code, it seems character ranges are defined using the int type:

  [StructLayout(LayoutKind.Sequential)]
  public struct CharacterRange
  {
      public CharacterRange(int cpmin, int cpmax) { cpMin = cpmin; cpMax = cpmax; }
      public int cpMin;
      public int cpMax;
  }

That will surely overflow as int is an alias for the Common Language Runtime’s Int32 type.