Great! I'll give it a try :) -- -- View this message in context: http://groovy.329449.n5.nabble.com/Latest-Groovy-benchmarks-tp2800989p3324109.html Sent from the groovy - user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
I am using the last one, 1.7.6, before i tried with 1.7.4, both for windows. On 31 December 2010 01:49, Thom Nichols <tmnichols@...> wrote: > What version of Groovy are you using? I wonder if this could be caused by a > 1.7 compiled binary being run under 1.6. > > Sent from my Android > > On Dec 30, 2010 5:28 PM, "fed" <resdev@...> wrote: >> I was not running it from Groovy Console. >> >> At first i run it from IntelliJ then from command line, but the error >> is still present. >> >> >> On 30 December 2010 17:52, Peter Niederwieser <pniederw@...> wrote: >>> >>> Where are you running this? Groovy Console? Try to run it on the command >>> line >>> instead. >>> >>> Cheers, >>> Peter >>> -- >>> View this message in context: >>> http://groovy.329449.n5.nabble.com/java-lang-LinkageError-problem-with-Executors-and-HttPBuilder-tp3321374p3322636.html >>> Sent from the groovy - user mailing list archive at Nabble.com. >>> >>> ---------------------------------------------------------------------(Continue reading)
Hi Folks, I'm relatively new to the Groovy world and am absolutely loving it. I think this is the programming language I have spent my life waiting for. :) Anyway, I'm (in some ways unfortunately, since I prefer Eclipse...) stuck with using Netbeans for my current project because it has a gui component which is developed using the Netbeans visual error. I have some groovy classes which extend GroovyTestCase and after an arbitrary number of successful runs, I eventually get a java.lang.OutOfMemoryError which requires me to close netbeans and restart it. 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. I realise this is a Netbeans issue rather than a Groovy issue, but I was wondering if anyone else had seen this and/or have a solution? Best regards, Andrew. -- -- View this message in context: http://groovy.329449.n5.nabble.com/Groovy-Netbeans-OutOfMemoryErrors-when-running-unit-tests-tp3325357p3325357.html Sent from the groovy - user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit:(Continue reading)
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_email
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.
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.
Am 03.01.2011 11:06, schrieb am2605: > 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. I would suggest you take a Profiler and look where all the memory is going to. 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_email
I'm not sure how to profile a Groovy unit test in Netbeans. With a java class you can right click and select "Profile file" however the Groovy class has much more limited set of options (Open, Cut, Copy, Run File, Delete, Rename, Save As Template, Local History, Mercurial, Tools, Properties).
I could wrap it in a Java class - would that be worthwhile?
Andrew.
Am 03.01.2011 11:06, schrieb am2605:> Hi blackdrag,I would suggest you take a Profiler and look where all the memory is
>
> 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.
going to.
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_email
View message <at> http://groovy.329449.n5.nabble.com/Groovy-Netbeans-OutOfMemoryErrors-when-running-unit-tests-tp3325357p3325546.html
To unsubscribe from Groovy / Netbeans - OutOfMemoryErrors when running unit tests, click here.
Wow - when I changed those options Netbeans started up in like 5 seconds instead of 50 seconds. I'll let you know how I go. Thanks for the suggestion! And I am actually growing more and more attached to Netbeans - it certainly has some good points :)
<style type="text/css"><!-- DIV {margin:0px;} --></style>Hello there!
I personally love netbeans (though i have to use eclipse on work), and, well, even though i like it, i think it really is a memory eater. On my experiences using it with jboss seam i had to increase the memory for it, and i think that its visual editor must need more ram. I have somewhere a screenshot of NB eating 480mb away while trying to render an UML diagram.
Anyway, if u didn't tried yet, i recommend u to try to increase NB memory. This page may help: http://www.jguru.com/faq/view.jsp?EID=1303659.
[]'s
WillDe: am2605 <[hidden email]>
Para: [hidden email]
Enviadas: Segunda-feira, 3 de Janeiro de 2011 2:51:19
Assunto: [groovy-user] Groovy / Netbeans - OutOfMemoryErrors when running unit tests
Hi Folks,
I'm relatively new to the Groovy world and am absolutely loving it. I think
this is the programming language I have spent my life waiting for. :)
Anyway, I'm (in some ways unfortunately, since I prefer Eclipse...) stuck
with using Netbeans for my current project because it has a gui component
which is developed using the Netbeans visual error.
I have some groovy classes which extend GroovyTestCase and after an
arbitrary number of successful runs, I eventually get a
java.lang.OutOfMemoryError which requires me to close netbeans and restart
it.I realise this is a Netbeans issue rather than a Groovy issue, but I was
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.
wondering if anyone else had seen this and/or have a solution?
Best regards,
Andrew.
--
View this message in context: http://groovy.329449.n5.nabble.com/Groovy-Netbeans-OutOfMemoryErrors-when-running-unit-tests-tp3325357p3325357.html
Sent from the groovy - user mailing list archive at Nabble.com.
---------------------------------------------------------------------
View message <at> http://groovy.329449.n5.nabble.com/Groovy-Netbeans-OutOfMemoryErrors-when-running-unit-tests-tp3325357p3325610.html
To unsubscribe from Groovy / Netbeans - OutOfMemoryErrors when running unit tests, click here.
> I'm not sure how to profile a Groovy unit test in Netbeans Try to run the JVM that crashes with -XX:+HeapDumpOnOutOfMemoryError. Then you can analyze the heap dump offline using jhat or jvisualvm. -- -- Cheers Alex --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
RSS Feed265 | |
|---|---|
260 | |
475 | |
521 | |
277 | |
208 | |
206 | |
255 | |
280 | |
151 | |
278 | |
314 | |
220 | |
159 | |
389 | |
309 | |
238 | |
246 | |
258 | |
349 | |
558 | |
277 | |
336 | |
444 | |
554 | |
578 | |
560 | |
559 | |
473 | |
354 | |
342 | |
487 | |
386 | |
264 | |
405 | |
510 | |
529 | |
526 | |
608 | |
400 | |
764 | |
636 | |
573 | |
606 | |
577 | |
805 | |
666 | |
573 | |
646 | |
761 | |
948 | |
679 | |
866 | |
549 | |
602 | |
617 | |
765 | |
684 | |
693 | |
791 | |
1018 | |
1093 | |
818 | |
987 | |
1039 | |
1171 | |
1072 | |
946 | |
1078 | |
1152 | |
1101 | |
1138 | |
1503 | |
1579 | |
1578 | |
1233 | |
1522 | |
824 | |
650 | |
243 | |
1 | |
42 | |
251 | |
576 | |
656 | |
278 | |
291 | |
454 | |
498 | |
315 | |
339 | |
289 | |
487 | |
281 | |
201 | |
192 | |
286 | |
128 | |
333 | |
315 | |
204 | |
174 | |
186 | |
134 | |
241 | |
249 | |
213 | |
501 | |
495 | |
221 | |
46 |
