Tyrsis
20-Nov-2005, 07:53 AM
Hi,
Have been using eurekalog for awhile now and am glad we use it. That being said we recently ran into a problem that would cause the call stack in the exception logger to break. Basically what we discovered that was happening was that there were memory leaks in the application that were causing us to eventually just run out of memory. This is above and beyond typical memory manager fragmentation (we use fastMM), and just blocks of memory that we had neglected to free.
That being said, the old standard of using Memproof has become impossible since it really does have problems these days with delphi 2005. We did manage to find a freeware component that we could compile in and it would give a good indication of where the leaks were, but it made me think that since eurekalog already does stack traces, perhaps you should think about adding memory leak logging to it as well. Since eurekalog is already great for debugging, it would also be good if it could catch memory leaks as well (since it's already compiled in to all our apps).
Anyway, just a suggestion, though probably a large undertaking.
There is a freeware component that does this memory leak checking that we use at: http://v.mahon.free.fr/pro/freeware/memcheck .. it works pretty well but it uses TD Debug info which adds a HUGE size to the exe. I believe it uses this in order to get a stack trace to locate the leaks. Perhaps by looking at this source you could get an idea of how hard it would be to add similar functionality to eurekalog if you were ever considering it? It would be a valuable debugging option!
Jay Macaulay
Have been using eurekalog for awhile now and am glad we use it. That being said we recently ran into a problem that would cause the call stack in the exception logger to break. Basically what we discovered that was happening was that there were memory leaks in the application that were causing us to eventually just run out of memory. This is above and beyond typical memory manager fragmentation (we use fastMM), and just blocks of memory that we had neglected to free.
That being said, the old standard of using Memproof has become impossible since it really does have problems these days with delphi 2005. We did manage to find a freeware component that we could compile in and it would give a good indication of where the leaks were, but it made me think that since eurekalog already does stack traces, perhaps you should think about adding memory leak logging to it as well. Since eurekalog is already great for debugging, it would also be good if it could catch memory leaks as well (since it's already compiled in to all our apps).
Anyway, just a suggestion, though probably a large undertaking.
There is a freeware component that does this memory leak checking that we use at: http://v.mahon.free.fr/pro/freeware/memcheck .. it works pretty well but it uses TD Debug info which adds a HUGE size to the exe. I believe it uses this in order to get a stack trace to locate the leaks. Perhaps by looking at this source you could get an idea of how hard it would be to add similar functionality to eurekalog if you were ever considering it? It would be a valuable debugging option!
Jay Macaulay