Answer to previous question regarding Task Mgr: "I don't know, yet." I haven't found anything strange going on so far, I continue to search. TM presents a wealth of "data." Turning it into "information" is a different task.
But, I do have one more tidbit, for what it's worth: It is not necessary to restart Windows to restore the normal speed ... ending and restarting the LBB IDE will do the trick. Strangely, not every window in the app is affected the same way. One in particular paints part and then stops, and finally paints the rest. It has maybe a half dozen text boxes, 7 or so radiobuttons, and 3 or 4 ordinary buttons. I've constructed much more complex windows and haven't had a problem. Work continues
Slowdown after repeated executions
Re: Slowdown after repeated executions
This sounds exactly like a run-of-the-mill resource leak. The practical solution is to quit and restart the LBB IDE if the slow-down gets annoying.
Re: Slowdown after repeated executions
Yes, it has all the characteristics of a leak. Exiting and restarting is fine, way superior to restarting Windows. Maybe I'll find some time to track it down ,K6DGW>