You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Windows 7 computer with two accounts, both of which have admin status. The main account (David) had previously run Brackets Live Preview without problem. However, after using the second account (V2B), Live Preview no longer works on the main account.
I suspect the problem is due to the way that Chrome installs the main program file in the user's AppData/Local folder rather than in the main Program Files (x86) folder. Here are a couple of error messages found in C:\Users\V2B\AppData\Local\Google\Chrome\Application\debug.log after trying to use Live Preview in the David account:
[0926/230000:ERROR:client_util.cc(394)] Failed to load Chrome DLL from C:\Users\V2B\AppData\Local\Google\Chrome\Application\22.0.1229.79\chrome.dll
[0926/230000:ERROR:client_util.cc(442)] Could not find exported function RelaunchChromeBrowserWithNewCommandLineIfNeeded
The reason chrome.dll can't be found is because C:\Users\V2B\AppData\Local\Google\Chrome\Application\22.0.1229.79 doesn't exist. The V2B account's version of chrome.dll is in C:\Users\V2B\AppData\Local\Google\Chrome\Application\21.0.1180.89. However, the David account's version of chrome.dll is in C:\Users\David\AppData\Local\Google\Chrome\Application\22.0.1229.79.
It appears that Chrome has updated itself in the David account since being used in the V2B account. After submitting this report, I'll switch to the V2B account to update Chrome to see if it fixes the problem.
There needs to be some way of telling Brackets to use the version of Chrome in the current user account.
The text was updated successfully, but these errors were encountered:
Comment by foundationphp Wednesday Sep 26, 2012 at 22:46 GMT
I've updated the version of Chrome on the V2B account, and can confirm that Live Preview is now working in both accounts. So, there's clearly a workaround, but it's going to be a pain to need to keep the version of Chrome on both accounts in sync.
Hi--it's hard for us to reproduce this, but from the description it sounds like a bug in Chrome--we run chrome.exe, and it's up to Chrome to find the right DLL (those log errors appear to be from Chrome, not Brackets). This FAQ on the Chrome support site suggests that it's best to use a different installer to install Chrome for all users on a machine if you want to use it in a multi-account environment:
Wednesday Sep 26, 2012 at 22:20 GMT
Originally opened as adobe/brackets#1720
I have a Windows 7 computer with two accounts, both of which have admin status. The main account (David) had previously run Brackets Live Preview without problem. However, after using the second account (V2B), Live Preview no longer works on the main account.
I suspect the problem is due to the way that Chrome installs the main program file in the user's AppData/Local folder rather than in the main Program Files (x86) folder. Here are a couple of error messages found in C:\Users\V2B\AppData\Local\Google\Chrome\Application\debug.log after trying to use Live Preview in the David account:
[0926/230000:ERROR:client_util.cc(394)] Failed to load Chrome DLL from C:\Users\V2B\AppData\Local\Google\Chrome\Application\22.0.1229.79\chrome.dll
[0926/230000:ERROR:client_util.cc(442)] Could not find exported function RelaunchChromeBrowserWithNewCommandLineIfNeeded
The reason chrome.dll can't be found is because C:\Users\V2B\AppData\Local\Google\Chrome\Application\22.0.1229.79 doesn't exist. The V2B account's version of chrome.dll is in C:\Users\V2B\AppData\Local\Google\Chrome\Application\21.0.1180.89. However, the David account's version of chrome.dll is in C:\Users\David\AppData\Local\Google\Chrome\Application\22.0.1229.79.
It appears that Chrome has updated itself in the David account since being used in the V2B account. After submitting this report, I'll switch to the V2B account to update Chrome to see if it fixes the problem.
There needs to be some way of telling Brackets to use the version of Chrome in the current user account.
The text was updated successfully, but these errors were encountered: