It is difficult to tell if this could be due to a memory leak. We have corrected a few issues that could have an impact since version 2.5.
I see to options to help you resolve this. First, you could use a memory profiler to discover if there are memory leaks, and if it is the case, have some kind of memory count when your application runs on a client machine, and analyze the memory consumption when the problem occurs.
The other option is to upgrade to the latest version (3.8), and see if you still reproduce the issue with this version. Note however that you may have to update your code to use updated features (some methods and properties have been marked as obsolete and replaced by new ones), to make sure the memory leaks have not followed in your application.
Imported from legacy forums. Posted by André (had 2163 views)