I've already worked on making ViewDebug less slow. I've made
reasonable
progress as measured by timings on the original code compared to
timings
after the changes.
My issue isn't about performance. I am trying to figure out why it is
hanging. As I said at the beginning:
I have put log statements into ViewServer and ViewDebug, so I see
that
that when it hangs: ViewServer calls viewServerWindowCommand(),
but
ViewDebug.dispatchCommand() does not get called. So execution is
getting stuck somewhere in between.
Do you have any idea why this hang would happen? or suggestions on how
to
debug it?
-Sam
On May 17, 12:42 pm, Romain Guy <[email protected]> wrote:
> > Examining the possibility of using ViewServer/ViewDebug as part of a test
> > framework -- a way to examine the phone's GUI state after user input.
>
> I would highly recommend you didn't use the ViewServer for this. Why
> don't you just walk the view hierarchy and examine its state?
>
> > What is the problem with the current ViewServer/ViewDebug that might prevent
> > it from being used that often?
>
> Because a ViewServer dump is very expensive as it relies heavily on
> reflection and it can take several seconds to perform a dump.
>
> --
> Romain Guy
> Android framework engineer
> [email protected]
>
> Note: please don't send private questions to me, as I don't have time
> to provide private support. All such questions should be posted on
> public forums, where I and others can see and answer them
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"android-framework" 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-framework?hl=en
-~----------~----~----~----~------~----~------~--~---
