Page 1 of 1

Chromium+arguments=crash (EasyOS 5.4.6)

Posted: Fri Jul 12, 2024 5:29 am
by franah486

Hello Dear Community, I'm passing args to Cr with a strange behavior the browser opens up and then its closes until the fourth attempt. my question is there is a way to pass arguments more effectively?

example.gif
example.gif (241.18 KiB) Viewed 571 times

Re: Chromium+arguments=crash

Posted: Fri Jul 12, 2024 7:16 am
by bigpup

What specific Puppy version you using?
Give the complete full name of it.
Name of the ISO is best info.

How did you install Chromium?

What version of Chromium?


Re: Chromium+arguments=crash

Posted: Fri Jul 12, 2024 9:04 pm
by franah486

Hello @bigpup :thumbup: I'm running EasyOS 5.4.6 from this easy-5.4.6-amd64.img the browser came pre-installed or built-in the version is 112.0.5615.165 another thing I have done was just pass one single command and still the browser won't launch straight away.


Re: Chromium+arguments=crash

Posted: Sat Jul 13, 2024 2:16 am
by williams2

1) you probably should ask EasyOS questions on the EasyOS section of the forum. viewforum.php?f=63

2) EasyOS can run things in containers, as user chromium for example, which can cause problems. And rox may be running in a slightly different environment to the shell.

Does everything run properly with no switches?

Rox is executing the shell script /usr/local/bin/defaultbrowser when you click the www icon.
You can edit the script and add the configuration switches to the script.
Then run the script in a terminal. to see what error messages you get.

Code: Select all

defaultbrowser

You can also type them in the terminal, like

Code: Select all

defaultbrowser --block-new-web-contents

Maybe there is one switch causing trouble?

Do you really want --single-process ?
It says it may cause instability.


Re: Chromium+arguments=crash (EasyOS 5.4.6)

Posted: Sun Jul 14, 2024 10:17 pm
by franah486

It seems that none of the method you've suggested works...

Here's when I run from the terminal since first boot

Code: Select all

