Re: possible chromium regression on -current (caused by llvm)

2017-03-05 Thread Steven Mestdagh
Robert Nagy [2017-03-03, 16:01:25]:
> The issue is caused by the llvm update most probably,
> reverting back to llvm-3.9.1p0 fixes the issue, so it's either the
> update or a commit after that.
> 
> http://nerd.hu/chromium-56.0.2924.87p0.tgz for amd64 using llvm-3.9.1p0

this fixes the issue for me as well.



Re: possible chromium regression on -current (caused by llvm)

2017-03-04 Thread Stuart Henderson
On 2017/03/03 16:01, Robert Nagy wrote:
> The issue is caused by the llvm update most probably,
> reverting back to llvm-3.9.1p0 fixes the issue, so it's either the
> update or a commit after that.
> 
> http://nerd.hu/chromium-56.0.2924.87p0.tgz for amd64 using llvm-3.9.1p0

SoundCloud fails playback too (mp3 audio only in that case), and fwiw
I don't see anything that looks particularly useful in logs with
"CHROME_LOG_FILE=/tmp/cr.log chrome --v=2 --enable-logging" from around
the time it fails..

[60559:1388765240:0304/111845.142774:VERBOSE1:web_request_time_tracker.cc(181)] 
WR percent 632: 
https://cf-hls-media.sndcdn.com/media/0/31762/6nYxQrtn2S9l.128.mp3?Policy=eyJTdGF0ZW1lbnQiOlt7IlJlc291cmNlIjoiKjovL2NmLWhscy1tZWRpYS5zbmRjZG4uY29tL21lZGlhLyovKi82bll4UXJ0bjJTOWwuMTI4Lm1wMyIsIkNvbmRpdGlvbiI6eyJEYXRlTGVzc1RoYW4iOnsiQVdTOkVwb2NoVGltZSI6MTQ4ODYyNjg0NX19fV19&Signature=kgFut9FjZe6KF89SJLz8gWDHsRh6hpmBvx~geUTQu6nOLr3b4pb-JUgmCCcB70yqDbfuNV8nZpA7UJUe3HH2bFhUBJPm8v6iVZM~U6BulrbjGIDrtobkJtUJn~umf3QP67yFSTnHdrw~ZbgLAylQVASQ4oLl6HSDEAKtNG64OLxrDe5qOrRIUhz5VEPBmaqnrl~W2t78sgf20ciTQ1a17tLJGQCcox2qfcYUgaZnA3zRDJlV72iDx5RTX8riBmZUE7SDTbkwvzPTI9chgEdQ4OBY06A00F56EFRgjZBnGC3B2G1gkESl90DIVDz6IJaVfAvqyvpbGZtoIlCrrRZnpw__&Key-Pair-Id=APKAJAGZ7VMH2PFPW6UQ:
 3/48 = 0.0752559
[37435:-430828960:0304/111845.159489:ERROR:render_media_log.cc(25)] MediaEvent: 
PIPELINE_ERROR pipeline: initialization failed




Re: possible chromium regression on -current (caused by llvm)

2017-03-03 Thread Robert Nagy
The issue is caused by the llvm update most probably,
reverting back to llvm-3.9.1p0 fixes the issue, so it's either the
update or a commit after that.

http://nerd.hu/chromium-56.0.2924.87p0.tgz for amd64 using llvm-3.9.1p0

