I've not experieced the "major" problems others attest to, but I can say that the SED memory management is, to put it mildly, "weird"...

I open up SED 1.2.8, and it has a un-stable footprint of 13 meg. Left alone, this footprint slowly rises. IT shouldn't.

But here is the weird part. I left SED open last night for about 12 hours and the footprint this morning registers at 1.3 megs...ten times less!!!

And of course, the "fast type" issue is still there. If you type normally, you'll get about 8 to 10 percent CPU usage on SED...by comparason, notepad and word only use less than 4% under the same circumstance. If you type fast, SED jumps up to 50 or 60% CPU usage...notepad and word barely make it to 10%.

I've tried this same thing on the beta 1.3.0f and the same behaiviour is there, including a 15 Meg footprint upon opening which also slowly rises.

I've not experienced major problems, but there is definitely a bug(s) in there somewhere...