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

Petr Fischer · Aug 22, 2016

Hello, after update chrome from 51 to the 52.0.2743.116, my chrome browser window looks like this:
https://www.dropbox.com/s/osh5esbw45bwpji/Screenshot-2016.08.22-03.19.20.png?dl=0

What's wrong? (I tried to delete the ~/.config/chromium folder with no luck)

Thanks!

drhowarddrfine · Aug 22, 2016

I'm not having that issue but Chromium, right now, is having issues. This happens every so often because Chromium has gotten very sophisticated and very complicated and the port maintainers are struggling to keep up with all the additions and changes that have come about over the last few years.

Right now, I have both Firefox and Chromium open at the same time and switch between the two cause some sites will hang in Chromium. This didn't happen until the last update.

tobik@ · Aug 22, 2016

Hmm odd. Maybe this is a bug in your graphics driver? What GPU and FreeBSD version are you using?

Try running Chromium with chrome --disable-gpu (make sure to close all open Chromium windows first) and see if that helps.

Petr Fischer · Aug 22, 2016

tobik - with --disable-gpu still the same situation. My graphics is "Intel Haswell HDA Controller". FreeBSD 11-RC1

I can see this in terminal after chrome start:

Code:

[3534:411147264:0822/153347:ERROR:linux_util.cc(122)] Not implemented reached in std::string base::GetLinuxDistro()
[3534:411131904:0822/153347:ERROR:battery_status_manager_default.cc(25)] Not implemented reached in virtual bool device::(anonymous namespace)::BatteryStatusManagerDefault::StartListeningBatteryChange()
[3534:411131904:0822/153347:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[3534:411131904:0822/153347:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[3534:411131904:0822/153348:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[3534:411131904:0822/153348:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[3534:411131904:0822/153348:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[3534:411131904:0822/153348:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[3534:411131904:0822/153348:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[3534:411131904:0822/153348:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[3534:411131904:0822/153349:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[3534:411131904:0822/153349:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[3534:411131904:0822/153350:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[3534:411131904:0822/153350:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[3534:411131904:0822/153351:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[3534:411131904:0822/153351:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[3534:411131904:0822/153351:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[3534:411131904:0822/153351:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[3534:411131904:0822/153351:ERROR:battery_status_manager_default.cc(29)] Not implemented reached in virtual void device::(anonymous namespace)::BatteryStatusManagerDefault::StopListeningBatteryChange()

Petr Fischer · Aug 22, 2016

Also - can I report bugs to the port maintainers (ArchLinux has some reporting functionality on ports website)?

drhowarddrfine · Aug 22, 2016

Port maintainer for Chromium is listed in the Makefile: Florent Thoumie <flz@FreeBSD.org>

Also, you can report bugs here: https://bugs.freebsd.org/bugzilla/

Petr Fischer · Aug 22, 2016

Bug created: PR 212060

cpm@ · Aug 23, 2016

Petr Fischer,

Can you provide your chrome://gpu content?

Petr Fischer · Aug 23, 2016

Export of chrome://gpu

https://www.dropbox.com/s/puqk2xxatutjdrs/chrome-gpu.pdf?dl=0

cpm@ · Aug 25, 2016

Does it reproduced with chrome --disable-scaling-in-image-skia-operations?

Petr Fischer · Aug 25, 2016

cpm@ - still the same problem, output:

Code:

05:07:13 pf@pf-bsd:~ $ chrome --disable-scaling-in-image-skia-operations
[34001:411147264:0825/050714:ERROR:linux_util.cc(122)] Not implemented reached in std::string base::GetLinuxDistro()
[34001:411131904:0825/050714:ERROR:battery_status_manager_default.cc(25)] Not implemented reached in virtual bool device::(anonymous namespace)::BatteryStatusManagerDefault::StartListeningBatteryChange()
ATTENTION: option value of option force_s3tc_enable ignored.
ATTENTION: option value of option force_s3tc_enable ignored.
[34001:411131904:0825/050714:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[34001:411131904:0825/050714:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
ATTENTION: option value of option force_s3tc_enable ignored.
ATTENTION: option value of option force_s3tc_enable ignored.
[34001:411131904:0825/050715:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[...repeated...]
[34001:411131904:0825/050717:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
libpng warning: iCCP: known incorrect sRGB profile
[34001:411131904:0825/050718:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[34001:411131904:0825/050718:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[34001:411131904:0825/050718:ERROR:battery_status_manager_default.cc(29)] Not implemented reached in virtual void device::(anonymous namespace)::BatteryStatusManagerDefault::StopListeningBatteryChange()

cpm@ · Aug 25, 2016

Your problem hasn't a quick-easy-feasable solution. In the meantime, you can revert www/chromium to previous version 51.0.2704.106 or use other browser, e.g. www/firefox.

Petr Fischer · Aug 25, 2016

cpm@ - thanks! is there any package cache with old package versions? on the http://pkg.FreeBSD.org/ are only latest packages (my package cache is cleared periodically from cron)

cpm@ · Aug 25, 2016

Petr Fischer said:
cpm@ - thanks! is there any package cache with old package versions? on the http://pkg.FreeBSD.org/ are only latest packages (my package cache is cleared periodically from cron)

Please, see Thread 49934.

bcomputerguy · Sep 12, 2016

I am having a similar issue, filed a bug but it was placed as a duplicate. I just found this thread and wanted to provide some of the info that cpm@ asked for.

Here's the output of my chrome://gpu

Code:

Graphics Feature Status
[LIST]
[*]Canvas: Hardware accelerated
[*]Flash: Hardware accelerated
[*]Flash Stage3D: Hardware accelerated
[*]Flash Stage3D Baseline profile: Hardware accelerated
[*]Compositing: Hardware accelerated
[*]Multiple Raster Threads: Enabled
[*]Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
[*]Rasterization: Software only. Hardware acceleration disabled
[*]Video Decode: Hardware accelerated
[*]Video Encode: Hardware accelerated
[*]WebGL: Hardware accelerated
[/LIST]
Driver Bug Workarounds
[LIST]
[*]clear_uniforms_before_first_program_use
[*]scalarize_vec_and_mat_constructor_args
[/LIST]
Problems Detected
[LIST]
[*]124764,349137
Applied Workarounds: clear_uniforms_before_first_program_use
[*]398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
[*]Accelerated rasterization has been disabled, either via blacklist, about:flags or the command line.
Disabled Features: rasterization
[*]Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers
[/LIST]
Version Information
Data exported 9/12/2016, 9:26:28 PM
Chrome version Chrome/52.0.2743.116
Operating system FreeBSD 11.0-RC2
Software rendering list version 11.7
Driver bug list version 8.78
ANGLE commit id unknown hash
2D graphics backend Skia
Command Line Args --incognito --window-depth=24 --x11-visual-id=33 --wm-user-time-ms=311064 --flag-switches-begin --flag-switches-end
Driver Information
Initialization time 0
In-process GPU true
Sandboxed false
GPU0 VENDOR = 0x0000, DEVICE= 0x0000
Optimus false
AMD switchable false
Driver vendor
Driver version
Driver date
Pixel shader version
Vertex shader version
Max. MSAA samples
Machine model name
Machine model version
GL_VENDOR
GL_RENDERER
GL_VERSION
GL_EXTENSIONS
Disabled Extensions
Window system binding vendor
Window system binding version
Window system binding extensions
Window manager i3
Compositing manager Yes
Direct rendering Yes
Reset notification strategy 0x0000
GPU process crash count 0
Compositor Information
Tile Update Mode One-copy
Partial Raster Enabled
GpuMemoryBuffers Status
ATC Software only
ATCIA Software only
DXT1 Software only
DXT5 Software only
ETC1 Software only
R_8 Software only
BGR_565 Software only
RGBA_4444 Software only
RGBX_8888 Software only
RGBA_8888 Software only
BGRX_8888 Software only
BGRA_8888 Software only
YUV_420 Software only
YUV_420_BIPLANAR Software only
UYVY_422 Software only

this is disable-scaling output

Code:

blubee@bn:~ % chrome --disable-scaling-in-image-skia-operations
[1098:430017792:0912/212854:ERROR:linux_util.cc(122)] Not implementLinuxDistro()
[1098:430006272:0912/212854:ERROR:battery_status_manager_default.cc(25)] Not implemented reached in virtual bool device::(anonymous namespace)::BatteryStatusManagerDefault::StartListeningBatteryChange()
[1098:430006272:0912/212854:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1098:430006272:0912/212854:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1098:430006272:0912/212855:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1098:430006272:0912/212855:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1098:430006272:0912/212855:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1098:430006272:0912/212855:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1098:430006272:0912/212855:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1098:430006272:0912/212855:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1098:430006272:0912/212855:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1098:430006272:0912/212855:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1098:430006272:0912/212858:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1098:430006272:0912/212858:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource

disable-gpu yields the same results

Code:

chrome --disable-gpu
[1187:430017792:0912/212948:ERROR:linux_util.cc(122)] Not implementLinuxDistro()
[1187:430006272:0912/212948:ERROR:battery_status_manager_default.cc(25)] Not implemented reached in virtual bool device::(anonymous namespace)::BatteryStatusManagerDefault::StartListeningBatteryChange()
[1187:430006272:0912/212948:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1187:430006272:0912/212948:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1187:430006272:0912/212948:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1187:430006272:0912/212948:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1187:430006272:0912/212948:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1187:430006272:0912/212948:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1187:430006272:0912/212948:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1187:430006272:0912/212948:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1187:430006272:0912/212948:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1187:430006272:0912/212948:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1187:430006272:0912/212952:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource
[1187:430006272:0912/212952:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource

I think i'll have to downgrade to the last version of chrome as well.

Petr Fischer · Sep 12, 2016

bcomputerguy - downgrade, ok, but where to download old packages? Do you have one in your pkg cache? Can you share please?

bcomputerguy · Sep 13, 2016

Petr Fischer said:
bcomputerguy - downgrade, ok, but where to download old packages? Do you have one in your pkg cache? Can you share please?

Go to

Code:

/usr/ports/ports-mgmt/portdowngrade

and install portdowngrade

Once you do that, head over to

Code:

/usr/ports/www/chromium

and run

Code:

make deinstall clean

That will remove the current version of chromium from your system.

Then go to your home directory cd, I would not run these commands inside the port tree. So go to your home directory

then run

Code:

portdowngrade www/chromium r417611

This will create a chromium folder inside your home folder. Next cd into this newly created chromium folder.

If you try to run make install clean you will run into some security errors and the make will fail so you should run

Code:

make DISABLE_VULNERABILITIES=yes install clean

This will go through and install the latest version 51 of your chromium browser.

Make sure you read the final output lines by the build system and add this

Code:

kern.ipc.shm_allow_removed=1

one line to your /etc/sysctl.conf

Once that's done you should be downgraded to chromium 51.0.2704.106 I forget the exact version.

You can then do pkg lock chromium

it will ask you are you sure, just choose yes. That will prevent updating your other applications from upgrading chromium until the bug is fixed.

Once the bug is fixed you can remove the pkg lock from chromium.

After that you should be good, I am currently running chromim 51 and it's fine since the vulnerabilities that FreeBSD knows and warned us about.

If you have any more questions just post them here.

cpm@ · Oct 28, 2016

Well, I'm finally using chromium-54.0.2840.50 and it's working properly.

Code:

% pkg info chromium
chromium-54.0.2840.50
Name           : chromium
Version        : 54.0.2840.50
Installed on   : Fri Oct 28 00:42:29 2016 CEST
Origin         : www/chromium
Architecture   : freebsd:10:x86:64
Prefix         : /usr/local
Categories     : www
Licenses       : MPL and LGPL21 and BSD3CLAUSE
Maintainer     : chromium@FreeBSD.org
WWW            : http://www.chromium.org/Home
Comment        : Google web browser based on WebKit
Options        :
    CODECS         : on
    DEBUG          : off
    DRIVER         : off
    GCONF          : on
    KERBEROS       : on
    PULSEAUDIO     : off
    TEST           : off
Shared Libs required:
    libgtk-x11-2.0.so.0
    libexpat.so.1
    libXext.so.6
    libxslt.so.1
    libpango-1.0.so.0
    libjpeg.so.8
    libfreetype.so.6
    libFLAC.so.8
    libcairo.so.2
    libxml2.so.2
    libXtst.so.6
    libwebp.so.6
    libatk-1.0.so.0
    libcups.so.2
    libgmodule-2.0.so.0
    libXcomposite.so.1
    libXss.so.1
    libgdk_pixbuf-2.0.so.0
    libgio-2.0.so.0
    libXfixes.so.3
    libwebpdemux.so.2
    libnss3.so
    libnssutil3.so
    libnspr4.so
    libgobject-2.0.so.0
    libgconf-2.so.4
    libharfbuzz.so.0
    libglib-2.0.so.0
    libX11.so.6
    libdbus-1.so.3
    libXdamage.so.1
    libXrender.so.1
    libgdk-x11-2.0.so.0
    libXcursor.so.1
    libXrandr.so.2
    libsnappy.so.1
    libfontconfig.so.1
    libsmime3.so
    libXi.so.6
    libpangocairo-1.0.so.0
Annotations    :
    cpe            : cpe:2.3:a:google:chrome:54.0.2840.50:::::freebsd10:x64
Flat size      : 175MiB
Description    :
Chromium is an open-source browser project that aims to build a safer,
faster, and more stable way for all users to experience the web.

The Chromium website contains design documents, architecture overviews,
testing information, and more to help you learn to build and work with
the Chromium source code.

WWW: http://www.chromium.org/Home

I hope that we get committed chromium update to 54.0.2840.50 pretty soon.

lonestar · Oct 29, 2016

cpm@ said:
I'm finally using chromium-54.0.2840.50

How did you update the version?

cpm@ · Oct 30, 2016

lonestar said:
How did you update the version?

chromium-54.0.2840.71 is out. Here is the GH repository:

https://github.com/paranormal/freebsd-chromium/tree/master/www/chromium

Note that to play audio (YouTube, SoundCloud, etc) it's necessary to build chromium with PULSEAUDIO enabled.

Petr Fischer · Oct 30, 2016

Sound in previous version of chrome works just fine without PULSEAUDIO (youtube etc...), why is PULSEAUDIO required now?

And also - will be new version available in PORTS?

cpm@ · Oct 30, 2016

Petr Fischer said:
Sound in previous version of chrome works just fine without PULSEAUDIO (youtube etc...), why is PULSEAUDIO required now?

We are investigating the issue, but we consider to use PULSEAUDIO as a quick fix that works properly.

And also - will be new version available in PORTS?

Sure, it will be committed ASAP. We prefer to delay the update to be sure that everything works as it should.

Thanks for your patience

marino · Oct 30, 2016

cpm@ said:
We are investigating the issue, but we consider to use PULSEAUDIO as a quick fix that works properly.

Dragonfly has intentionally removed pulseaudio from the dports tree so this "quick fix" is unworkable for us.
I would guess some config script isn't honoring a no-pulseaudio config.

cpm@ · Nov 1, 2016

marino@ said:
Dragonfly has intentionally removed pulseaudio from the dports tree so this "quick fix" is unworkable for us.
I would guess some config script isn't honoring a no-pulseaudio config.

Yes, this problem was fixed, so we have sound via ALSA instead of PULSEAUDIO as previous chromium releases.

Code:

--- Makefile.orig    2016-11-02 00:57:43.858578000 +0100
+++ Makefile    2016-11-01 14:19:45.820422000 +0100
@@ -84,7 +84,7 @@
        enable_remoting=false \
        toolkit_views=true \
        use_allocator="none" \
-        use_alsa=false \
+        use_alsa=true \
        use_aura=true \
        use_experimental_allocator_shim=true \
        treat_warnings_as_errors=false \

bcomputerguy · Nov 3, 2016

Is this latest version of chromium in the ports tree yet?

My above steps don't even work for me anymore.

Code:

portdowngrade www/chromium r417611

then try to build it....

sudo make MAKE_JOBS_UNSAFE=yes DISABLE_VULNERABILITIES=yes install clean

then I get this error
/printing/backend/print_backend_cups.cc -o obj/printing/backend/printing.print_backend_cups.o
../../printing/backend/print_backend_cups.cc:276:21: error: use of undeclared identifier 'cupsGetPPD'
    ppd_file_path = cupsGetPPD(name);
                    ^
../../printing/backend/print_backend_cups.cc:289:21: error: use of undeclared identifier 'cupsGetPPD2'
    ppd_file_path = cupsGetPPD2(http.http(), name);
                    ^
2 errors generated.
ninja: build stopped: subcommand failed.
*** Error code 1

Stop.
make[1]: stopped in /usr/home/xxxxx/chromium
*** Error code 1

Can I get the updated chromium 54.xxx from ports?

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

Petr Fischer

drhowarddrfine

tobik@

Petr Fischer

Petr Fischer

drhowarddrfine

Petr Fischer

cpm@

Moderator

Petr Fischer

cpm@

Moderator

Petr Fischer

cpm@

Moderator

Petr Fischer

cpm@

Moderator

bcomputerguy

Petr Fischer

bcomputerguy

cpm@

Moderator

lonestar

cpm@

Moderator

Petr Fischer

cpm@

Moderator

marino

cpm@

Moderator

bcomputerguy