cblume@, can you grab a galaxy note edge from the device library and see if this bisects? Thanks!

We do not have a Galaxy Note Edge to test with.
However, we do have a Galaxy Note 4, which shares the same GPU....I think.

It seems like there is a version of both the Galaxy Note Edge and the Galaxy Note 4 which uses Adreno 420 and another version which uses Mali T-760. I can test on a Mali T-760.



serphen@gmail.com, can you go to chrome://gpu and scroll down to the "GPU0" part of the table?




I just grabbed the latest Canary (69.0.3465.2) and could not repro.

This test device is running Android 4.4.4 though. I don't want to update the Android version on this device since I can't set it back for the next tester.

Sure.
The device has a Adreno 420, driver version 104.0, pixel shader version 3.10, vertex shader version 3.10.

I will let you know if I can figure out better way to repro or if I can repro on a cloud device (to be sure it's not hardware related).

Well shoot.
I'll see if any of our other Galaxy Note 4s have the Adreno 420 and not the Mali T-760.

I tried the exact Canary build which you reported and was not able to reproduce the error on the Mali T-760.

I found a Galaxy Note 4 with an Adreno 420.
In installed that exact Canary build but could not reproduce the bug.
This test device was on Android 5.1.1 as well.
Driver version 104.0, pixel shader version 3.10, vertex shader version 3.10.

I lucked out to have a device so similar. But I still cannot reproduce. :(



Maybe the difference between Android 5.1 and 5.1.1 is significant?
Or maybe there was something between our two tests?
Does this reproduce every time for you or do you need to do something special to trigger it?


Just to double check, at the top of chrome://gpu in your Canary build, under "Graphics Feature Status" everything is green (Hardware accelerated) except for:
- Multiple Raster Threads: Disabled
- Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
- Out-of-process Rasterization: Disabled
- Hardware Protected Video Decode: Unavailable
- Skia Deferred Display List: Disabled
- Skia Renderer: Disabled
- Surface Synchronization: Disabled
- Viz Service Display Compositor: Disabled
right?

If we have no clues from the above things, we might need to start comparing chrome://flags which is not ideal.

Ping

Friendly ping.
I am unable to reproduce this. Are you still seeing this behavior?

Closing since I cannot repro and/or it may already be fixed.

If this problem still exists please feel free to re-open it.