Ah - how humiliating, that rather obscure option was indeed activated - turning it off solves the (literal!) window bloating.
There's no reason I can think of off the bat why I would be using that option, except awhile ago I was experimenting with SendMessageW calls via User32.dll (using the AutoIt Language) when reading the text from the edit portion of a combo-box, and for some unknown reason DF was causing nonsense characters to appear at the end of the allocated array (this did not happen on other machines or with DF disabled), so I must have thought to myself "Hey, I know, let's try this option that's guaranteed to make things even
more unstable!" (yeah, the things we do for fun).
Anyway, long story short, I never did discover why DF was interfering with the SendMessageW call, but I found an alternate workaround, and figured it would be way too esoteric a problem to raise on the forums, so the universe was at peace again. Except that I obviously forgot to de-select that rather grumpy rendering option, and it came back to haunt me.
So - no harm, no foul! Thanks for clearing that up - I'm reminded why my mum taught me to look both ways before crossing the street by myself.
(Something about
not leaving one's shoelaces experimentally un-tied comes to mind...)