I've had Chrome crash a dew times lately. The chrome_debug.log had no information relating to the crash.
I ran across this help article, https://support.google.com/chrome/a/answer/6271282?sjid=1570637331475214..., "Chrome browser debug logs", with instructions to "Turn on logging" by adding a command line
https://i.postimg.cc/13JTPZ19/CHROME-LOGGING2.png
Afterwards, when I open Chrome, a command prompt also opens, with what looks like some erroneous information, regarding a defunct download manager, Eagleget, I used to use, and that something does not exist or isn't readable
https://i.postimg.cc/9XwYQHZW/CHROME-LOGGING.png
The instruction reads "Note: Instructions assume that Chrome browser is installed in the default location." Is there anything I can do about this?
The command window is there when you run in debug mode whether local or portable. This is by design of the publisher. That information is correct, you have some entries for Eagleget somewhere in the registry or local files that Chrome Portable is reading as it was never fully uninstalled. To fix this, remove all the old Eagleget bits in your registry, APPDATA, etc.
Note that to use this command line option with Google Chrome Portable you can either launch GoogleChromePortable.exe with the options added or copy the GoogleChromePortable.ini file from the GoogleChromePortable\Other\Source directory to the GoogleChromePortable directory and then edit the AdditionalParameters line to read:
AdditionalParameters=--enable-logging --v=1
Sometimes, the impossible can become possible, if you're awesome!
I altered the file;
[GoogleChromePortable]
Google ChromeDirectory=App\Chrome-bin
; The main app directory
ProfileDirectory=Data\profile
The profile directory
SettingsDirectory=Data\settings
; The directory containing settings. Currently only used for the master
; password hash, if enabled.
AdditionalParameters=--enable-logging --v=1
I put it here "N:\PortableApps.com Platform\PortableApps\GoogleChromePortable64\GoogleChromePortable.ini"
and got this
https://i.postimg.cc/4xNbXFRs/CHROME-LOGGING3.png
Did I put it I the wrong place?
Microsoft Windows 10 Professional (x64) Build 19045.4894 (22H2)
You will always receive different messages in the command line window. I receive a few errors about USB inaccessibility. Unless you are specifically looking for that, ignore it. If you want help with specific error messages, you'll need to ask the developers of Chrome/Chromium.
Sometimes, the impossible can become possible, if you're awesome!
Thank you.
Microsoft Windows 10 Professional (x64) Build 19045.4894 (22H2)