

MagicDraw takes less memory with increased active validations period. Your projects will be opened over a shorter period of time without opening a diagram as well as use less memory.

To increase an efficiency of modeling, we suggest the following solutions: When you work with very large models or use a lot of diagrams at a time, the performance of MagicDraw may become slow.
#Magicdraw 12.5 zip
As the file may be large, please zip the created file, and upload it to the provided ftp server. The dump file will be created in the provided location – d:\\snapshots (please make sure that this location is available), if an OutOfMemory exception occurs.
#Magicdraw 12.5 manual
You should follow the instructions for manual update.
#Magicdraw 12.5 install
* - autoupdate feature fails to install these service packs because of Java incompatibility. In order to change Java version which MagicDraw uses, please follow the instructions in this file. Service pack 1 for MagicDraw 17.0.3 which solves this incompatibility issue was released on 4th March 2013.įor older MagicDraw versions we highly recommend using the officially recommended Java version:.Service pack 3 for MagicDraw 17.0.2 which solves this incompatibility issue was released on 25th February 2013.
#Magicdraw 12.5 update
Oracle Java 6 update u39 and higher or Java 7 update u13 and higher have undocumented changes in the way the threading works.

As a result, MagicDraw 17.0.2 &17.0.3 and older versions are not compatible with Java 6 update u39 and higher or Java 7 update u13 and higher. It was Oracle’s mistake in introducing the undocumented behavior changes that have caused the incompatibility between Java and our product. What is the Reason That Has Caused Java 6 Update 39 and higher or Java 7 Update 13 and higher Incompatibility With Our Products? Java versions 1.6.0_39 and higher or 1.7.0_13 and higher are incompatible with MagicDraw v17.0.2 (prior SP3) and v17.0.3 (prior SP1) and older versions.
