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.
When using Netbeans 7.1.2 with jdk7u4 the IDE sometimes fails to start. The messages shown below are printed to the shell in these cases. I already increased the code cache size to 256m. But this does not help. Sometimes several attempts are needed before Netbeans comes up. Java HotSpot(TM) 64-Bit Server VM warning: CodeCache is full. Compiler has been disabled. Java HotSpot(TM) 64-Bit Server VM warning: Try increasing the code cache size using -XX:ReservedCodeCacheSize= Code Cache [0x00007f1edb63c000, 0x00007f1edbcec000, 0x00007f1eeb63c000) total_blobs=2363 nmethods=1865 adapters=414 free_code_cache=255353Kb largest_free_block=261423232 Java HotSpot(TM) 64-Bit Server VM warning: CodeCache is full. Compiler has been disabled. Java HotSpot(TM) 64-Bit Server VM warning: Try increasing the code cache size using -XX:ReservedCodeCacheSize= Code Cache [0x00007f1edb63c000, 0x00007f1edbcec000, 0x00007f1eeb63c000) total_blobs=2370 nmethods=1870 adapters=415 free_code_cache=255345Kb largest_free_block=261423232 Java HotSpot(TM) 64-Bit Server VM warning: Attempt to deallocate stack guard pages failed. Java HotSpot(TM) 64-Bit Server VM warning: Attempt to allocate stack guard pages failed.
Same Problem for me. This morning I need 4 times to start netbeans 7.1.2 with jdk7u4 on my ubuntu 10.04 LTS system using the 64 bit jdk version.
(In reply to comment #0) > When using Netbeans 7.1.2 with jdk7u4 the IDE sometimes fails to start. > The messages shown below are printed to the shell in these cases. > I already increased the code cache size to 256m. But this does not help. > Sometimes several attempts are needed before Netbeans comes up. > > Java HotSpot(TM) 64-Bit Server VM warning: CodeCache is full. Compiler has been > disabled. It's just a warning. It cannot block launching IDE at all. What does mean 'fails to start'? A crash on startup? Slow startup? Frozen during startup? Something else? Please, attach your messages.log and all further details of your installation. Did you use NB7.1.1 before? Thanks > Java HotSpot(TM) 64-Bit Server VM warning: Try increasing the code cache size > using > -XX:ReservedCodeCacheSize= > Code Cache [0x00007f1edb63c000, 0x00007f1edbcec000, 0x00007f1eeb63c000) > total_blobs=2363 nmethods=1865 adapters=414 free_code_cache=255353Kb > largest_free_block=261423232 > Java HotSpot(TM) 64-Bit Server VM warning: CodeCache is full. Compiler has been > disabled. > Java HotSpot(TM) 64-Bit Server VM warning: Try increasing the code cache size > using > -XX:ReservedCodeCacheSize= > Code Cache [0x00007f1edb63c000, 0x00007f1edbcec000, 0x00007f1eeb63c000) > total_blobs=2370 nmethods=1870 adapters=415 free_code_cache=255345Kb > largest_free_block=261423232 > Java HotSpot(TM) 64-Bit Server VM warning: Attempt to deallocate stack guard > pages failed. > Java HotSpot(TM) 64-Bit Server VM warning: Attempt to allocate stack guard > pages failed.
Created attachment 119294 [details] bzip2 message.log file
(In reply to comment #2) I am not the reporter but I have the same problems. > What does mean 'fails to start'? A crash on startup? Slow startup? Frozen > during startup? Something else? It begins to start normally, the splash screen appears and then it exits. It seems to be that it does not crash and it does not freeze. > Please, attach your messages.log and all further details of your installation. > Did you use NB7.1.1 before? Thanks The messages log is too big to be attached uncompressed. I bzip2 it and attached it then. Yes. But only with JDK 1.6. > > Java HotSpot(TM) 64-Bit Server VM warning: Attempt to deallocate stack guard > > pages failed. > > Java HotSpot(TM) 64-Bit Server VM warning: Attempt to allocate stack guard > > pages failed. I think that these are the real problems.
anba, thank for messages.log. Could you also generate full thread dump during [1] starting IDE and attach it? Thanks in advance. [1] http://wiki.netbeans.org/GenerateThreadDump#Console_on_Unix.2C_Linux.2C_Mac_OS_X A suspicion place is <java_home>/jre/lib/amd64/libt2k.so: failed to map segment from shared object: Cannot allocate memory. Rest of content of messages.log are just OutOfMemoryError: unable to create new native thread.
Created attachment 119346 [details] Threads after first error message
(In reply to comment #6) > Created attachment 119346 [details] > Threads after first error message It is really complicated to get thoses thread dumps since - most starts work - 1 of 5 starts have the problem - I am not sure at which time of the start the thread dump is usable for you. The attached dump was created after the first error message appeared. You can see this in the shell output from the thread dump. After the first error message appeared you have typically between half a second to 3 second before the program exits.
(In reply to comment #7) > The attached dump was created after the first error message appeared. You can > see this in the shell output from the thread dump. > Sorry, as I saw a minute agon the following message was already printed when I issued the stack trace "Threads after first error message": Java HotSpot(TM) 64-Bit Server VM warning: Attempt to deallocate stack guard pages failed. A minute ago I was able to create a stack trace after the CodeCache lines. This stack trace is named "Thead dump after CodeCache error line"
Created attachment 119348 [details] Thead dump after CodeCache error line
A small additional information: the return code of the netbeans process is 2 in case of the error.
We installed netbeans 7.2 Beta and had the same problems with starting using our JDK. We use a JDK where we install the JAI and JAI IO from SUN. If we do not install these software packages the start problem seems to go away (I have not had it since then) but then we have problems with our developed application. We switched of the features using JAI and JAI IO in our application to develop it using netbeans for these tests. So what does JAI and JAI IO in netbeans?
java.lang.UnsatisfiedLinkError: /usr/local64/java/jdk1.7.0_04_b20_jaxb2.2.5_xalan2.7.1/jre/lib/amd64/libt2k.so: /usr/local64/java/jdk1.7.0_04_b20_jaxb2.2.5_xalan2.7.1/jre/lib/amd64/libt2k.so: failed to map segment from shared object: Cannot allocate memory at java.lang.ClassLoader$NativeLibrary.load(Native Method) Not a NetBeans bug. A corrupt installation of JDK. > our JDK. We use a JDK where we install the JAI and JAI IO from SUN. > If we do not install these software packages the start problem seems to > go away (I have not had it since then) Then, please don't do it. Run NetBeans on a clean JDK. > but then we have problems with our developed application Use a different Java platform for your project. See main menu Tools / Java Platforms, and project Properties of your project.