URL "chrome://dxva" is not documented
Reported by
xmillsa@tutanota.com,
Oct 17
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36 Steps to reproduce the problem: 1. Visit chrome://dxva on windows What is the expected behavior? The url is not documented and not listed on chrome://chrome-urls/, so ERR_INVALID_URL is expected to appear. What went wrong? Page is displayed, but with confusing error message. It looks like chrome://settings page, there is searchable menu bar with "Search settings" placeholder but title is null. Also it displays some weird javascript error instead of content. Screencast is attached. Did this work before? N/A Chrome version: 70.0.3538.67 Channel: stable OS Version: 6.3 Flash Version: N/A
,
Oct 18
Unable to reproduce the issue on Win-7 and Win-10 using chrome reported version #70.0.3538.67 and latest canary #72.0.3584.0. Attached a screen shot for reference. Following are the steps followed to reproduce the issue. ------------ 1. Navigated to chrome://dxva on windows. 2. Observed the error ERR_INVALID_URL as expected. xmillsa@@ - Could you please check the issue on latest canary #72.0.3584.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Thanks...!!
,
Oct 18
Our win10 PC is offline. We don't see a way to install the canary build from an offline (standalone) installer. Note: Our current profile is clean (no apps, extensions or plugins (though we don't see how any of them could affect this)).
,
Oct 18
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
,
Oct 25
xmillsa@ Request you to update Chrome to the latest Canary 72.0.3591.0 or Stable 70.0.3538.77, retry the issue and update the thread with the observations, which will help in further triaging of the issue. URL for downloading the latest Canary/Stable builds: Canary : https://www.google.com/chrome/canary/?platform=win64 Stable: https://www.google.com/chrome/?platform=win64 On the latest Canary 72.0.3591.0, on navigating to chrome://dxva, can observe the error ERR_INVALID_URL as expected Thanks..
,
Oct 25
In case we are speaking chinese, we are repeating what we've already said: our win10 PC is offline. We don't have internet access. You are requesting us to install the canary build without the internet connection. How are we supposed to do it? What we did is to download the .exe file from the link you provided in comment C#5 using our win8 computer and then copy-paste it to our offline win10 computer. However, the ChromeSetup.exe file requires internet in order to install the canary build. For the latest stable 70.0.3538.77 there is an option to download an offline installer https://www.google.co.uk/chrome/?platform=win64&standalone=1 However, this option is not available for the Canary build. We updated our Chrome to the latest stable (not canary) and the issue is still present. We can provide another screencast if needed. So the question remains: if we are requested to install the canary build, how can we do it offline?
,
Oct 25
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
,
Oct 25
Please see comments C#3 and C#6. We're providing screenshot hereby.
,
Nov 2
updating the component..!
,
Nov 13
As per comment#2 the issue is not getting reproduced on TE end and as per comment#6 the reporter could not check the issue on latest stable and latest canary. To push the issue out of TE triaging bucket, adding TE-NeedsTriageHelp label and requesting the respective team to look into the issue. Thanks.!
,
Nov 13
This issue is resolved. We found that the culprit is an unwanted software (virus) that modifies Chrome binaries and injects malware assemblies into chrome.dll. We also found that folders randomly open and close while Chrome is open, so we suspected the issue is a virus. Reinstalling Windows solved the problem.
,
Nov 13
Closing per comment #11. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by phanindra.mandapaka@chromium.org
, Oct 18