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

Issue 786778 link

Starred by 54 users

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression


Show other hotlists

Hotlists containing this issue:
Hotlist-2


Sign in to add a comment

Canary Chrome v.64 doesn't launch

Reported by atgard...@gmail.com, Nov 19 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3269.3 Safari/537.36

Steps to reproduce the problem:
Update Chrome Canary to latest version (64.0.3273.0)

What is the expected behavior?
Chrome runs as usual

What went wrong?
Chrome doesn't launch at all. Looking at the debug.log file in its Application folder, I have the following line:

[1119/102024.841:ERROR:main_dll_loader_win.cc(134)] Failed to load Chrome DLL from C:\Users\XXX\AppData\Local\Google\Chrome SxS\Application\64.0.3273.0\chrome.dll: The specified module could not be found. (0x7E)

Crashed report ID: 

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? Yes The previous Canary version worked well.

Chrome version: 64.0.3273.0  Channel: canary
OS Version: 10.0
Flash Version: 

I also removed Canary from my computer, and installed from scratch. The same result.
 

Comment 1 by canb...@gmail.com, Nov 19 2017

same issue for me windows 10 x64 latest canary 

Comment 2 by qwer1...@gmail.com, Nov 19 2017

same issue for me windows 10 x64 latest canary 

Comment 3 by yurif...@gmail.com, Nov 19 2017

Starting from crrev.com/517684 Chrome needs openvr_api.dll in its Application folder. As a workaround you can get one from github.com/ValveSoftware/openvr/tree/master/bin.

cf.  Issue 786708 .

Comment 4 by atgard...@gmail.com, Nov 19 2017

Thanks. The openvr_api.dll workaround seems to work.
Labels: Hotlist-ConOps M-64
After canary crashed for me, I couldn't get it to open either. 
The same in Windows 7 x64: openvr_api.dll is missing.
Cc: ddorwin@chromium.org
Labels: -Pri-2 Pri-1
Owner: billorr@chromium.org
Status: Assigned (was: Unconfirmed)
Bill, I can also confirm this is due to the new dependency on openvr_api.dll, please take a look / revert as soon as possible as indeed canary doesn't run as distributed due to this issue.

Comment 8 by bvkan...@gmail.com, Nov 19 2017

 I just installed the openvr_api.dll from github into the chrome directory. So far it works. Thanks for linking to github. 

Comment 9 Deleted

Comment 10 Deleted

Just built 9fb91d7 on Win10 and confirmed.

Can also confirm setting the build arg "enable_openvr = false" as a workaround for those building locally.
I've got a speculative revert in the cq https://chromium-review.googlesource.com/c/chromium/src/+/777858

Comment 13 Deleted

Comment 14 by deff...@gmail.com, Nov 19 2017

Same error here. Windows 10 x64.
Reinstallation is not helping this time.

Fix with openvr_api.dll works for me.

Comment 15 Deleted

Comment 16 Deleted

I was able to fix the issue by doing this:

Go here:
https://github.com/ValveSoftware/openvr/tree/master/bin

And go to your operating system and download the openvr_api.dll file.
Put it into the Application/version folder folder.

In Windows can this be found here: 
%localappdata%\Google\Chrome SxS\Application\

Open the folder with your version number (in my/this case, 64.0.3273.0)
And then put the file here.

And then re-launch Chrome and it should start. :) 

Comment 18 Deleted

Comment 19 Deleted

Experiencing same issue described above; installed the x64 openvr_api.dll but now getting error 0xc000012f. 

Debug log excerpts: 

[1119/110027.655:ERROR:main_dll_loader_win.cc(134)] Failed to load Chrome DLL from %LocalAppData%\Google\Chrome SxS\Application\64.0.3273.0\chrome.dll: The specified module could not be found. (0x7E)

[1119/112750.153:ERROR:main_dll_loader_win.cc(134)] Failed to load Chrome DLL from %LocalAppData%\Google\Chrome SxS\Application\64.0.3273.0\chrome.dll: %1 is not a valid Win32 application. (0xC1)

