Video link: https://storage.cloud.google.com/chromiumos-test-logs/bugfiles/cr/703902/Mar%2021%202017%205-25%20PM.webm?_ga=1.62491628.1381462633.1480703761

Atatched screenshot.

+marcheu any ideas if the log below may be related to this?

Looking at the log for src/gpu/command_buffer/service/gles2_cmd_decoder.cc it appears the code that prints this has not been touched in years, so I am assuming this is something being passed up from the graphics stack.

Sahiti, is this only ever happening in Caroline? 

...
[16150:16150:0321/170757.571267:ERROR:gpu_command_buffer_stub.cc(900)] Got WaitForGetOffset command while currently waiting for offset.
[16150:16150:0321/170757.572566:ERROR:gles2_cmd_decoder.cc(5279)] Error: 4 for Command kReadPixels
[16150:16150:0321/170800.042243:ERROR:gles2_cmd_decoder.cc(17396)] [.DisplayCompositor-0x94f1570f300]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[16150:16150:0321/170800.042337:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.042596:ERROR:gles2_cmd_decoder.cc(17396)] [.DisplayCompositor-0x94f1570f300]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[16150:16150:0321/170800.042642:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.042700:ERROR:gles2_cmd_decoder.cc(17396)] [.DisplayCompositor-0x94f1570f300]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[16150:16150:0321/170800.042736:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.042883:ERROR:gles2_cmd_decoder.cc(17396)] [.DisplayCompositor-0x94f1570f300]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[16150:16150:0321/170800.042928:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 1 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.073112:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.073631:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.073710:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.074296:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 1 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.089336:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.089800:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.089892:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.090587:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 1 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.110652:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.111426:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.111552:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.112144:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 1 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.142705:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.143231:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.143314:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.144209:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 1 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.165110:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.165522:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.165583:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.166212:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 1 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.182071:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.182738:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.182872:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.183473:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 1 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.203855:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.204195:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.204255:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.204759:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 1 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.224507:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.224810:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.224870:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[16150:16150:0321/170800.225182:ERROR:gles2_cmd_decoder.cc(9629)] [.DisplayCompositor-0x94f1570f300]RENDER WARNING: texture bound to texture unit 1 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
...

these happen all the time, they're probably unrelated

Reproduced on other devices as well.

Tested on veyron_jerry, samus. Build: 9334.18.0 / 58.0.3029.31

These systems don't appear to be under intense memory pressure. Any ideas on why these might hang and whom might be good at debugging such a 'pages unresponsive' failure?

If this happens reliably for 5 apps, we probably do need to block beta on this, many beta users are Googlers whom are likely to have >5 on a regular basis, and this would probably be grounds for leaving beta channel for such users.

This is not quite P0 yet, but we are nearing that point soon.

Is this scenario reproducible outside QO usage?

+more folks whom may be able to look at this.

Hi Atul, Nagmani - can you investigate as a priority? Thx!

Unable to reproduce this issue with pixel and acer x-86 chromebooks available with us. Is there a specific set of files that is causing this issue? We used QO Version: 119.2042.2044 that is available on Chrome Web Store. Following are the chromebook details 

1. Chromebook Pixel - 
     Version 58.0.3029.31 dev (64-bit)
     Platform 9334.18.0 (Official Build) dev-channel link
     Firmware Google_Link.2695.1.169

2. Chromebook x86 - 
     Version 58.0.3029.31 dev (64-bit)
     Platform 9334.18.0 (Official Build) dev-channel link
     Firmware Google_Link.5216.239.109

Reproduced issue on caroline. 

Build: 9334.28.0 / 58.0.3029.40

Testcase : https://testtracker.googleplex.com/efforts/testcase/detail/12502445

Office files used for testing: https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/703902/

We do a sanity check with these files for every release and not seen this issue before.

Able to reproduced the issue for file 'All feature mix.docx'. Following steps I have performed - 
1) Open 'All feature mix.docx' file in Chrombook
2) Do some editing(adding some content) between 2 to 7 pages.
3) After few min page unresponsive dialog is appeared.

other observation - 
--------------------
1. Issue is not reproducible with other mentioned files in this issue.
2. Issue is reproducible with all Chrome version i.e. Stable(57), Beta(58) and Dev(59)
3. Issue is reproducible with older Quickoffice versions as well. 
4. Issue is reproducible with 'All feature mix.docx' file only, with other files we are unbale to reproduced.Hence looks like it is file specific issue. 

Any update here? This is marked as a stable blocker, and we are nearing stable promotion for 58. 

Whom is the right owner here?

Hi, will get an update from the team to see how the investigation is going for this. But please note that from the investigation so far (see comment #15), it looks like:

- the problem is file specific, the problem is not caused by just opening multiple files 
- the issue is reproduced in the problem test files when it is opened and the user edits between pages 2 to 7 causing the unresponsiveness. The team is investigating what in that document in those specific pages is causing an issue. 
- also noticed that this file specific issue has been present in older versions of Quickoffice Chrome which are already out in the public domain.

So my question is should this really be a release stable blocker? If this is file specific and is already out in the public domain? 

The issue occurs only in a rare scenario when there is single run spanning across more than 2 pages. This case was never considered in the pagination logic and the bug was present since the beginning. 

Right now the fix is in progress. Since the fix will be in the core logic of pagination, we will need time to thoroughly test the fix after we find correct fix. 

@btbhthompson - should this still be a releaseBlock-Stable? 

The Synerzip vendor team have found a fix for the unresponsiveness issue for that specific file, but it looks like it has surfaced 2 other issues. So even with the unresponsiveness fix you will still see errors due to these other issues. These will take some time to completely resolve. 

If this is not really a regression, as suggested by comment 18, then we don't have to block stable on it.

Moreover if we are confident this will not impact many users, that would also put it out of the stable blocking category.

I will tentatively remove it, if we can get a fix for this we can still potentially get into a second stable.

Reproduced this issue again. Build: 9592.66.0, 60.0.3112.72

Feedback report link: http://feedback/#/Report/68799045583

This may not be a file specific issue as reported in c#15 because I have not opened 'All feature mix.docx' file when the issue reproduced.