Issue metadata
Sign in to add a comment
|
Web Worker's importScripts waits long data URI
Reported by
manjian2...@gmail.com,
Mar 1 2018
|
||||||||||||||||||||||
Issue descriptionExample URL: See the attachment Steps to reproduce the problem: 1. Get chrome://inspect?trace ready to trace: install WebViewInstrumentation.apk and open, select "Javascript and rendering". Press record. 2. Open my attachment. 3. Stop recording when the noise image is shown. 4. Observe the "DedicatedWorker thread". Just after the v8.NewContext, the first v8.Execute has a long wait interval about 90ms long. What is the expected behavior? Don't wait. What went wrong? The url resource request is sent back to the main thread of render process, where render process decide to handle locally. But the worker thread still has to wait for the main thread of the render process. Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? N/A Chrome version: 66.0.3357.2 Channel: stable OS Version: 6.0 Flash Version: The attachment exploit.tar.xz is the page trigger this problem. before_fixed.png shows the trace before fix.patch applied. after_fixed.png shows the trace after fix.patch applied
,
Mar 6 2018
manjian2006@ -- Thanks for reporting this issue. Could you please share the WebViewInstrumentation.apk along with the screen cast of the actual issue for better understanding. How can the fix.patch file be applied to get the fix, the file seems to be not compatible on Samsung S7 Android 6.0.1 or on Windows 10? Thanks in advance!
,
Mar 6 2018
This problem belongs to the WebKit component. The the patch is applied in the source tree of the chromium project like: patch -p 1 <fix.patch I don't think a screen cast is helpful in this issue. Because it belongs to the loading module of the WebKit component.
,
Mar 6 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 6 2018
,
Mar 8 2018
These are known issues: requesting the worker main script and importScripts go through the main thread now. It's tracked variously in issue 706331 and issue 741227 .
,
Mar 8 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by pnangunoori@chromium.org
, Mar 5 2018