Andrew Ross wrote:
> On Thu, May 27, 2010 at 03:49:22PM -0400, Hazen Babcock wrote:
>> It really looks to me like it is consuming some finite system resource.
>> As I mentioned before the test will hang at the call to QApplication.
>> What I have now discovered however, is that if I close another GUI
>> application (Firefox or Emacs) then the test will continue and make it
>> through another cycle, i.e.:
>> 1. test hangs at iteration 991
>> 2. close Firefox
>> 3. test finishes iteration 991 and now hangs at 992.
>> Are we sure that we are closing the QApplication properly?
> I think so, although most programs would only create a QApplication once
> at the beginning of the program then delete it at the end, so resource
> leaks might not be obvious.
I believe that is what we are doing too in these tests.
> You could try valgrind with things like --track-fds to see if there is a
> leak of file descriptors?
Attached, not sure what to make of it, except that we don't close test.png?
Let me know if there is anything else I can run that would be informative.