3 Jan 2011 11:06
[groovy-user] Re: Groovy / Netbeans - OutOfMemoryErrors when running unit tests
Hi blackdrag,
Thanks for your reply . I am not using ExpandoMetaClass or any custom meta class in my own code. Most of my groovy code is using HttpBuilder to parse web content.
The only place I reference metaClasses in my own code is a toString method like this:
def String toString() {
def result = ""
this.properties.each { prop, val ->
if(["metaClass", "class"].find {it == prop}) return
result += "[${prop}]: " + this[prop] + " "
}
return result
}
Regards,
Andrew.
On 3 January 2011 20:17, Jochen Theodorou [via Groovy] <[hidden email]> wrote:
Am 03.01.2011 05:51, schrieb am2605:
[...]
> As far as I know I'm doing memory management "by the book" - my tearDown()
> method sets any global vars back to null. So I'm not really sure what's
> going on.
do you use ExpandoMetaClass? Or any custom meta class?
bye blackdrag
--
Jochen "blackdrag" Theodorou
The Groovy Project Tech Lead
http://blackdragsview.blogspot.com/
For Groovy programming sources visit http://groovy.codehaus.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_emailView message <at> http://groovy.329449.n5.nabble.com/Groovy-Netbeans-OutOfMemoryErrors-when-running-unit-tests-tp3325357p3325499.html
To unsubscribe from Groovy / Netbeans - OutOfMemoryErrors when running unit tests, click here.
View this message in context: Re: Groovy / Netbeans - OutOfMemoryErrors when running unit tests
Sent from the groovy - user mailing list archive at Nabble.com.
RSS Feed