I have been struggling with the "memory lead" for months it is quite real and nasty. I have had TeamView sessions and endless support emails without any of this being mentioned. Everyday I have to reload the workspaces. Now I see it, found that one indicator triggered a "too many brushes" error in in the log and wow your posting is totally eye opening. Thanks so much. What a mess.
Many thanks, Sim22
No Comment
Thank you for the warning.
The most frustrating events for me are crushes and calling up in the log errors where compiling indicator does not show any issues. I am in the process (again) to reload everything from clean start - and NT support would not suggest nor admit there is any stability (as I call it) issue.
thanks
Thank you for the warning and instruction.
I am very disappointed with NT8 as those issues were not a problem with NT7.
My most common error is ..."not set to an instance of an object"
Even after compoling OK - after a whie comes up!
Now I use your suggestion in Point 3 - and always start with clean workspace, then load desired workspace.
It has reduced many issues, did not solve the one I described above.
Any suggestion?