This is a known Java bug. This issue is fixed in MagicDraw 18.4. If you are using MagicDraw 18.3 and earlier versions, you can use the recommended Java version that comes with installation. Once you have installed the recommended Java version, do the following:
|
This is a known Java bug. This issue is fixed in MagicDraw 18.3, but in the meantime you can upgrade to the recommended Java version. |
Try to start MagicDraw without direct draw, and edit JAVA_ARGS the line in the MagicDrawUML/bin/mduml.properties* file by adding -Dsun.java2d.noddraw=true. The line should look like: JAVA_ARGS=-Xmx600M -XX\:PermSize\=40M -XX\:MaxPermSize\=200M -Dsun.java2d.noddraw=true.
* If you are using MagicDraw 17.0.5 or later, the name of the property file is magicdraw.properties. |
If you are running the Sun's JVM, set the following java properties in your mduml.properties* file: to the line JAVA_ARGS=-Xmx600M, append the string -Xss[stack size] For example: JAVA_ARGS=-Xmx600M -Xss2M This sets java stack size to 2 megabytes.
* If you are using MagicDraw 17.0.5 or later, the name of the property file is magicdraw.properties. |
MagicDraw stops responding due to an issue detected in Java SE 7 Update 40, which is bundled with MagicDraw 17.0.5 (for the issue details, go to https://bugs.openjdk.java.net/browse/JDK-8025588). This issue will be fixed in MagicDraw 17.0.5 SP1, coming out in the middle of February. To solve the issue manually (without the SP), switch the version of the bundled Java to SE 7 Update 25*, which does not cause the issue. For this, do the following:
Please contact our customer support, if this does not help. -- |