Status Update
Comments
an...@google.com <an...@google.com> #2
I notice the same issue and LogCat shows the following message:
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
an...@google.com <an...@google.com> #3
Same here.
"Google Play services out of date. Requires 3159100 but found 3136130"
"Google Play services out of date. Requires 3159100 but found 3136130"
pi...@gmail.com <pi...@gmail.com> #4
me as well....
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
pi...@gmail.com <pi...@gmail.com> #5
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
pi...@gmail.com <pi...@gmail.com> #6
Having the same issue:
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
pa...@google.com <pa...@google.com> #7
same
pi...@gmail.com <pi...@gmail.com> #8
SAME ! - Google can't do sth working in 100 percent?
pe...@google.com <pe...@google.com> #9
same issue - Google Play services out of date. Requires 3159100 but found 3158130
pi...@gmail.com <pi...@gmail.com> #10
Having the same issure:
07-26 03:14:00.731: W/GooglePlayServicesUtil(2566): Google Play services out of date. Requires 3159100 but found 3136130
07-26 03:14:00.731: W/GooglePlayServicesUtil(2566): Google Play services out of date. Requires 3159100 but found 3136130
pa...@google.com <pa...@google.com> #11
API 18 (4.3) same issue
07-26 03:54:03.303: W/GooglePlayServicesUtil(1207): Google Play services out of date. Requires 3159100 but found 3158130
07-26 03:54:03.303: W/GooglePlayServicesUtil(1207): Google Play services out of date. Requires 3159100 but found 3158130
pi...@gmail.com <pi...@gmail.com> #12
Same issue here.
Description
Steps to reproduce the problem
Problem Description
In the latest changes in dev tools, a serious performance issue was introduced when using the mouse to move the time frame around if it's smaller than about 200ms. Whereas in the previous versions this interaction was fully smooth, it now became extremely slow and seems to render the moving action at only about 4fps with massive input delay.
This is almost certainly a bug, because the scrolling seems to work fine if you use a larger window, and the larger windows don't seem to show any less information. So the same operations on a strictly smaller set of results somehow gets slower, this indicates there's probably an oversight somewhere.
I used developer tools on the developer tools instance to get a performance trace of this slow behavior, which revealed the following:
Additional Comments
See attached a performance recording of the slow behavior. There's also an image of the timeline of this recording for convenience. First the problematic behavior is triggered when zoomed in, then around 6s the timeline is zoomed out and dragging is performed again for comparison.
Summary
Moving performance recording time frame by dragging gets extremely slow when zoomed
Additional Data
Category: Developer Tools
Chrome Channel: Stable
Regression: Yes