[M61] Injection:, [Windows 7x86] .swf for [OTS: 46055, 45754, 28635) regression test cases does not load. Chrome: 61.0.3163.91[Blocker] for the rest of supported platforms. |
|||||||||||||
Issue descriptionBLOCKING: From first build of Chrome M61 and until Chrome 61.0.3163.79 it used to fail on Windows 7 x86 but starting with Chrome 61.0.3163.91 it also fails on all other supported platforms. Injection for Windows 7 x86 - first build of Chrome M61. Injection for Windows 7 x64, Windows 10 and Mac Chrome 61.0.3163.91. FAIL: Windows 7x86, Chrome 61.0.3163.59, FP 26.0.0.151 PASS: Windows 7x86, Chrome 60.0.3112.101, FP 26.0.0.151 PASS: Windows 7 x64, Chrome 61.0.3163.59, FP 27.0.0.117 PASS: Windows 10, Chrome 61.0.3163.59, FP 27.0.0.117 PASS: Mac 10.11, Chrome 61.0.3163.59, FP 27.0.0.117 PASS: Windows 7 x64, Chrome 61.0.3163.79 , FP 27.0.0.134 PASS: Windows 10, Chrome 61.0.3163.79 , FP 27.0.0.134 PASS: Mac 10.11, Chrome 61.0.3163.79 , FP 27.0.0.134 FAIL: Windows 7 x64, Chrome 61.0.3163.91 , FP 27.0.0.134 FAIL: Windows 10, Chrome 61.0.3163.91 , FP 27.0.0.134 FAIL: Mac 10.11, Chrome 61.0.3163.91 , FP 27.0.0.134 What steps will reproduce the problem? !. Unzip attachment. 2. Drag and drop the html from URLQueryParsing folder to Chrome browser to repro the issue on Windows 7 x86. 3. Click on each URL and on any .swf to load the page. What is the expected result? No warning, .swf to load. What happens instead? "This type of file can harm your computer. Do you want to open it anyway?" warning displays. OTS.png is attached. Selecting "Keep" option in the warning and clicking on a loaded .swf results in "This file does not have a program associated with it for performing this action" another warning to display. See attached screen shot OTS1.png. It's M61 injection for Windows 7 x86 only.. Works OK on Windows 7x86with M60. Please use labels and text to provide additional information. Workaround: Run the test in M60. Chrome injection point. You are probably looking for a change made after 474898 (known good), but no later than 474903 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/dbe2894b5f9fc7b0d480eefe87 9e8cb5d087d71c..f2b5ef577de5bea5bcc93375eeb2e5c4ea4def7f
,
Sep 15 2017
,
Sep 15 2017
,
Sep 15 2017
,
Sep 15 2017
,
Sep 15 2017
,
Sep 15 2017
,
Sep 15 2017
,
Sep 25 2017
Different injection point on 10.13 and 10.12. PASS: OSX 10.13 and 10.12 - Chrome 61.0.3163.100 (Official Build) (64-bit) - FP 27.0.0.154 PASS: OSX 10.13 and 10.12 - Chrome 62.0.3202.29 (Official Build) beta (64-bit) - FP 27.0.0.154 PASS: OSX 10.13 and 10.12 - Chrome 63.0.3218.0 (Official Build) dev (64-bit) - FP 27.0.0.154 FAIL: OSX 10.13 and 10.12 - Chrome 63.0.3223.0 (Official Build) canary (64-bit) - FP 27.0.0.154 Bisect was ran on OSX 10.13. Bisect result: You are probably looking for a change made after 502517 (known good), but no later than 502518 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/7dd05b8243f89a1af4927912e5ca9750bdc9bdad..869d13439f5712193f27ded17a6300b67fd318f3
,
Sep 26 2017
That last bisect doesn't look correct. The CL referenced in the changelog only runs on Chrome OS.
,
Sep 26 2017
From first build of Chrome M61 and until Chrome 61.0.3163.79 it used to fail on Windows 7 x86 only. I've added build bisect results before: CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/dbe2894b5f9fc7b0d480eefe87 9e8cb5d087d71c..f2b5ef577de5bea5bcc93375eeb2e5c4ea4def7f Starting with Chrome 61.0.3163.91 it also started to fails on all other supported platforms. Chrome 61.0.3163.79 is Good build for Windows 7 x64 and Mac 10.11. 10.12 Chrome 61.0.3163.91 is first Bad build build for Windows 7 x64 and Mac 10.11. 10.12. If you want me to run bisect again within this range, please let me know.
,
Feb 11 2018
|
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by ihf@chromium.org
, Sep 2 2017