CI memory leak testing

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

CI memory leak testing

Ben Coman


On 26 May 2018 at 18:21, Tudor Girba <[hidden email]> wrote:
Hi,

Yes, Glamour is stable since years. Yes, we did have some leak issues that appeared along the way. Last year, we discovered that a memory leak came from Rubric (specifically there was a global variable in it). People saw inspectors laying around, so naturally, the issue was seen as being due to GT. And now there is another one, which is still under investigation. For me, the main issue is not the memory leak, but the fact that we have no tool to reason about them.

I wonder if its possible/useful to define a generic mechanism that at the end of a CI test run all windows are force closed, garbage collected and then tallied objects the check a zero count for all classes except those explicitly defined, perhaps in a class manifest.  May have picked this up earlier.

cheers -ben