When given so little information, no. The best we can do is give vague generalities, such as "use Traceview". But this is not such a bad "vague generality" after all. Traceview is the basic tool in the Android environment for finding memory leaks as well as solving other similar debugging problems.
See http://groups.google.com/group/android-developers/browse_thread/thread/66e81163ab4599c8 for more details relevant to getting native code to output under Traceview. On Mar 26, 4:46 am, sunskyor sunskyor <[email protected]> wrote: > Hi, > > I found the investigation of jni memory leak is too hard to execute. > > Anybody can give some clues for such problem?? > > Thanks. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
