[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.