Take 30 seconds, help fix our export woes

Done.

tumira

I posted there, but my thread hasn't gone live yet...

done, and told firends to do it as well!

Done...

Wow this is almost up to 200 stars (started near 30) Good Work Everyone

Mild bump.

Looks like things are moving quickly! In case you missed it[quote:2hrrrivb] Okay, for anyone responding to this issue with smoothness/vsync issues here's a simple way you can help us better understand the problem:

1) Download this experimental Chromium build (Windows only) and extract it to a temporary folder: https://drive.google.com/file/d/0BzudLt ... sp=sharing

2) Run it with the command line flag --hardware-vsync-only. (Must be passed in via the command line, it doesn't appear in about:flags)

3) Test content that you've had trouble with in recent Chrome builds. Is it smoother, more jittery, or about the same?

4) Close the browser then re-run with the command line flag --software-vsync-only.

5) Test the same content again. Is it smoother, more jittery, or about the same?

6) Visit about:gpu and save that page's contents to an HTML file.

7) Report your findings on this bug, making sure you attach your systems about:gpu page.

I appreciate your help and patience while we narrow down this issue!

Quoted from https://code.google.com/p/chromium/issu ... ?id=422000

Yup. The stars seem to be working: the devs are back on board.

I just ran through some tests with the experimental build, plus stable/canary, and posted my findings in the bug report. Hope a few others will do the same.

Basically, it seems like the current stable is really pretty good; however, Canary has some odd monkey business going on that could lead to a future regression if it's not addressed. Here's hoping this will keep the fire on the dev team.

Basically, it seems like the current stable is really pretty good; however, Canary has some odd monkey business going on that could lead to a future regression if it's not addressed. Here's hoping this will keep the fire on the dev team.

Indeed. I have noticed this as well. It's like it works great and then every now and then it janks... I get all excited then defeated in a matter of about a minute. lol - I just posted my results.

Kyatric

Can we pin this post ?

Kyatric

Can we pin this post ?

It already has Google's attention, we now need to do this:

> Kyatric

>

> Can we pin this post ?

>

It already has Google's attention, we now need to do this:

Yup, it does take a little more time, but this info is what the devs over at Google really need.^^^

TiAm

Do they know that the issue occurs on Android also ? The ticket just mention about windows.

tumira

That's a good point. I haven't experimented with the beta versions of crosswalk much, but from what I've read on the forums it sounds like v8 and v9 are affected by this to some degree.

To tell you the truth, I assumed the bug report linked in this post was 'generic', and was not specific to one build of chrome. Now that I look at it, I can see that it says "OS-Windows".

I'll post about this in the bug report...maybe we need a new, more generic bug definition. :/

Thanks TiAm for your work. I hope they implement the fix on both mobile and desktop version.