Can't get Canary to work....


Comment 21 by yurif...@gmail.com, Nov 19 2017

Thanks vollick@, the revert landed in crrev.com/517733 (which fixes Chromium).
Win 7 x64 here.  After placing the openvr_api.dll in the appropriate directory the following error appears at Canary launch:

C:\Users\Administrator\AppData\Local\Google
Chrome SxS\Application\64.0.3273.0\openvr_api.dll is either not designed to run on Windows orit contains an error.  Try installing the program again using the original installation media or contact your system administrator for the software vendor for support.

Comment 23 by jra...@gmail.com, Nov 19 2017

i am getting same above error after putting  openvr_api.dll in the chrome directory to fix the first error :(
For me, placing openvr_api.dll from https://github.com/ValveSoftware/openvr/tree/master/bin/win64 in c:\Users\[username]\AppData\Local\Google\Chrome SxS\Application\ fixes the issue on Windows 7 x64

Comment 25 by daiv...@gmail.com, Nov 19 2017

Win x64: placing openvr_api.dl x64 version in app directory fixed the issue. No errors found in debug.log after that

Comment 26 by bat...@gmail.com, Nov 19 2017

Fixed after copy openvr_api.dll from github to chrome dir. That is interesting, if it needs openvr_api.dll, why it doesn't installed it?
Win 10 x64: the workaround is not working, same message as above:

C:\Users\Administrator\AppData\Local\Google
Chrome SxS\Application\openvr_api.dll is either not designed to run on Windows orit contains an error.  Try installing the program again using the original installation media or contact your system administrator for the software vendor for support. Error status 0x000012f.

Putting the dll into 64.0.3273.0 subdirectory gives the same error (of course the poath is modified in the error message.)

Debug log:
[1119/210848.489:ERROR:main_dll_loader_win.cc(134)] Failed to load Chrome DLL from C:\Users\chuck\AppData\Local\Google\Chrome SxS\Application\64.0.3273.0\chrome.dll: %1 is not a valid Win32 application. (0xC1) 


Comment 28 by psyvi...@gmail.com, Nov 19 2017

[1119/235554.128:ERROR:main_dll_loader_win.cc(134)] Failed to load Chrome DLL from C:\Users\%USERNAME%\AppData\Local\Google\Chrome SxS\Application\64.0.3273.0\chrome.dll: The specified module could not be found. (0x7E)

in debug log. Fixed it by adding openvr_api.dll & openvr_api.pdb in 
\Chrome SxS\Application\
folder. Now all works fine!

Win10x64v17040
Workarround obviously worked,
hope a new canary version with https://chromium-review.googlesource.com/c/chromium/src/+/777858 is build / distributed in time.. As all users updating to 64.0.3273.0 have to manually apply the workarround or manually install the newer version :( essentially they are locked out of the upgrade path.
The workaround from https://github.com/ValveSoftware/openvr/tree/master/bin works. And noone knows how those external files could possibly harm. *paranoid mode on*
However, there will be a massive panic on our product forums.

Comment 31 Deleted

makes total sense.. making a webbrowser depending on a virtual reality  library from a third party
adding openvr_api.dll also works for me. Thanks world

Comment 34 Deleted

Thanks. The workaround dll from https://github.com/ValveSoftware/openvr/tree/master/bin works.
Cc: abdulsyed@chromium.org anan...@chromium.org ajha@chromium.org ligim...@chromium.org
Labels: ReleaseBlock-Dev
Cc: nyerramilli@chromium.org

Comment 38 by jra...@gmail.com, Nov 20 2017

the work around doesn't work for me canary still crashes at launch 
placing openvr_api.dll from https://github.com/ValveSoftware/openvr/tree/master/bin/win64 in c:\Users\[username]\AppData\Local\Google\Chrome SxS\Application\ fixes the issue on Windows 7 x64.

Bisect info:
CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.
  https://chromium.googlesource.com/chromium/src/+log/262a9e7bd31156e7611108447254c2e52e92956f..14d631ca392fa139a6f6b89d052d089b99758e33

suspect CL: https://chromium.googlesource.com/chromium/src/+/14d631ca392fa139a6f6b89d052d089b99758e33

Good Build:64.0.3272.0 (Revision: 517671)
Bad Build: 64.0.3273.0 (Revision: 517724)

 Issue 786841  has been merged into this issue.
Cc: msrchandra@chromium.org billorr@chromium.org ranjitkan@chromium.org rbasuvula@chromium.org
 Issue 786860  has been merged into this issue.
 Issue 786847  has been merged into this issue.
 Issue 786832  has been merged into this issue.
 Issue 786798  has been merged into this issue.
 Issue 786797  has been merged into this issue.
Cc: vollick@chromium.org markdavidscott@google.com mmoss@chromium.org
Can some one pls merge the fix/rever to branch 3273 so we can trigger new canary from same branch?

Comment 48 by dhw@chromium.org, Nov 20 2017

Summary: Canary Chrome v.64 doesn't launch (was: Chrome doesn't launch)

