New Chrome (since last two releases) is not closing multiple files when I exit last instance of the browser. That is fatal as those files remain locked and can not be accessed by number of file system synchonization tools.
Workaround: Log out and log in from win 7.
Files noticed to be locked:
GoogleChromePortable\Data\profile\Default\Archived History
GoogleChromePortable\Data\profile\Default\Archived History-journal
GoogleChromePortable\Data\profile\Default\Current Session
GoogleChromePortable\Data\profile\Default\File System\Origins\000433.log
GoogleChromePortable\Data\profile\Default\File System\Origins\MANIFEST-000432
GoogleChromePortable\Data\profile\Default\Preferences
Thx,
R.
PS. I am willing to beta test.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
The only way they can remain locked is if Chrome hasn't closed yet. It takes a while to close on a slower drive. You can watch it in task manager.
Sometimes, the impossible can become possible, if you're awesome!
Hi John,
You are absolutely correct. The point is that chrome is never closing ... it's 14 processes are running in spite that I have terminated the last instance.
There is no chrome in applications tab, but there is zoo of it in processes tab.
And this just happened two release ago. Moreover this is identical on three different PCs I have .. some of them with SSD and pile of RAM.
Thx,
R.
Ok based on the hint I dig more and found that this is google chrome setting to continue to run when any application requires it settings/advanced
Check removed / chrome terminates / case solved !
Many thx,
R.
I know this thread is old, but I am just putting this out there for anyone who googles in vain like me. I had the same problem with the process for ChromiumPortable not ending when the application GUI was closed.
Other threads suggested starting the app with --disable-plugins or --disable-background-mode neither of which worked for me.
Starting the app with the switch --incognito did work for me. Now the process closes immediately when the GUI is closed.
BATCH FILE RUNNING APP FROM NETWORK DRIVE:
CD /d H:\ChromiumPortable
SET "iniLine1=DisableSplashScreen=true"
SET "iniLine2=AdditionalParameters=--incongnito --user-data-dir=$(mktemp -d) --allow-file-access-from-files --app=%appPath%