# defaultbrowser --enable-low-end-device-mode --single-process
localuser:chromium being added to access control list
[4940:4940:0714/185431.278039:ERROR:gaia_urls.cc(125)] Ignoring invalid origin "0.0.0.0" for switch "gaia-url"
[4940:4940:0714/185431.278320:ERROR:gaia_urls.cc(111)] Ignoring invalid URL "0.0.0.0" for switch "lso-url"
[4940:4940:0714/185431.278402:ERROR:gaia_urls.cc(111)] Ignoring invalid URL "0.0.0.0" for switch "google-apis-url"
[4940:4940:0714/185431.278481:ERROR:gaia_urls.cc(111)] Ignoring invalid URL "0.0.0.0" for switch "oauth-account-manager-url"
[4940:4978:0714/185432.304538:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.StartServiceByName: object_path= /org/freedesktop/DBus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[4940:4940:0714/185433.767877:ERROR:system_network_context_manager.cc(765)] Cannot use V8 Proxy resolver in single process mode.
[4940:4940:0714/185434.241464:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management controller initialization aborted as CBCM is not enabled.
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[4940:4940:0714/185439.226132:ERROR:system_network_context_manager.cc(765)] Cannot use V8 Proxy resolver in single process mode.
[4940:4940:0714/185439.690603:ERROR:system_network_context_manager.cc(765)] Cannot use V8 Proxy resolver in single process mode.
[4940:4940:0714/185439.857996:ERROR:system_network_context_manager.cc(765)] Cannot use V8 Proxy resolver in single process mode.
[4940:4940:0714/185439.864985:ERROR:gpu_memory_buffer_support_x11.cc(49)] dri3 extension not supported.
/usr/bin/chromium.bin: line 3:  4940 Segmentation fault      /usr/bin/chromium.bin0 $@
# 

Eventually the browsers crashes with this error at the last line.

Note: I'd to clarify that this sequence of run and crash only occur right at the first boot. If i close Chromium and open it again it runs OK with all arguments.

I get this /usr/local/bin/defaultbrowser and passes all arguments with Geany this time I've removed --guest flag and tried to run from terminal. A Chromium windows then appears and ask if I wanna be Guest or Person 1 no matter what you choose the browser closes up.

Code: Select all

d# defaultbrowser 
[16119:16119:0714/195008.408942:ERROR:gaia_urls.cc(125)] Ignoring invalid origin "0.0.0.0" for switch "gaia-url"
[16119:16119:0714/195008.409190:ERROR:gaia_urls.cc(111)] Ignoring invalid URL "0.0.0.0" for switch "lso-url"
[16119:16119:0714/195008.409266:ERROR:gaia_urls.cc(111)] Ignoring invalid URL "0.0.0.0" for switch "google-apis-url"
[16119:16119:0714/195008.409349:ERROR:gaia_urls.cc(111)] Ignoring invalid URL "0.0.0.0" for switch "oauth-account-manager-url"
[16119:16119:0714/195008.503330:ERROR:system_network_context_manager.cc(765)] Cannot use V8 Proxy resolver in single process mode.
[16119:16119:0714/195008.513780:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management controller initialization aborted as CBCM is not enabled.
[16119:16119:0714/195008.567847:ERROR:system_network_context_manager.cc(765)] Cannot use V8 Proxy resolver in single process mode.
[16119:16119:0714/195008.823734:ERROR:system_network_context_manager.cc(765)] Cannot use V8 Proxy resolver in single process mode.
[16119:16119:0714/195009.001757:ERROR:system_network_context_manager.cc(765)] Cannot use V8 Proxy resolver in single process mode.
Warning: disabling flag --expose_wasm due to conflicting flags
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[16119:16152:0714/195009.300259:ERROR:gpu_memory_buffer_support_x11.cc(49)] dri3 extension not supported.
[16119:16219:0714/195009.336761:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[16119:16141:0714/195009.435365:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.StartServiceByName: object_path= /org/freedesktop/DBus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[16119:16206:0714/195009.558631:ERROR:font_unique_name_lookup_linux.cc(21)] @font-face src: local() instantiation only available when connected to browser process.
[16119:16206:0714/195009.559601:ERROR:font_unique_name_lookup_linux.cc(21)] @font-face src: local() instantiation only available when connected to browser process.
[16119:16206:0714/195010.090292:ERROR:font_unique_name_lookup_linux.cc(21)] @font-face src: local() instantiation only available when connected to browser process.
[16119:16206:0714/195010.090392:ERROR:font_unique_name_lookup_linux.cc(21)] @font-face src: local() instantiation only available when connected to browser process.
[16119:16119:0714/195012.219274:ERROR:system_network_context_manager.cc(765)] Cannot use V8 Proxy resolver in single process mode.
/usr/bin/chromium.bin: line 3: 16119 Trace/breakpoint trap   /usr/bin/chromium.bin0 $@
#

Re: Chromium+arguments=crash (EasyOS 5.4.6)

Posted: Sun Jul 14, 2024 10:30 pm
by Wiz57

What, if any, extensions, add-ons and plug-ins have you installed? Can't be sure, but to me it appears that some
add-on is misbehaving and throwing errors, which eventually lead to chromium crashing. So, try running first
without any add-ons, then add them back one at a time, launch, and check for error messages.


Re: Chromium+arguments=crash (EasyOS 5.4.6)

Posted: Mon Jul 15, 2024 1:29 am
by franah486

Hi @Wiz57 :thumbup:

Wiz57 wrote: Sun Jul 14, 2024 10:30 pm

What, if any, extensions, add-ons and plug-ins have you installed? Can't be sure, but to me it appears that some
add-on is misbehaving and throwing errors, which eventually lead to chromium crashing. So, try running first
without any add-ons, then add them back one at a time, launch, and check for error messages.

All is default settings none extension added... I'm just discovered that some arguments do not play well each other so it was that's the browser closed up. I've identified the issue so you now can close the topic or mark it as solved.

Btw if you're curious about what these arguments are there's a repo from user melo936 at Github named Chromium Hardening.

Cheers!