Comment 49 by mmoss@chromium.org, Nov 20 2017

I can do it (assuming it merges cleanly).
ok, thank you mmoss@.
mmoss@ merged the change to 3273 branch - https://chromium-review.googlesource.com/c/chromium/src/+/778442. I'm triggering new canary from branch 3273 for windows.

Comment 52 Deleted

Comment 53 by qwer1...@gmail.com, Nov 20 2017

I'm amazed every time such a fiasco happens - how is a build that won't even start released to downloads? 
Something's very wrong in the release process.
 Issue 786708  has been merged into this issue.
 Issue 786875  has been merged into this issue.

Comment 56 by yurif...@gmail.com, Nov 20 2017

Definitely this could have been detected earlier when only Chromium builds were the first affected.
storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win_x64/517684/
64.0.3273.3 fixed the issue. able to launch Canary 64.0.3273.3 on Win 
Cc: sc00335...@techmahindra.com
 Issue 786816  has been merged into this issue.
 Issue 786792  has been merged into this issue.

Comment 60 by nvil...@gmail.com, Nov 20 2017

64.0.3273.2 Win 8.1

---------------------------
chrome.exe - System Error
---------------------------
The program can't start because openvr_api.dll is missing from your computer. Try reinstalling the program to fix this problem. 
---------------------------
OK   
---------------------------
Status: Fixed (was: Assigned)
Resolving this as fixed.  New Canary builds don't have the issue.

Comment 62 by ykle...@gmail.com, Nov 21 2017

Had to install Canary from: https://www.google.com/intl/en/chrome/browser/canary.html

Can confirm the below version fixed this issue:
Version 64.0.3273.3 (Official Build) canary (64-bit)

Thanks!
Version 64.0.3273.3 fixed the problem in Win 10 x64.
Google postmortem: go/chromepostmortem552
How can I see the postmortem?
Thx
I'll summarize here. 
 
openvr_api.dll is a small bit of code that can check whether OpenVR is installed on the machine, and load it to interact with VR headsets.  It is open-source, and can be found in Valve's github repo mentioned above. 

I checked in a change to allow OpenVR support for WebVR.  This included adding a dependency on openvr_api.dll, which was being built inside Chromium code as a mirror of the open-source code from Valve.  I missed adding this new dll to the installer.  Tests picked up the built openvr_api.dll so they all passed fine.  There is an installer test for Canary, and it tested that Canary was successfully installed.  However, the installed Canary was not launched because part of the test has been disabled due to flakiness. Canary is part of the test pipeline, effectively nightly builds that can experience bugs like this (even though we try to find them beforehand), and it served its purpose to prevent this from getting out to dev/beta/release channels. 
 
For the immediate issue, my change was rolled back, removing the dependency.  It was re-landed without adding a new dll.  crbug/461856 represents the work to re-enable the test to launch Canary after installing.

Sign in to add a comment