[news.eclipse.technology.iam] Re: Release candidate 0.9.0 at Q4E

[amuino@xxxxxxxxx (Abel Muiño)]

Unless there is a bug (which, by the size of the string, is quite 
possible), each MavenLog is an object representing a log message from 
maven (along with other formatting information). 

It looks like maven is generating this gigantic string for your build.

Could you try one more thing?
Run a command line build  with debug output enabled and look for the 
string in the output: 
   mvn -X process-test-resources > build.log

This will not be 100% accurate (since IAM uses a non-released version of 
maven) but with some luck it might help us to determine if maven is 
creating this string or is something in IAM.

Marek Romanowski wrote:

> I've dumped JVM memory on OutOfMemoryError and started to analyze it with 
> Eclipse Memory Analyzer. I think there is some problem with MavenLog 
> class. One of instances points to a String 275MB big... Connections go 
> like this:

> MavenEventStore -> CircularFifoBuffer -> Object[10000] -> MavenLog -> 
> String -> char[137022158]

> So it looks like MavenEventStore stores logs in CircularFifoBuffer. CFB 
> has got array of logs (array size: 10000). Array holds reference to a 
> MavenLog which references enormous String (137022158 characters). This 
> String starts with: "  (f) classpathElements = [" - after this goes 
> classpath elements from my project; two first chars are whitespaces.

> I think this take place only while plugin enables maven dependency 
> management. Maybe when I'm enabling it for 50+ projects at one operation, 
> this log is concatenated between all of them?


> I hope this will help you,
> Marek.