Difference between revisions of "Talk:WeeksOnEnd"
Jump to navigation
Jump to search
Skilgannon (talk | contribs) (→OutOfMemory errors: iterate in script?) |
(→OutOfMemory errors: thanks; comment) |
||
Line 4: | Line 4: | ||
I used to get those, but they stopped when I changed from iterating within roborumble (ie. ITERATE=YES in roborumble.txt) to iterating in a shell script instead (ie. <code>while sleep 1; do ./roborumble.sh; done</code>). I suspect Robocode still isn't releasing all the memory from bots. --[[User:Skilgannon|Skilgannon]] 13:10, 9 September 2009 (UTC) | I used to get those, but they stopped when I changed from iterating within roborumble (ie. ITERATE=YES in roborumble.txt) to iterating in a shell script instead (ie. <code>while sleep 1; do ./roborumble.sh; done</code>). I suspect Robocode still isn't releasing all the memory from bots. --[[User:Skilgannon|Skilgannon]] 13:10, 9 September 2009 (UTC) | ||
+ | |||
+ | : Hmm, I'll have to switch if that solves the problem... The issue with that is that it doesn't seem to recognize priority battles as well on the first iteration, at least that's what I've seen. The first iteration, it just seems to look at the BATTLESPERBOT, while on successive iterations, it tries to fill all pairings. I'll tinker with it later though. Thanks! --[[User:Voidious|Voidious]] 13:12, 9 September 2009 (UTC) |
Revision as of 14:12, 9 September 2009
OutOfMemory errors
Anyone else had issues with any of Simonton's bots lately? Last night, 3 of my 4 clients were hung with "java.lang.OutOfMemoryError: Java heap space" from WeeksOnEnd 1.10.4 battles, and I've had it happen with another of his bots recently, too (LifelongObsession maybe?). And, sadly, my 4th client hung with the same error from RougeDC willow. =( --Voidious 13:03, 9 September 2009 (UTC)
I used to get those, but they stopped when I changed from iterating within roborumble (ie. ITERATE=YES in roborumble.txt) to iterating in a shell script instead (ie. while sleep 1; do ./roborumble.sh; done
). I suspect Robocode still isn't releasing all the memory from bots. --Skilgannon 13:10, 9 September 2009 (UTC)
- Hmm, I'll have to switch if that solves the problem... The issue with that is that it doesn't seem to recognize priority battles as well on the first iteration, at least that's what I've seen. The first iteration, it just seems to look at the BATTLESPERBOT, while on successive iterations, it tries to fill all pairings. I'll tinker with it later though. Thanks! --Voidious 13:12, 9 September 2009 (UTC)