You are here

[Fixed] Chrome Portable Dev 38.0.2107.2 sometimes leaves files in %LOCALAPPDATA%

7 posts / 0 new
Last post
marcelo-ar
Offline
Last seen: 6 years 3 months ago
Joined: 2013-11-29 11:32
[Fixed] Chrome Portable Dev 38.0.2107.2 sometimes leaves files in %LOCALAPPDATA%

Google Chrome Portable Dev 38.0.2107.2 sometimes leaves files behind in...

%LOCALAPPDATA%\Google\Chrome\User Data\SwiftShader\3.2.6.45159

----------------------------------
Files added: 4
----------------------------------
...SwiftShader\3.2.6.45159\libEGL.dll
...SwiftShader\3.2.6.45159\libGLESv2.dll
...SwiftShader\3.2.6.45159\manifest.fingerprint
...SwiftShader\3.2.6.45159\manifest.json

Files belongs to SwiftShader component from Google Chrome.
Google Chrome Portable Stable (36.0.1985.125) stores SwiftShader files in profile, but probably due to a bug in latest Dev versions, Chrome is ignoring profile location command line "--user-data-dir" passed by the launcher and places some component files in %LOCALAPPDATA%.

I've tested Chrome Dev with two computers, the newer one has hardware acceleration support and the older doesn't.
Files are left behind only in the older PC.

In newer hardware we can trigger the bug following this steps:

1) Launch Google Chrome Portable Dev
2) Go to Settings, advanced settings, and disable "Use hardware acceleration when available", and restart Chrome
3) Type chrome://components/ in url bar (Swift Shader should now be listed)
4) If Swift Shader is version 0.0.0.0 click on "Check for update" button to force installation (normally it installs automatically)
5) Exit Google Chrome

Results:
Swift Shader files remains in host PC under %LOCALAPPDATA%

Swift Shader component seems to be necessary in old hardware to support WebGL.
Test site: http://get.webgl.org/

This bug only affects portable version, so I think is useless to report it to chrome developers.
I've tried to launch chrome with command line "--swiftshader-path=[profile-location]\SwiftShader" with no success.
The only workaround I've found is to launch Chrome Portable with command line "--disable-component-update", to avoid file creation.

John T. Haller
John T. Haller's picture
Online
Last seen: 9 min 59 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Noted

I've noted this for the next Dev release. You'll get this on Dev as Google Chrome shoots increasingly more offshoots into random areas of the system's registry and file system. We use dev to figure these out so we get them fixed for beta and stable.

Sometimes, the impossible can become possible, if you're awesome!

John T. Haller
John T. Haller's picture
Online
Last seen: 9 min 59 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Fixed in Dev 38.0.2114.2

This is fixed with today's release of Google Chrome Portable 38.0.2114.2 Dev.

Sometimes, the impossible can become possible, if you're awesome!

marcelo-ar
Offline
Last seen: 6 years 3 months ago
Joined: 2013-11-29 11:32
Bug reported to Chrome Developers

Thanks for the fix.

I found a way to reproduce this bug with non-portable Google Chrome Dev/Canary and decided to report it to Chome developers:

Issue 399993: SwiftShader component is installed in %LOCALAPPDATA% instead of specified user-data-dir
https://code.google.com/p/chromium/issues/detail?id=399993

The bug was confirmed and now they're working on a fix.
Bug affects all this components: CLD2, Recovery, SwiftShader, SwReporter.
Perhaps this will be fixed before v 38 enters in beta or stable Channel, and you can go back to previous launcher.

tommycli
Offline
Last seen: 8 years 3 months ago
Joined: 2014-08-12 17:43
Hello, I'm the Chromium dev

Hello, I'm the Chromium dev who broke this.

The fix is in trunk now, and should be fixed for v 38. Thanks for the report.

John T. Haller
John T. Haller's picture
Online
Last seen: 9 min 59 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Thanks

Thanks for the heads up.

Sometimes, the impossible can become possible, if you're awesome!

marcelo-ar
Offline
Last seen: 6 years 3 months ago
Joined: 2013-11-29 11:32
Thanks for the fix

Tommy, thanks for your quick fix.

Log in or register to post comments