SlickEdit is hanging after my first paste from clipboard

[pbrightly]

Not sure why, or if something funky was in the clipboard. But late this afternoon, after I pasted something from (a wiki, I think), my editor window went opaque and I lost the ability to type. It was persistent after I shutdown slickedit and retried.  I shutdown before heading home. On boot at home, everything seemed fine. Until I pasted some text to a window.  Same. Any ideas how I can troubleshoot this?
Ha.  I just tried to copy my about window info and.. it hung for a bit, went to the background and did not go to the clipboard.
I'll screen cap it.  Oh. Second attempt worked.
SlickEdit Pro 2023 (v28.0.0.6 64-bit Qt5)

Serial number: WB303722
Licensed number of users: Single user
License file: C:\ProgramData\slickedit\28\slickedit.lic

Build Date: November 2, 2023
Emulation: SlickEdit (text mode edition)

OS: Windows 10 x64
OS Version: 10.00.0 
Memory: 37% Load, 12096MB/32471MB Physical, 15252MB/34519MB Page File, 4731MB/134217727MB Virtual
Shell Information: c:\windows\system32\wsl.exe --exec bash -il
Screen Size: 1440 x 2560 (4800 -329 1800 3200), 3840 x 2160 (0 0 3840 2160)

Project Type: Single file project - Python
Language: .txt (Python)
Encoding: ACP (1252)

Installation Directory: C:\SlickEditPro28.0.0\ (non-removable drive,NTFS,167597MB free)
Configuration Directory: C:\Users\374432897\AppData\Local\SlickEdit\28.0.0\ (non-removable drive,NTFS,167597MB free)
Migrated from: C:\Users\374432897\Documents\My SlickEdit Config\27.0.2\
Spill File: C:\Users\374432897\AppData\Local\Temp\slkspill.PaulBrightly.9388 (non-removable drive,NTFS,167597MB free)

[pbrightly]

And thus far, this morning... problem is gone. Hmm..  It's early. Will post back if/when it recurs and if I have more info.

[pbrightly]

OK, I think I figured out what was causing the problem (but maybe not the root cause).  If this is how to reproduce, not sure if it's worth fixing.

I force any text file in my notes directory to be treated as a config-file type (it gives me nice color compatible with bash snippets... allows me to put comments with #.. etc.

1. I edited my primary, generic notes.txt file, which is > 29k lines!
2. I'd pasted several openssl commands with bash variables embedded. Those are still at the top of the file
3. The problem manifested again after typing at the end o those snippets.  Screen went gray...
4. When I finally got focus back, on the command-line I entered fundamental-mode. Color went away. So did problem.

So... maybe a huge file trying to colorize/format/whatever choked the editor?  I'm going to archive the majority of this file and expect the problem to disappear for good.

[Clark]

By "config-file type" do you mean Bourne Shell?

[pbrightly]

No, if not an SE type, it's something I probably put together over the last 3 decades. I've used Slick for so long, it's hard to remember when I've done what. This is the config:

[Clark]

Ok. Sometimes the language type can have an effect on performance. For example, languages with a ####_proc_search() function have noticeably slower performance.

[pbrightly]

Agreed.  Without a huge file, there is no problem.  No need to address this, now that I understand it.  Thanks.

PS. Using a language type makes note-taking spectacularly productive and visually pleasing for comments, step-instructions and code snippets.  50% of that is simply colorizing #-comments and numbers.