** 2007-08-30 Its still not fixed :-( something else is still eating up all the memory. Back to digging through heap traces. 2007-08-30 |
** 2007-08-30 Its still not fixed :-( something else is still eating up all the memory. Back to digging through heap traces. ** 2007-08-30 Okay, so I think it was fixed. The profiler takes up an increasing amount of memory as it runs, so over time the profiler itself was causing the OutOfMemory? error. Rather frustrating actually. So look for the changes in the CVS repo sometime this weekend or early next week. |
* It would affect anything that use the RobocodeEngine?. I ran across it not running the normal RoboCode but in use the Engine in another project. -- Ntroutman 2007-08-30 |
* It would affect anything that use the RobocodeEngine?. I ran across it not running the normal RoboCode but in using the Engine in another project. -- Ntroutman 2007-08-30 |
Who really wants to see a picture of me? |
I just recently (Aug 28, 2007) started making contributions to Robocode in the form of bug fixes.
Don't forget to put feature requests/bug reports into the tracker at https://sourceforge.net/tracker/?group_id=37202
Welcome to the RoboWiki, and thank you for the contributions so far! ;-) --Fnl
Oh, yes, sorry, where's my manners?? Welcome!! -- Simonton
Welcome! Good work on the memory fix for the engine. Pardon my ignorance, but would that affect only the Robocode (ie the GUI) or anything that uses the library (like RoboLeague, or RoboResearch)? -- Skilgannon
Welcome from me, too! We always welcome fresh blood--- err, newcomers to the Robocode arena. =) -- Voidious
Welcome to the (hopefully) Robocode addiction! --Starrynte