On (2017-03-03 23:27), Jonathan Gray wrote:
> On Thu, Mar 02, 2017 at 10:48:55PM +1100, Jonathan Gray wrote:
> > On Thu, Mar 02, 2017 at 11:24:13AM +, Stuart Henderson wrote:
> > > On 2017/03/02 22:12, Jonathan Gray wrote:
> > > > On Wed, Feb 22, 2017 at 11:35:24AM +, Dimitris Papastamos wrote:
> > > > > Hi everyone,
> > > > > 
> > > > > I think at some point in the last week a possible chromium regression
> > > > > was introduced.
> > > > > 
> > > > > Youtube videos give a playback error.  This is what I get in the log:
> > > > > 
> > > > > [11087:-105893312:0221/190453.466753:ERROR:sync_control_vsync_provider.cc(144)]
> > > > > glXGetSyncValuesOML should not return TRUE with a media stream counter
> > > > > of 0.
> > > > > [70895:441591864:0221/190454.467559:ERROR:network_interfaces_posix.cc(63)]
> > > > > Not implemented reached in bool
> > > > > net::GetNetworkList(NetworkInterfaceList *, int)
> > > > > [97863:574132800:0221/190457.039780:ERROR:render_media_log.cc(25)]
> > > > > MediaEvent: PIPELINE_ERROR pipeline: initialization failed
> > > > > [11087:-105893312:0221/190457.133204:ERROR:sync_control_vsync_provider.cc(144)]
> > > > > glXGetSyncValuesOML should not return TRUE with a media stream counter
> > > > > of 0.
> > > > > [97863:574132800:0221/190457.459204:ERROR:render_media_log.cc(25)]
> > > > > MediaEvent: PIPELINE_ERROR pipeline: initialization failed
> > > > > [70895:441591864:0221/190500.474199:ERROR:network_interfaces_posix.cc(63)]
> > > > > Not implemented reached in bool
> > > > > net::GetNetworkList(NetworkInterfaceList *, int)
> > > > > 
> > > > > Any ideas?
> > > > > 
> > > > 
> > > > works with 1st of March snapshot on amd64 with:
> > > > 
> > > > chromium-56.0.2924.76
> > > > 
> > > > doesn't with
> > > > 
> > > > chromium-56.0.2924.87
> > > > chromium-56.0.2924.87p0
> > > 
> > > But then iridium fails too, and that wasn't updated since October.
> > 
> > It worked before this pkg_add -uiv chromium command, failed after:
> > 
> > # pkg_add -uiv chromium
> > Update candidates: quirks-2.286 -> quirks-2.290
> > quirks-2.290 signed on 2017-02-27T16:35:48Z
> > quirks-2.286->2.290: ok
> > Update candidates: chromium-56.0.2924.76 -> chromium-56.0.2924.87p0
> > Update candidates: gconf2-3.2.6p8 -> gconf2-3.2.6p8
> > Update candidates: libxslt-1.1.29 -> libxslt-1.1.29
> > Update candidates: gtk+2-2.24.31p0 -> gtk+2-2.24.31p0
> > Update candidates: libgnome-keyring-3.12.0p4 -> libgnome-keyring-3.12.0p4
> > Update candidates: nss-3.28.1 -> nss-3.29.1
> > Update candidates: sqlite3-3.16.2 -> sqlite3-3.17.0
> > chromium-56.0.2924.87p0:.libs-sqlite3-3.14.2+sqlite3-3.16.2->sqlite3-3.17.0:
> >  ok
> > Update candidates: nspr-4.13.1 -> nspr-4.13.1
> > chromium-56.0.2924.87p0:nss-3.28.1->3.29.1: ok
> > Update candidates: cups-libs-2.2.2 -> cups-libs-2.2.2
> > Update candidates: avahi-0.6.32 -> avahi-0.6.32
> > Update candidates: glib2-2.50.3 -> glib2-2.50.3
> > Update candidates: libffi-3.2.1p2 -> libffi-3.2.1p2
> > Update candidates: libelf-0.8.13p3 -> libelf-0.8.13p3
> > Update candidates: pcre-8.38p0 -> pcre-8.38p0
> > Update candidates: python-2.7.13 -> python-2.7.13p0
> > Update candidates: gettext-0.19.8.1 -> gettext-0.19.8.1
> > Update candidates: bzip2-1.0.6p8 -> bzip2-1.0.6p8
> > chromium-56.0.2924.87p0:python-2.7.13->2.7.13p0: ok
> > New package glib2-2.50.3 will run the following commands
> > + @exec /usr/local/bin/glib-compile-schemas 
> > /usr/local/share/glib-2.0/schemas >/dev/null
> > + @exec /usr/local/bin/gio-querymodules /usr/local/lib/gio/modules
> > Running update
> > chromium-56.0.2924.87p0:glib2-2.50.3->2.50.3: ok
> > Update candidates: dbus-1.10.16v0 -> dbus-1.10.16v0
> > Update candidates: dbus-daemon-launch-helper-1.10.16 -> 
> > dbus-daemon-launch-helper-1.10.16
> > Update candidates: libdaemon-0.14p1 -> libdaemon-0.14p1
> > Update candidates: gdbm-1.12 -> gdbm-1.12
> > chromium-56.0.2924.87p0:avahi-0.6.32->0.6.32: ok
> > Update candidates: gnutls-3.5.9p0 -> gnutls-3.5.9p0
> > chromium-56.0.2924.87p0:cups-libs-2.2.2->2.2.2: ok
> > Update candidates: noto-fonts-20150929p2 -> noto-fonts-20150929p2
> > Update candidates: libexecinfo-0.3v0 -> libexecinfo-0.3v0
> > Update candidates: gtk-update-icon-cache-3.22.8p0 -> 
> > gtk-update-icon-cache-3.22.8p0
> > Update candidates: gdk-pixbuf-2.36.5 -> gdk-pixbuf-2.36.5
> > Update candidates: tiff-4.0.7p0 -> tiff-4.0.7p0
> > Update candidates: shared-mime-info-1.8 -> shared-mime-info-1.8
> > Update candidates: libxml-2.9.4p0 -> libxml-2.9.4p0
> > New package shared-mime-info-1.8 will run the following commands
> > + @exec /usr/local/bin/update-mime-database /usr/local/share/mime
> > Running update
> > chromium-56.0.2924.87p0:shared-mime-info-1.8->1.8: ok
> > Update candidates: jasper-1.900.1p5 -> jasper-1.