mBooster 2.6.4 Release Notes

 

 

New in mBooster 2.6.4: (Release date: 21 November 2007)

 

Improvements

• Allow Class Merging in Simple mode to use Max Instances field to identify classes to exclude from merging

Bug fixes

• Internal NullPointerException reported in step 3 due to null array type

 

New in mBooster 2.6.3: (Release date: 20 August 2007)

 

Improvements

• Remote access support for stand alone mBoosterZip

Bug fixes

• Generated code can cause an IncompatibleClassChangeError from a strange INVOKESPECIAL instruction
• Internal NullPointerException reported in step 39

 

New in mBooster 2.6.2: (Release date: 3 April 2007)

 

Improvements

• mBooster workaround for defect in some Sony Ericsson devices
• mBooster workaround for defect in devices using intEnt JVM

Bug fixes

• Class merging fails given an interface duplicating an unused library method

 

New in mBooster 2.6: (Release date: 5 February 2007)

 

New Features

• Automatic checking and reporting of Reflection API use within input application
• Concurrent session support for mBooster remote access server, via MAX.CONCURRENT.SESSION property

Improvements

• New CLASS.MERGING.EXCLUDE property to prevent a specified class from ever being merged
• Add option to mBoosterPng to create PNG files with store-mode compression
• Enable PNG Recompression step by default

 

 

Bug fixes

• mBooster workaround for a JVM defect in Sony Ericsson JP-6 and JP-7 devices
• Internal NullPointerException reported in step 29 (mBooster 2.5.X), or 27 (in 2.1)
• NullPointerException in step 16 for app with large amounts of redundant code
• mBooster terminates with FATAL: Out of memory
• mBooster fails when input class contains empty infinite loop
• Class Merging fails given an invokespecial instruction resolving into unusual class
• Internal NullPointerException reported in step 3
• Typo in documentation for Advanced Class Merging

 

New in mBooster 2.5.4: (Release date: 25 July 2006)

 

Improvements

• Reduced heap memory usage to work around a JVM defect on certain handsets
• Property to set maximum class size that class merging can form

 

 

Bug fixes

• Non-graceful termination on recieving invalid class files
• Class merging can lead to method being removed when concrete and abstract class implmenting library interface are merged
• Internal NullPointerException reported in step 23
• Concurrent modification error in step 21

 

New in mBooster 2.5.3: (Release date: 3 July 2006)

 

Bug fixes

• Internal error reported in step 36
• Special field for class merging optimization in ADVANCED mode named wrong in documentation
• Class Merging does not respect subclasses of merge candidates that are marked as AVOID classes

New in mBooster 2.5.2 (Release date: 8 June 2006)

 

Improvements

• User able to direct mBooster to never overload field names
• Resource Packing Optimization support for Vodafone Sound API

Bug fixes

• Class Merging fails or leads to optimized application failing

New in mBooster 2.5.1: (Release date: 30 January 2006)

 

New features

• Class merging of instantiated class
• Resource file access profiling
• Added client/server capability through mBooster Remote Access Server
• Redundant field elimination and redundant field access elimination
• FAST property to improve mBooster execution time

 

 

Improvements

• Added CLASS.MERGING.NOCHECK.CHECKCAST and CLASS.MERGING.NOCHECK.ARRAY.STORE properties to turn off conservative checks in class merging optimizations.

 

 

Bug fixes

• Null pointer exception (step 38 in mBooster 2.1, step 34 in mBooster 2.0)
• mBooster fails when class contains access of static field/method in public class in different package when referenced class has default visibility parent class containing the field/method
• DoJa support disabled in mBooster 2.1. DoJa support is re-enabled in mBooster 2.1.1 and 2.5 streams
• Incorrect StackMap attribute produced for constructor containing inlined method call
• Null pointer exception during Class Merging (step 14 in mBooster 2.1, step 12 in mBooster 2.0)
• Method inlining of interface method calls may result in incorrect code.

 

 

Deprecated functionalities

• RESOURCE.PACKING.PRELOAD.ENABLED property is now deprecated, and is replaced by the new property RESOURCE.PACKING.MODE. This backward incompatible change will affect existing properties files.

 

 

— Previous page – Contents – Next page —