Did you take a look at the allocation tracker in DDMS? This is a
really useful tool - you can see exactly what objects you are creating
in your control loop.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Dev
Note also that some Java 5 idioms will allocate objects "for you" if you're
not careful.
For example, string concatenation like:
myString = "value of x is" + x;
Will allocate a temporary StringBuilder object each time this statement is
executed.
Other cases are using for () to iterate over cert
Without any detail about what your core loop is doing, there is no way we
can answer that.
The general rule of thumb is "don't allocate" and you won't get a GC at all.
On Thu, Apr 2, 2009 at 10:53 AM, admin.androidsl...@googlemail.com <
admin.androidsl...@googlemail.com> wrote:
>
> So my app is p
3 matches
Mail list logo
