This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
+++ This bug was initially created as a clone of Bug #253322 +++ Everytime that I open a web application, not too big yet, a process of index unpacking begin and it starts to eat all the memory, progress detail shows: "com.sleepcamel.bsoneer:bsonner-parent", tooltip says "Transfering Maven Repository index: OSS Sonatype Staging" and freezes the pc this is the POM <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.mycompany</groupId> <artifactId>SindicatoWeb</artifactId> <packaging>war</packaging> <version>1.0-SNAPSHOT</version> <name>SindicatoWeb</name> <properties> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> <vaadin.version>7.4.0.alpha7</vaadin.version> <vaadin.plugin.version>${vaadin.version}</vaadin.plugin.version> </properties> <repositories> <repository> <id>vaadin-addons</id> <url>http://maven.vaadin.com/vaadin-addons</url> </repository> <repository> <id>vaadin-snapshots</id> <url>http://oss.sonatype.org/content/repositories/vaadin-snapshots/</url> <releases> <enabled>false</enabled> </releases> <snapshots> <enabled>true</enabled> </snapshots> </repository> <repository> <id>oss.sonatype.org</id> <name>OSS Sonatype Staging</name> <url>https://oss.sonatype.org/content/groups/staging</url> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>vaadin-snapshots</id> <url>http://oss.sonatype.org/content/repositories/vaadin-snapshots/</url> <releases> <enabled>false</enabled> </releases> <snapshots> <enabled>true</enabled> </snapshots> </pluginRepository> </pluginRepositories> <dependencies> <!-- <dependency> <groupId>Utilitiez</groupId> <artifactId>Utilitiez</artifactId> <version>1.0</version> </dependency>--> <!-- para instalar el jar en el repositorio local mvn install:install-file -Dfile=/home/nsteinhilber/NetBeansProjects/libs/utilitiez.jar -DgroupId=Utilitiez -DartifactId=Utilitiez -Dversion=1.0 -Dpackaging=jar --> <dependency> <groupId>utilities</groupId> <artifactId>utilities</artifactId> <version>1.0</version> <scope>system</scope> <systemPath>D:/libs/utilitiez.jar</systemPath> <type>jar</type> </dependency> <dependency> <groupId>com.vaadin</groupId> <artifactId>vaadin-server</artifactId> <version>${vaadin.version}</version> </dependency> <dependency> <groupId>com.vaadin</groupId> <artifactId>vaadin-client-compiled</artifactId> <version>${vaadin.version}</version> </dependency> <dependency> <groupId>javax.transaction</groupId> <artifactId>jta</artifactId> <version>1.1</version> </dependency> <dependency> <groupId>com.vaadin.addon</groupId> <artifactId>vaadin-charts</artifactId> <version>1.1.7</version> </dependency> <dependency> <groupId>org.vaadin</groupId> <artifactId>suggestfield</artifactId> <version>0.0.3</version> </dependency> <dependency> <groupId>org.vaadin.addon</groupId> <artifactId>confirmdialog</artifactId> <version>2.1.2</version> </dependency> <!-- Needed when using the widgetset optimizer (custom ConnectorBundleLoaderFactory). For widgetset compilation, vaadin-client-compiler is automatically added on the compilation classpath by vaadin-maven-plugin so normally there is no need for an explicit dependency. --> <!-- <dependency> <groupId>com.vaadin</groupId> <artifactId>vaadin-client-compiler</artifactId> <version>${vaadin.version}</version> <scope>provided</scope> </dependency> --> <dependency> <groupId>com.vaadin</groupId> <artifactId>vaadin-client</artifactId> <version>${vaadin.version}</version> <scope>provided</scope> </dependency> <dependency> <groupId>com.vaadin</groupId> <artifactId>vaadin-push</artifactId> <version>${vaadin.version}</version> </dependency> <dependency> <groupId>com.vaadin</groupId> <artifactId>vaadin-themes</artifactId> <version>${vaadin.version}</version> </dependency> <dependency> <groupId>javax.servlet</groupId> <artifactId>javax.servlet-api</artifactId> <version>3.0.1</version> <scope>provided</scope> </dependency> <dependency> <groupId>org.eclipse.persistence</groupId> <artifactId>eclipselink</artifactId> <version>2.5.1</version> <exclusions> <exclusion> <groupId>org.eclipse.persistence</groupId> <artifactId>commonj.sdo</artifactId> </exclusion> </exclusions> <scope>provided</scope> </dependency> <dependency> <groupId>postgresql</groupId> <artifactId>postgresql</artifactId> <version>9.1-901.jdbc4</version> <scope>provided</scope> </dependency> <dependency> <groupId>org.eclipse.persistence</groupId> <artifactId>org.eclipse.persistence.jpa.modelgen.processor</artifactId> <version>2.5.1</version> <scope>provided</scope> </dependency> <dependency> <groupId>com.vaadin</groupId> <artifactId>vaadin-cdi</artifactId> <version>1.0.0.alpha2</version> <type>jar</type> </dependency> <dependency> <groupId>net.sf.jasperreports</groupId> <artifactId>jasperreports</artifactId> <version>5.5.1</version> <type>jar</type> <exclusions> <exclusion> <groupId>bouncycastle</groupId> <artifactId>bcmail-jdk14</artifactId> </exclusion> <exclusion> <groupId>org.bouncycastle</groupId> <artifactId>bcmail-jdk14</artifactId> </exclusion> <exclusion> <groupId>org.bouncycastle</groupId> <artifactId>bcprov-jdk14</artifactId> </exclusion> <exclusion> <groupId>bouncycastle</groupId> <artifactId>bcprov-jdk14</artifactId> </exclusion> <exclusion> <groupId>org.bouncycastle</groupId> <artifactId>bctsp-jdk14</artifactId> </exclusion> <exclusion> <groupId>org.codehaus.castor</groupId> <artifactId>castor</artifactId> </exclusion> <exclusion> <groupId>com.fasterxml.jackson.core</groupId> <artifactId>jackson-annotations</artifactId> </exclusion> <exclusion> <groupId>com.fasterxml.jackson.core</groupId> <artifactId>jackson-databind</artifactId> </exclusion> <exclusion> <groupId>com.fasterxml.jackson.core</groupId> <artifactId>jackson-core</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>1.2.17</version> <type>jar</type> </dependency> <dependency> <groupId>javax</groupId> <artifactId>javaee-web-api</artifactId> <version>6.0</version> <type>jar</type> </dependency> <dependency> <groupId>net.sf.jasperreports</groupId> <artifactId>jasperreports</artifactId> <version>5.1.0</version> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <configuration> <source>1.7</source> <target>1.7</target> </configuration> </plugin> <!-- As we are doing "inplace" GWT compilation, ensure the widgetset --> <!-- directory is cleaned properly --> <plugin> <artifactId>maven-clean-plugin</artifactId> <version>2.4.1</version> <configuration> <filesets> <fileset> <directory>src/main/webapp/VAADIN/widgetsets</directory> </fileset> </filesets> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <version>2.2</version> <configuration> <failOnMissingWebXml>false</failOnMissingWebXml> </configuration> </plugin> <plugin> <groupId>com.vaadin</groupId> <artifactId>vaadin-maven-plugin</artifactId> <version>${vaadin.plugin.version}</version> <configuration> <gwtSdkFirstInClasspath>true</gwtSdkFirstInClasspath> <extraJvmArgs>-Xmx2048M -Xss4096k</extraJvmArgs> <!-- <runTarget>mobilemail</runTarget> --> <!-- We are doing "inplace" but into subdir VAADIN/widgetsets. This way compatible with Vaadin eclipse plugin. --> <webappDirectory>${basedir}/src/main/webapp/VAADIN/widgetsets </webappDirectory> <hostedWebapp>${basedir}/src/main/webapp/VAADIN/widgetsets </hostedWebapp> <!-- Most Vaadin apps don't need this stuff, guide that to target --> <persistentunitcachedir>${project.build.directory}</persistentunitcachedir> <deploy>${project.build.directory}/gwt-deploy</deploy> <!-- Compile report is not typically needed either, saves hunreds of mb disk --> <compileReport>false</compileReport> <noServer>true</noServer> <!-- Remove draftCompile when project is ready --> <draftCompile>false</draftCompile> <style>OBF</style> <strict>true</strict> <runTarget>http://localhost:8080/ProyectoUno</runTarget> </configuration> <executions> <execution> <configuration> <!-- if you don't specify any modules, the plugin will find them --> <!-- <modules> <module>com.vaadin.demo.mobilemail.gwt.ColorPickerWidgetSet</module> </modules> --> </configuration> <goals> <goal>clean</goal> <goal>resources</goal> <goal>update-theme</goal> <goal>update-widgetset</goal> <goal>compile-theme</goal> <goal>compile</goal> </goals> </execution> </executions> </plugin> <plugin> <groupId>org.mortbay.jetty</groupId> <artifactId>jetty-maven-plugin</artifactId> <configuration> <webApp> <contextPath>/SindicatoWeb</contextPath> </webApp> <scanIntervalSeconds>5</scanIntervalSeconds> </configuration> </plugin> </plugins> <pluginManagement> <plugins> <!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.--> <plugin> <groupId>org.eclipse.m2e</groupId> <artifactId>lifecycle-mapping</artifactId> <version>1.0.0</version> <configuration> <lifecycleMappingMetadata> <pluginExecutions> <pluginExecution> <pluginExecutionFilter> <groupId>com.vaadin</groupId> <artifactId> vaadin-maven-plugin </artifactId> <versionRange> [7.4.0.alpha7,) </versionRange> <goals> <goal>resources</goal> <goal>update-widgetset</goal> <goal>compile</goal> <goal>update-theme</goal> <goal>compile-theme</goal> </goals> </pluginExecutionFilter> <action> <ignore></ignore> </action> </pluginExecution> </pluginExecutions> </lifecycleMappingMetadata> </configuration> </plugin> <plugin> <artifactId>maven-eclipse-plugin</artifactId> <configuration> <wtpversion>2.0</wtpversion> <additionalProjectnatures> <projectnature>com.vaadin.integration.eclipse.widgetsetNature</projectnature> </additionalProjectnatures> <additionalBuildcommands> <buildcommand>com.vaadin.integration.eclipse.widgetsetBuilder</buildcommand> <buildcommand>com.vaadin.integration.eclipse.addonStylesBuilder</buildcommand> </additionalBuildcommands> </configuration> </plugin> </plugins> </pluginManagement> </build> </project> Product Version = NetBeans IDE 8.0.2 (Build 201411181905) Operating System = Windows 7 version 6.1 running on amd64 Java; VM; Vendor = 1.8.0_45 Runtime = Java HotSpot(TM) 64-Bit Server VM 25.45-b02
I've come across the same issue in 8.0.2 and 8.2 (not tried 8.1 or other intermediate releases). I'm running on Windows 7. Several Maven based war projects. I can post effective POMs if need be although I'm not sure they'll be terribly useful. I think a clean and build tries to load the sonatype-oss-public repository index. This takes an awfully long time to start with. However, when the status bar shows 'Unpacking index for sonatype-oss-public' memory usage jumps up and up until it's using over 6GB and I have to kill the Netbeans64.exe process (I've got 8GB). This will usually take place over a period of a few hours. I've added -J-Dmaven.indexing.doNotAutoIndex=sonatype-oss-public in netbeans.conf (on the 8.2 release) and memory usage seems stable at just over 2GB although I'll be keeping an eye on it. Usage is creeping up but that could just be normal caching. I think this is definitely a live issue and warrants a bit more investigation. Perhaps index unpacking for certain repo's should be switched off by default? It does pretty much make netbeans useless when it's happening. I considered switching IDEs.
Any attempt to auto complete in, for example, a spring definition XML seems to set off whatever process is consuming all the memory. I'm having to restart my IDE several times a day.