[ 
http://jira.codehaus.org/browse/MCLEAN-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130878#action_130878
 ] 

Ryan Sonnek commented on MCLEAN-32:
-----------------------------------

We're running with 512M for the JVM heap size which should be *more* than 
enough for this operation.

The question is why is the directory scanner caching references to files so 
aggressively?  This seems *very* inefficient. 

> Out of Memory Error cleaning target directory with *large* number of 
> sub-directories
> ------------------------------------------------------------------------------------
>
>                 Key: MCLEAN-32
>                 URL: http://jira.codehaus.org/browse/MCLEAN-32
>             Project: Maven 2.x Clean Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>         Environment: maven-2.0.8, solaris, jdk 1.6.0_05
>            Reporter: Ryan Sonnek
>            Priority: Critical
>         Attachments: output.txt
>
>
> running mvn clean on a target directory with a *large* number of sub 
> directories causes an OutOfMemoryError.  The plexus DirectoryScanner seems to 
> be the major culprit from the stacktrace.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to