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.
I create a new project using "Java Project with Existing Sources". Resolved the test-sources folder conflict due to a defect (BugID 47609). Then add all the jar files needed for the new project including the JUnit jar. After that the whole IDE freezes.
Created attachment 17007 [details] Output captured from the Console
there is OutOfMemoryException Cheong, could you tell us more informations ? Build number, JDK (or attach you message.log file), RAM , have you changed Xmx, Xms .... ?
Oops, so sorry. My environment is NB 4.0Beta1, OSX 10.3.5, Java 1.4.2_05-141, 2GB of ram. I wanted to set to a larger memory but now NB 4.0 OSX doesn't come with the launcher and i dont't know how to do it now. I tried to do a Ctrl-/ but doesn't seems to be able to force a dump. I encountered these freezes about 3 -4 times in total in the past using the last Q Build just before the Beta1. They all occur immediately after i try to create a new project from existing sources and resolving the test-sources folder conflict and adding my external jar files. After i kill NB4.0 and re-run it, i had to resolve the test-sources conflict and setup the external jar files again. Hope this helps.
No particular reason to think this is projects-related; adding JARs to the classpath is more likely to consume a lot of memory due to classpath scanning. But without steps to reproduce and a memory profiler, one can only guess.
How many JARs do you have? How many java files in them? Isn't this issue in fact the following two issues combined? Please, see issue 47910 and issue 47870 and let us know. Thanks.
I have a total of 17 jars which total up to 685 classes. Is there a better way to count the classes in the jar file? I had to do it manually.
Hmm, it is not too much. Should not cause OOME from classpath scanning and parsing. Milane, please, could you try reproducing this and finding more details about it? Thanks.
Perhaps disapointing but I haven't managed to reproduce the problem. No more deatils. Sorry.
Is there any way i can force a dump while the IDE appears to be frozen? I think the ctrl-/ is suppose to do the job, but i dont seems to be able to do that. It happened to me about 3 -4 times from the pre Beta1 and Beta1 build. I am using Mac OSX 10.3.5, java 1.4.2_05, NB Beta1
Ctrl-\ not Ctrl-/, and in the terminal window you start NB from, not in the app itself. (Definitely works on Unix, but I don't know about Macs.)
No thread dump provided for a long time, closing.
This issue was reported by NetCAT program member.