Viewing and Editing Project Properties
Running Projects in the Emulator
Searching the WURFL Device Database
Finding Files in the Multiple User Environment
Manage Device Addresses (device-address)
Build a Project from the Command Line
Packaging a MIDLet Suite (JAR and JAD)
Command Line Security Features
Change the Default Protection Domain
Manage Certificates (MEKeyTool)
Running the Payment Console From the Command Line
Run the Java Heap Memory Observe Tool
JSR 82: Bluetooth and OBEX Support
JSR 135: Mobile Media API Support
JSR 177: Smart Card Security (SATSA)
JSR 205: Wireless Messaging API (WMA) Support
JSR 211: Content Handler API (CHAPI)
JSR 226: Scalable 2D Vector Graphics
JSR 238: Mobile Internationalization API (MIA)
JSR 256: Mobile Sensor API Support
The Java Heap Memory Observe Tool (also known as the Heap Walker) records detailed information about the Java heap at a specific point in the virtual machine execution. It collects and displays:
global pointers
data for all objects (classes, sizes, addresses and references)
addresses for all roots
names of all classes
Please note the following:
The memory profiler uses the same connection technology as the debugger. Because they use the same transport layer, the memory profiler and Java debugger cannot be used simultaneously.
Note - For the memory profiler, the Xrunjdwp -suspend option must be set to n.
The memory monitor slows down your application startup because every object created is recorded.
The memory usage you observe with the emulator is not exactly the same as memory usage on a real device. Remember, the emulator does not represent a real device, it is just one possible implementation of its supported APIs.
See also: Run the Java Heap Memory Observe Tool