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.
Steps to reproduce: - Reverse Engineer the attached java project into UML project - Expand 'operations' node under 'test|basic|TestConditionIf' class element - Reverse engineer 'testConditionIf1' operation and create a sequence diagram - Reverse engineer 'testConditionIf2' operation and create a sequence diagram - Reverse engineer 'testConditionIf3' operation and create a sequence diagram After some operations IDE looks freezing. See attached snap-shot.
Created attachment 36543 [details] REOperationCodeSamples java project
Created attachment 36544 [details] IDE looks freezing after operation reverse engineering actions
on the intel mac, this causes a stack overflow. It looks to be the same font problem that we see in other stack overflows. (This is a know mac jvm bug that Apple is working on) Does this stack overflow occur on the PC?
I did not see any exceptions on Windows XP.
OutOfMemoryError is thrown when I used the latest nbms: java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOfRange(Arrays.java:3209) at java.lang.String.<init>(String.java:216) at java.io.BufferedReader.readLine(BufferedReader.java:331) at java.io.BufferedReader.readLine(BufferedReader.java:362)
Created attachment 38106 [details] OutOfMemoryError in IDE log file
why are these "out of memory" comments attached to this bug? Were you following the steps to reproduce this bug and got the exception? What were you doing when you got the exception? What are your memory settings for your IDE?
I got the exceptions exactly followed by the steps. My netbeans settings were: netbeans_default_options="-J-Xms32m -J-Xmx128m -J-XX:PermSize=32m -J-XX:MaxPermSize=160m -J-Xverify:none -J-Dapple.laf.useScreenMenuBar=true" But IDE still looks like frozen even I have increased my memory settings.
The IDE is frozen for some time on Linux Ubuntu.
don't see what we can do on 128M - it is just too little. With normal setting - Xmx512m - 2 fixes resulted in improved performance: 1.using weak references allowed to avoid in some cases, not always of course, reparsing of the library 2.blocking of model element change notifications during RE allowed to avoid snowballing effect when number of opened diagram grows The fixes were commited into release55 branch.
verified