Vince,
>Has anyone had any problems with memory leaks in fpw. How does go about checking for memory leaks and rectifying the situation if one is found
Yes.. The memory leaks I'm aware of had to do with menus. Typically what would happen was this: menus would be built pad by pad but released in one command. This caused memory to not get correctly reallocated into the memory pool and over some time you'd run out and have troubles. The fix was to individually release each pad in a reverse order to how you built them.
You might see how you are building and releasing menus.
There may be others but that's the one I'm aware of. Also, 2.6a may have fixed this.
Best,
DD
A man is no fool who gives up that which he cannot keep for that which he cannot lose.
Everything I don't understand must be easy!
The difficulty of any task is measured by the capacity of the agent performing the work.
