Do you mean TraceView?
I tried with Debug.startAllocCounting, Debug.startMethodTracking(...),
made a lot of reports, but the result is the same:
practically same % spent in all methods. Just everything is slower in
absolute time during the GLSurfaceView rendering.
For example, the GL effects I use take more time, but the distribution
of method times is exactly the same. To be brief, everything is
slower, proportionally.
Memory allocation is fine, no leak, no increase in heap...
On Jul 22, 7:17 pm, RichardC <richard.crit...@googlemail.com> wrote:
> Run the profiler.
>
>
>
>
>
>
>
> On Sunday, July 22, 2012 5:41:55 PM UTC+1, Tamás Kovács wrote:
>
> > I know that System.gc() is needless and discouraged, and I don't try
> > to suggest otherwise, but the point is that it shouldn't cause issues
> > either (i.e. it should be useless at most).
>
> > If I add the following code to my Activity.onPause(), then my
> > application will be slow after the second start of the activity:
>
> > if (isFinishing()) {
> > System.gc();
> > }
>
> > I.e. the framerate in my GLSurfaceView will be reduced by 50%. If I
> > remove the System.gc() call, everything is totally fine, no matter how
> > many times I start the activity again (i.e. start it again after it
> > was finished()).
>
> > The relevant source codes here:
>
> >http://stackoverflow.com/questions/11601914/system-gc-causing-slowdow...
>
> > Please help! GC is discouraged but shouldn't mess up the View/Layout
> > destroying system of Android.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
