I'll try to catch it in the act.
There are usually three child processes of nw.exe running, and they mostly fluctuate from 50-90,000 KB each. I've seen them spike up to 4-500,000 KB when TiddlyDesktop is starting to slow down.
I tried exporting a .DMP file from Process Explorer just now (while TD is running like a champ), but in the absence of a crash there's nothing there I can view/read with my meager debugging tools. If you think that might be useful, I'll upload it here so you can have a look ... .
(Also, I have a Frankenstein monster file that I occasionally open to fish things out of. It likely has distorted macro calls and mangled code throughout, so I'm going to be careful NOT to open it with TiddlyDesktop, just to see if it's setting off the chain of events that bogs down TD.)