On Sunday, 24 July 2011 at 9:47:14 -0400, Yuval Levy wrote: > > We know that the current Hugin is plagued with a pesky spurious bug that is > difficult to reproduce. It is causing grievance to a lot of users as seen on > the ML and on the main tracker ticket where the bug is discussed [0]. > > This is most likely caused by a memory leak. The most difficult part of > fixing a memory leak is to identify where it happens. Would you like to help > nuke this bug?
I've just cloned the hg repository and built the latest version (5345). I had some difficulties building, which I'll mention in a separate message, but I wasn't able to provoke this bug. From reading the bug report, it seems possible that it's hardware or software dependent. My system: OS: FreeBSD 8.2-STABLE, i386, 3 GB memory X: X.Org X Server 1.7.7 Display card: NVIDIA GPU GeForce 9500 GT (G96) (2, FWIW) Display driver: nVidia nvidia-driver-256.53_1 This was with my own images, a collection of 25. I tried playing around with the buttons in the fast preview window and kept an eye on the process memory image with ps, but there's no evidence of any memory leak. Anything else I should try? Until I can reproduce it with tip, there doesn't seem to be much point to try a binary search. Greg -- Finger g...@freebsd.org for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. See http://www.lemis.com/grog/email/signed-mail.php for more details. If your Microsoft MUA reports problems, please read http://tinyurl.com/broken-mua
pgpzxzGIDyhMj.pgp
Description: PGP signature
