|
From: Benjamin R. <ben...@ou...> - 2012-09-09 19:15:13
|
On Tue, May 22, 2012 at 9:18 AM, Stevenson, Samuel < Sam...@co...> wrote: > Hi Ben**** > > ** ** > > I am using 1.0.0. My colleague has 1.1.0 installed on his machine and is > able to reproduce the same problem.**** > > ** ** > > Thanks**** > > > Sam > Going through my old unresolved emails, I came across this one. I suspect that whatever has caused this problem in v1.1.0 is still present in v1.2.0 that we will be putting out an RC for. If you can make a small script that can demonstrate the memory leak, maybe we can track it down and nail this sucker before the final release? Cheers! Ben Root |