(continued)OK, now when you have some clues of possible root-causes, what's next ?#1.If you believe you found a memory leak, first of all, do not panic. Be patient to identify if this is a true leak or a false positive. For that:#2. Use efficient memory checking tools (Intel Parallel Inspector XE, Valgrind, etc).#3. If you want to exclude custom memory allocator, be sure...
(continued)Having discussed possible symptoms, now let's try to understand their possible root-causes.1. True leaks.When developing in native (C/C++) code you may just forget to free allocated memory. This can be for example:a. Something as simple as such:{ char* p = (char*)malloc (1 * 1024); //do work... //free (p); //will never forget to uncomment this later}b. Architecture design deficiency. Unclear object ownership, management of...
There often appear posts on the Open CASCADE forum, either as questions or as blames that there are persistent memory leaks. Truth to be told, this happens on many forums of other software products I visited, so this is not something OCC-specific.So I'd like to shed some light, which would hopefully help someone to understand the issue in the future. As always, extensions...
