I haven't tried 2.0.3 yet, I only built the packages last night. I'm told, however, this patch only applies to 2.1 dev branch, and that 2.0 branch doesn't have this particular bit of leaky code. I'll try 2.0.3 soon and report back. The sheer volume of bug fixes listed in the change log looks promising, if frightening. :-) On the subject of the change log - is there any chance of tagging changes by in addition to just by date? Gordan -----Original Message----- From: "Anand Avati" <anand.avati@xxxxxxxxx> To: "Gordan Bobic" <gordan@xxxxxxxxxx> Cc: "Gluster Devel" <gluster-devel@xxxxxxxxxx> Sent: 09/07/09 08:45 Subject: Re: Memory Leak Strikes Again > This doesn't seem to apply against 2.0.3. Can you provide a patch vs. 2.03 > release? The patch was included in 2.0.3. Do you still face the leak in 2.0.3 as well? Avati
