[jira] [Commented] (MASSEMBLY-766) OOM with 1CPU

["Kristian Rosenvold (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MASSEMBLY-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523992#comment-14523992 ] 

Kristian Rosenvold commented on MASSEMBLY-766:
----------------------------------------------

Oops. The intended behaviour was max 10mb per CPU core. It seems there was an extra 0 in there, making the maximum 100mb per cpu core and the effective minimum 10mb per core (in 10mb increments) This was definitely somewhat outside the intemded bounds. The idea was to use approx 160Mb on at 8 core + 8 ht cpu before offloading to disk, which should be an acceptable memory hit. But still, if your zip/jar file is in the region of 100mb it should only use somewhere in the region of  100-200mb even with the current algorithm. Does adding a little extra memory solve the problem ?

> OOM with 1CPU
> -------------
>
>                 Key: MASSEMBLY-766
>                 URL: https://issues.apache.org/jira/browse/MASSEMBLY-766
>             Project: Maven Assembly Plugin
>          Issue Type: Bug
>          Components: maven-archiver
>    Affects Versions: 2.5.4
>         Environment: jdk 8, sles 11.3, 1G heap build large assemblies 100M +
>            Reporter: Dan Tran
>
> Just happen to run on 1CPU VM, and VM crash on OOM
> sample errors
> #
> # There is insufficient memory for the Java Runtime Environment to continue.
> # Native memory allocation (malloc) failed to allocate 82576 bytes for Chunk::new
> # An error report file with more information is saved as:
> # /var/lib/jenkins/jobs/xxxx-all-bugId-template/workspace/hs_err_pid26261.log
> #
> # Compiler replay data is saved as:
> # /var/lib/jenkins/jobs/xxx-all-bugId-template/workspace/replay_pid26261.log
> Build step 'Invoke top-level Maven targets' marked build as failure
> another one
> [INFO] --- maven-assembly-plugin:2.5.4:single (uber-jar) @ xxx-configmgr ---
> mmap failed for CEN and END part of zip file
> java.lang.OutOfMemoryError
> 	at java.util.zip.ZipFile.open(Native Method)
> ....
> org.codehaus.plexus.archiver.zip.PlexusIoZipFileResourceCollection$1.getResource(PlexusIoZipFileResourceCollection.java:69)
> 	at org.codehaus.plexus.archiver.zip.PlexusIoZipFileResourceCollection$ZipFileResourceIterator$1.getURL(PlexusIoZipFileResourceCollection.java:125)
> 	at org.codehaus.plexus.components.io.resources.PlexusIoURLResource.getContents(PlexusIoURLResource.java:37)
> 	at ....
> org.codehaus.plexus.archiver.ArchiveEntry.getInputStream(ArchiveEntry.java:126)
> 	at org.codehaus.plexus.archiver.zip.AbstractZipArchiver.zipFile(AbstractZipArchiver.java:514)
> 	at org.codehaus.plexus.archiver.zip.AbstractZipArchiver.addResources(AbstractZipArchiver.java:370)
> 	at org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArchiver.java:326)
> 	at org.codehaus.plexus.archiver.zip.AbstractZipArchiver.execute(AbstractZipArchiver.java:227)
> 	at org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:990)
> 	at org.apache.maven.plugin.assembly.archive.archiver.AssemblyProxyArchiver.createArchive(AssemblyProxyArchiver.java:437)
> 	at org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:181)
> 	at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:484)
> 	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)