I want to start of this post by saying I HATE Windows 10, 22H2. Inkscape (and several other things) worked PERFECTLY under the 2016 release.

But alas, 22h2 seems to have issues with a lot of things, and this time around it's inkscape.

If I edit text with the text/font properties open (which I tend to leave open a lot) and get to typing fast, Inkscape just..... DISAPPEARS. Gone. No recovery, no autosave, no NOTHING. Just... boom. Gone.

If I CLOSE the fint and text properties (font selection window)  after picking a font, this problem goes away.

I thought about upgrading to the newest Inkscape, but under 22H2 I can't click on half the icons so.... that's an issue for another day/post.   For now, I've checked the bug list over on Git and I'm not seeing anything to do with this particular issue so I thought one of you might've run across it.

Before anyone asks: Yes I do have a bajillion fonts.  No I don't feel like swapping them in and out all the time. Yes they did work fine in 0.9 under Win 10, 2016 release.

I'm pretty sure this is a problem with how the new version of Win10 renders things versus Inkscape trying to preview text in 3500000 fonts. (Slight exaggeration there, but you know what I mean.)

Any help is truly, truly appreciated and I thank you in advance for any insight or clarity you can provide.

Cheers!

I'd give 1.2.2 a try.

(Reset the preferences and relaunch after any install.)

I'd give 1.3 a try.
The fontlist works better than in 1.2.2 on Win 11.

@TylerDurden Unfortunately I tried that FIRST.  That one does the whole "can't click on anything reliably" deal.

I'll try 1.3.  Thanks @Aero! ^_^

Will report back and let you know the result.

In the meantime, if anyone else is experiencing this bug the [WORKAROUND] is to close your font properties panel after selecting/applying your new font.

Cheers!

P.S. @TylerDurden  I forgot to say thank you for your input. While it doesn't work for me, it was in fact a legitimate suggestion and I appreciate it. 0.9 and 1.2 both do that whole" can't click on anything correctly" deal on this new OS install.  Win 10 22H2 has some weird issues.  It's also got that microsoft bug reported in 11 where Alt+tab is opening new explorer windows randomly from time to time. I think this is probably an OS-involved issue, but it'll likely be something the dev team has to at least deal with/address going forward. As a programmer: my condolences. ; )

Okay, so 1.3 does NOT crash while typing. It DOES, however, crash when scrolling rapidly through the fonts.
However, if you turn off the "font preview" option, it seems to fix that error.

(I filed a bug at GitLab about it, regardless. It seems like the handler for the font preview's getting overwhelmed if you scroll too fast, and pre-caching the samples could help.)

In the meantime, the workaround is:  [1.1.2]  Close the font & text properties window before you start typing, or [1.3]  Turn off fonts preview in preferences (I'm thinking this is the preferable solution, since A) It's  newer version, albeit an Alpha release, and B) Whatever works in this one will probably be baked into versions going forward.

Again, I have LOTS of fonts and I'm aware that's a thing with a lot of software, but the problem didn't occur under the 2016 release of Windows 10 so I'm hypothesizing it's to do with something Inkscape's making a call to in the new OS's rendering libraries.  Either way, it just does NOT like flashing several hundred font previews fast in 1.3, though the typing while Text&Font properties is open problem is gone.

I suspect 22H2 changes caused this because, again... worked fine before and this isn't the only thing to go haywire since installing it on these new machines.

Good news! There's a fix for this in Inkscape 1.3 courtesy of lb90 over at the Inkscape GitLab site.

https://gitlab.com/inkscape/inkscape/uploads/c5458fc07bdb441b974986c9d3ec8f7e/libpangowin32-1.0-0.dll