good to hear that.
the next release (7.7) will be code signed again.

a little warning: 7.7 is a major upgrade jump of the integrated scintilla editor engine, as well as the boost regex engine, so we expect some unknown issues yet to arise, while some others, depending on old engine’s issues, will be fixed.

many thanks and best regards.

I appreciate your ideas! I guess I will put my laptop away for now. Hopefully someone else has some ideas.

running out of ideas and it is already 01:00 here.
If no one else finds the culprit, I try thinking about it after a good sleep :-)
One last question for now, all the tests were done with the portable version, right?

By any chance, did you recently update/upgrade any driver (any, not only mouse driver) or antivirus software?

Document Map behaved when docked, but not after undocking it😔

I’m wondering, does this also happen when you are using two views and resize them?
Or any other docked window other than the find in result window?

could you try to resize the find result window and NOT to close it?
Does the error happen again?

is this a normal Windows 10 installation?
Meaning, it does NOT run under some virtualization environments like VirtualBox, Qemu, VirtualPC etc… ?
What kind of mouse do you use?
Did you install some mouse related driver software?

I’m still getting the error message in that version as well… Let me know what else you may need to figure out why this is happening. I appreciate it!

please try a separate portable version of notepad++, to see if an absolutely clean and isolated notepad++ would work on your system.

• download the notepad++ 7.6.6. 64 bit portable version from >>> here <<<.
  (the portable version does not require any installation and runs completely independent and isolated from your installed version. all custom settings, as well as any stuff you might want to try at the portable version, will not modify your installed version)

• extract npp.7.6.6.bin.x64.zip to your desktop.
  (copy npp.7.6.6.bin.x64.zip from your download folder to your desktop, right-click on it, select extract all from the explorer context menu, and press extract to extract it to a folder called npp.7.6.6.bin.x64)

• important note: make sure to close all instances of notepad++ that might be running, before starting the portable version at the next step, to be sure you are using the portable version for this test.

• open the extracted npp.7.6.6.bin.x64 folder and start this portable version by double-clicking on notepad++.exe inside this folder.
  (note: notepad++.exe will just be seen as notepad++, if you have enabled to hide all known file extensions at your explorer settings)

• retry with e.g. conducting a find all in current document search and closing your find result panel again.

does this portable version work as expected ?

best regards.

Unfortunately, I’m not good at debugging crash issues… especially ones I haven’t seen.

I’m hoping one of the others will be able to help you through debugging this.

Sorry.

Thank you for that. I took the changing the folder to .disabled and it still caused the issue. I went as far as doing the notepad++.exe -noPlugin option as well, and still, same results :(

Plugins : ComparePlugin.dll mimeTools.dll NppConverter.dll NPPJSONViewer.dll PoorMansTSqlFormatterNppPlugin.dll

I wonder if your problem is caused by the plugins. Could you try exiting Notepad++ and re-running using the notepad++.exe -noPlugin command line argument? (Alternatively, you could temporarily rename your C:\Program Files\Notepad++\plugins subfolder to C:\Program Files\Notepad++\plugins.disabled, and then re-run notepad++ normally).

When you disable plugins in one of those two manners, does it still crash on you?

If it still crashes, then the problem is with how Notepad++ interacts with your system, and someone with better crash-debug skills than I have will have to jump in. (I say “with your system”, because there are plenty of people here who have been using 7.6.6 for a month without such crashes.)

If it doesn’t crash when you’ve disabled plugins, then it’s (probably) one of the plugins that’s causing the problem, and we can help you though the steps of narrowing down which plugin it is that’s causing your instability.

Either way, let us know, and we can then help you with the next-steps.

would you mind showing us your debug-info?
Is available under the ? menu.

and I had to wait 20

There is no editing of postings, except for those with super-powers.

You should have no 20-minute delay now if you want to post further. That delay is a safeguard against scum-of-the-earth spammers.

And I love how I couldn’t edit my post to add this, since it was over 3 minutes… and I had to wait 20 to be able to post this reply…