On 11/05/10 10:12 PM, Steve Appling wrote:
On May 10, 2010, at 5:36 PM, John Murph wrote:
We are getting OOMs occasionally. These seems to happen for many (if not all)
our various builds on our project, but not consistently for any of them. Each
of these builds is run with a -Xmx of 256m. An example stack trace is given
below. It seems related to caching of task archives, and my .bin file is ~30
MB right now...
--
John Murph
Automated Logic Research Team
On one of our build agents that is consistently failing, the
taskArtifacts/cache.bin is 767Mb. Does this ever get garbage collected in any
way, or does the cache file always just grow?
There's some basic garbage collection, but it needs more work. Nothing
under ~/.gradle or $rootDir/.gradle is garbage collected.
I know I can do a -C rebuild to clean this out, but I don't want to keep
performing maintenance on these agents.
And that's quite reasonable. Some time soon we should look at a scheme
for garbage collecting all the state that Gradle caches.
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
