If this happens on 68, we will not block 69 on it (not a regression). 

If we have a fix, we can still consider merging it though.

Can we get any log from the device? The log messages in chrome://gpu/ could be useful too.

Just to narrow down what are we looking at, I understand this happens on M68 
and M69; what about M70, is it working with delay or not? And, with black bars 
or without? Just to confirm, this uses the NaCl API, not the Web?

Do we know when this last worked? Is it possible this was a change on the Keep side?

69.0.3497.73 beta -- black bars, very slow
70.0.3538.7 dev -- no black bars, hw overlay, but still high latency (50ms+)

Side note for Ink team: with M70 dev, we see tearing when panning/zooming due to hw underlays. Ink will need to do version detection to decide how to handle panning/zooming.

I got my hands on a Dru, M69.0.3497.87 (official build); opened Keep Chrome App (has a 
little chrome logo over the icon, right?) -- can't repro the black bars on the sides 
of the grey back-canvas. wfurr@, can you plz try to repro that?

I'm going to flash now the Dru to an M70 w/ latest firmware to check the latency
and overlays.

On my Scarlet M71, Keep Chrome App drawing area doesn't get promoted to 
overlay because is partially occluded by the upper and lower menu bars,
see the attached screenshot, where I had the tint-gl flag on. So this is
a WAI...? Same Cr version promotes to overlay correctly a canvas 3D 
with lowLatency (and enable-experimental-web-platform-features on).

Deleted: 3986871272375314336.jpg 404 KB

	3986871272375314336.jpg 404 KB View Download

Miguel, that's the Keep Android app.

This bug is about the Keep Chrome app.  If you have both installed, look for the Keep icon with a Chrome badge in the lower right corner.

I do see the black bars and high latency with the Keep Chrome app on M70 as well.

The Keep Chrome app does use the Native Client API.

It's possible this is an issue with the Keep or Ink code, but I'm not sure how or what would have changed recently to cause this specifically on Dru and not Eve or other devices.

The Keep Chrome app looks fine on 69.0.3497.35 beta on Dru.  I'm updating now to a newer version and will report in.

Another tip to tell the right app, the Keep Chrome app has the pen toolbar across the top, whereas the Keep Android app has the tool drawer at the bottom over the canvas.

After the update, Dru on 69.0.3497.87, Keep Chrome app seems fine.

My other Dru updated to 71.0.3544.0 canary.  No black bars, but latency/performance is bad.  I think the additional latency is dropped frames.  Everything feels a lot slower in M71 compared to M69 on Dru.  The UI transitions, signing in, etc.

#9: hark, you're right :-P  
 My Dru wasn't in Dev mode, so I switched back to my scarlet and there
 arose the confusion.  
Scarlet M71.0.3544.0 canary, with Keep Chrome App turns the drawing area
 to overlay correctly.  I don't see it much less responsive than usual.

Could it be a general slow down? there's a thread about that with some
potential flag(s) that might minimize it:
https://groups.google.com/a/google.com/forum/?utm_medium=email&utm_source=footer#!msg/chrome-speed-releasing/x71JmAxySek/yaStvZeCBgAJ

Closing this bug. It appears the issue was tied to Keep and has been fixed. mrcasey/wfurr will investigate what caused the regression.