New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 699930 link

Starred by 5 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

NaCl modules 'load' event firing in packaged apps terribly broken.

Project Member Reported by mtomasz@chromium.org, Mar 9 2017

Issue description

58.0.3027.0, but it's broken on 56 and 57 too, and most likely it's been broken since 34 (See  crbug.com/350445 ).

The 'load' event is dispatched few minutes too late, or until the next relayout. Such relayout may never happen when loading in background page in NaCl module. We do that in two component extensions: Image Loader and ZIP unpacker.

Note, that the load event works if the NaCl module is loaded in the global scope of the background page. However, loading the NaCl event in any event handler, such as onLaunched fails.

This became visible now, as we try to defer loading a NaCl module, or unload and reload when needed in order to fix  crbug.com/517741 .

We do a workaround suggested by  crbug.com/350445  few years ago and it somehow works, but this is terribly broken, and should get fixed. With the hack loading a module takes less than a second. Without the hack, takes minutes.
 
Cc: hidehiko@chromium.org
Owner: bradnelson@chromium.org
Status: Assigned (was: Available)
bradnelson@, could you triage?

Comment 2 by tkent@chromium.org, Mar 15 2017

Components: -Blink>HTML>Embed Blink>Loader

Comment 3 by w...@chromium.org, Mar 15 2017

Ick. Is this why the TTS Engine extension for CrOS tries to dereference embed.lastError, to nudge the NaCl embed into being loaded..?

Comment 4 by mtomasz@google.com, Mar 15 2017

Most likely. We do embed.offsetTop to force relayout and get the load event dispatched, but I guess embed.lastError works the same way.

Comment 5 by w...@chromium.org, Mar 19 2017

Looks like a dupe of issue 371059?
Might this problem be the direct cause of the Zip Unpacker behavior described in #658465?

It seems that that bug occurs when the Image Loader extension fails to load the image files contained inside the zip file, causing the Zip Unpacker extension to not be able to mount the file completely and falling into the "Operation taking longer than expected" loop.

Sign in to add a comment