chromium - crippled graphics / [no|bad] sound / pulseaudio / hangs / flame

Something to keep in mind when testing chromium on i386.

Set off in chromium/Makefile the following flag:
Code:
GN_ARGS+=use_lld=false

There is an issue with LLD. Note that this linker can link chromium approximately twice as fast as gold.
 
I am waiting for official package build servers. On my server, I am using
Code:
url: "pkg+http://pkg.eu.FreeBSD.org/${ABI}/quarterly"
and chrome 54 is available in this quarterly repo, but on my laptop I have latest packages
Code:
url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest"
, and there is still chrome 52 only. So "quarterly" is more actual than "latest" :/
 
I am waiting for official package build servers. On my server, I am using
Code:
url: "pkg+http://pkg.eu.FreeBSD.org/${ABI}/quarterly"
and chrome 54 is available in this quarterly repo, but on my laptop I have latest packages
Code:
url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest"
, and there is still chrome 52 only. So "quarterly" is more actual than "latest" :/

I can't comment on those test servers but I have chrome 54 working. I cloned the git repo and then did a make install from within that www/chromium folder. If you want sound just run make config and enable alsa then build and install.

It works but sometimes some of my chrome apps crashes but that's no big deal. Surfing, audio, everything else works as expected.

I'd like to get this chrome into the official packages but for now this is good enough.
 
Finally (official package)! Graphics is working, but no sound.

If ALSA is needed for sound, why is not ALSA enabled by default in port, for all FreeBSD users?

Can I debug/test something (about sound)?
 
Finally (official package)! Graphics is working, but no sound.

If ALSA is needed for sound, why is not ALSA enabled by default in port, for all FreeBSD users?

Can I debug/test something (about sound)?

It's pending to be committed:

https://github.com/gliaskos/freebsd-chromium/commit/5cf6634e3d2dbfc4aea4c5805decc9508d14054f

If you are able to build your own packages via poudriere(8)

You can set the build options for your ports. Edit /usr/local/etc/poudriere.d/make.conf
Code:
# custom options
www_chromium_SET= ALSA PULSEAUDIO
 
It seems that everyone (experts) on the FreeBSD are compiling software on their own build clusters :)
I am just using default binary packages (pkg) and sane defaults is good for everyone (think about newcomers).
Thanks again for your work about this chrome issues.
 
Actual version of "chromium-55.0.2883.87" has the dependency to the PulseAudio AGAIN. Is there any sane reason, why push pulseaudio to all users by default?
What is bad with default sound via OSS? I am just curious, what is the reason? Thanks!
 
I am having some issues with chromium as well. I am using Chromium 55.0.2883.87 (64-bit). What happens is that sometimes websites will just not load at all, whether they are videos on YouTube or news sites. The sites will hang and I will need to copy the URL and open it up in a new tab and close the original tab. This happens a lot and is starting to get annoying. Firefox does not do this but Firefox seems very sluggish in comparison with chromium. Anyone else having this issue of sites not leading in chromium? Thanks.
 
Yes Grell is right - same behaviour on my side (my tabs often hangs when loading twitter.com etc, after a while, Chrome asks me to kill this tab).

Also, when I open fullscreen video player on youtube (or other site), then when exiting from full screen, top bar with URL and tabs is also crippled and redrawed slowly when i move mouse over it.
 
And sideeffects is here, as I suspected - after I installed pulseaudio (and updated recently to the version 10) - as dependency by Chrome, sound is crippled/choppy completely from chromium, from firefox too, because firefox starts using pulseaudio dynamicaly (maybe pulse is interfering with OSS in some way). When I need to switch sound output, I need to switch it in OSS (for some apps) and also in pulse (for other apps). I also need to read extra long wiki pages (+ Arch linux wiki pages) about PulseProblem 10.0, google like a maniac and hope, that my sound will be OK and properly configured somewhere in the future.
Or, of course, I can recompile chrome port every 14 days with bare OSS/ALSA support only. Or recompile everything other once a month with PulseProblem. Or throw away PulseProblem + Chrome from my drive. It's good, so many options.

I knew it!
 
Hello,

I'm sure you'll be interested in this bugreports:
- Chromium + Pulseaudio : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216327
- Firefox + Pulseaudio : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216383
Yes, Pulseaudio doesn't work correctly and saturate CPU, it's a known fact on FreeBSD and Linux.

Or throw away PulseProblem + Chrome from my drive.
Would love too... But what are the alternative for a modern browser? Firefox isn't a solution because of all its problems, and not just because of Pulseaudio.

Best Regards.
 
drhowarddrfine: it's not related to FreeBSD, but common on all OS (Linux and Windows, I admit I haven't tried it on FreeBSD): Firefox uses too much RAM, CPU and is very slow. It has always been this way since at least Firefox 2.x and it just get worst with every few releases :-(
 
Firefox looks best on my FreeBSD, but is a CPU and RAM hog, problems with videos on second monitor, sometimes choppy or pink tinted videos...
Actual Chromium state: it's fast, but often whole tab hangs, pulseaudio dep annoyances, graphics redrawing problems sometimes (in url bar/tab tops)...

In my personal despair, I even tried suckless "surf" browser - you can add your own hot-keys directly into core C code and recompile :) But as a minimal-browser, it still sucks/segfaults (based on Webkit+old gtk2).
Maybe some other browser, like "otter"? I don't know, everything is Webkit.

I tried compile chromium from port myself (without PulseProblem), but somewhere in the build process, linker exits with error :(
 
Actualization: to be fair, I must say that I fixed PulseAudio config (after 2 days) by:
Code:
default-fragments = 10
default-fragment-size-msec = 25
Maybe the main suckery is in the HW of my laptop, I have no idea what those settings are.

But I still think that the PulseAudio should be optional (if possible, of course).
 
Back
Top