I just realized this bug has nailed me, too! And boy is it a floozy! But until now, I had just assumed it was somehow my fault. I've assigned a ton of RAM to the undo function, allow undos to be written to disk, and set the option to remove undo states starting at the oldest one. Yet it has still happened to me. I hope this gets fixed!