test for memory leak?
Hi, as mentioned in a previous thread, I've been overriding new operator to understand the use of the memory api both in duneuro-bst and in duneuro in general. So far the new new operator isn't covering all cases and thus this is just some ideas.
- I've seen a bid difference between memory allocated and memory deleted so far. I need to work more on this.
- Because of 1, ive seen how the memory of the whole OS behaves when having subsequent hundreds of calls to duneuro-bst and the accessible memory does in fact get reduced every call. However this can happen for other reasons.
- There are hundreds of memory allocations and deletes in the program. Perhaps a more unified access to memory would help to actually make the application run faster.