There comes a time in any mobile project of significant size, where no matter how careful you were, you missed something (or you over optimized) and you have memory leak.
WTK2.5 comes a long way to show the count of live objects in memory, but it does not allow to trace the references to see why the heck it is not garbage collected and what is referencing it. It works pretty much the same way as Memory Monitor that ships with WTK, by connecting to the emulator vm and extracting info from there.
That is why I like YourKit Java Profiler as it does exactly that, help you trace those unwanted references.
technorati tags: j2me profiling yourkit memory leak
Post a Comment