Comment 16 for bug 212825

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote : Re: Memory leak present in 0.5.25

Ok, there's a simple (but tedious) process that you can follow to help me find the leak. The trick is to disable some code to stop the leak then slowly start re-enabling parts until we see it again. The tedious part is that each test takes a few hours to see the leak, as you know.

For anyone that is able, here's the list of tasks. For each task insert "return true;", make then test.

1. application.cc, line 509, if this still leaks then I'm very wrong and we should stop this process
2. application.cc, line 511
3. application.cc, line 515
4. application.cc, line 542
5. application.cc, line 551
6. application.cc, line 558
7. application.cc, line 574
8. application.cc, line 580

I've only just started looking into this issue and I'm not sure if I get the same problem. I will start checking tonight.