Re: Running 'chromium' locks up machine

[David Brownlee <abs%absd.org@localhost>]

On Mon, 10 Mar 2025 at 13:54, John D. Baker <jdbaker%consolidated.net@localhost> wrote:
>
> I finally got "www/chromium" built but upon running it for the first
> time, its window didn't quite finish rendering and the system gradually
> froze until only the (PS/2) mouse pointer could move but not affect any
> visual elements.
>
> The (also PS/2) keyboard was unresponsive so the only way to regain
> control was a hard reset.
>
> I suspect the issue is 'dbus'.  I seem to recall seeing some message
> about that in the terminal window from which I ran 'chromium', but
> couldn't read it entirely before 'chromium's window obscured the terminal.
>
> ISTR that dbus-using applications usually try to launch it if they find
> that it isn't currently running.  Do I need to ensure it's running before
> starting 'chromium'?
>
> Anyone else have problems running 'chromium'?
>
> In case it matters, as mentioned in PR pkg/59164, I built my 'chromium'
> after re-enabling "dbus" for _only_ "devel/at-spi2-core" and re-enabling
> "gtk3-atk-bridge" for "x11/gtk3".  Was this sufficient, or should "dbus"
> be re-enabled on other dependencies of "www/chromium"?

I run chromium occasionally (most of my work is in Firefox), for
example when I need to configure an awful Arris NVG578LX router (which
has a UI which uses chrome specific dom objects in what appears to be
a botched CSRF implementation, but I digress :)

This is on various amd64 netbsd-10 stable builds, locally built
packages but nothing special.

Some thoughts on testing
- Can you ssh in from another system and leave top running while
starting chromium?
- Similar to above but "ssh -Y" and run chromium back to the remote
systems X display

David