On 17/06/10 7:30 AM, John Murph wrote:
Definitely a bug. But maybe only a nuisance bug if it only wastes space. However, we have been seeing some OutOfMemory errors that might (might!) be related to the size of this file. If so, then it's a more serious bug.
Looking at the code, I do see one potential leak if the set of output files or directories of a task change each time the task is executed (not the contents of the files, the set of paths). For example, if you include a timestamp in an archive file name, then each time the archive is built, then some space is leaked, both in the file and in heap, when the history for the task is loaded.
This is pretty bad. I've added http://jira.codehaus.org/browse/GRADLE-986
On Wed, Jun 16, 2010 at 5:20 PM, vincer <[email protected] <mailto:[email protected]>> wrote:My cache.bin file in projectDir/.gradle/0.9-preview-3/taskArtifacts gets extremely large so I have to occasionally delete it. Once it was over 1.5GB and just now it was 700MB. After deleting it and doing a clean build its 1MB. Bug or feature? -- View this message in context: http://old.nabble.com/cache.bin-gets-very-large-tp28907834p28907834.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email -- John Murph Automated Logic Research Team
-- Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz
