If you experience an unacceptable performance impact then you should When the HotSpot(TM) JVM is used, the approximate performance impact for general purpose applications is shown in the table below.Īgain, it is recommended that you measure the impact on your classes. The performance impact of flow obfuscation varies depending upon Note that the size increase will vary from application to application and you should measure the impact on your bytecode. The table below shows the approximate bytecode size increase that could be expected in a compressed JAR file for typical applications. It is a trade off between the degree of protection against decompilation and bytecode size and speed. The disadvantages of flow obfuscation are that your bytecode will run slower and will be slightly larger. To switch off flow obfuscation, you should select none in the "Obfuscate Control Flow" list. Selecting normal results in more flow obfuscation than would be done if you selected light. Selecting aggressive results in more flow obfuscation than would be done if you selected normal. while or for) constructs so that they cannot be directly decompiled back If you select light, normal or aggressive in the "Obfuscate Control Flow" list, Zelix KlassMaster will obfuscate Then, after it has been read, the original file will be overwritten with the new change details. Also, if the change log out file name is the same as the input change log file name Then only the second set of name changes will be retained. If you obfuscate twice with the same change log file name Note that only the latest changes will appear in the file. Without a change log, debugging the stack traces caused by uncaught exceptions is extremely difficult if not impossible.Īlso, you can use the change log as an input change log when you obfuscate your next release so that the same obfuscated names will be used. With a change log, you can use the Stack Trace Translate tool to translate obfuscated stack traces. It is recommended that you always select this option. In the input field to the right of the option. The change log file will be given the name that you entered If you select "produce a change log file" Zelix KlassMaster will write the name changeĭetails to a change log file. This ensures consistent renaming across releases which can be vital in certain situations (e.g. If you select "use input change log file" Zelix KlassMaster will read the name changeĭetails from the existing change log file that you named in the input field to the right of the option. Obfuscate Name Exclusions dialog will be obfuscated. Generally speaking, all package, class, field and method names not excluded using the Note that there is no name obfuscation option. Zelix KlassMaster provides the following obfuscation options. Java Obfuscator - Zelix KlassMaster - Obfuscate Options
0 kommentar(er)
