Re: possible chromium regression on -current

2017-03-21 Thread mitchell wodach 
It works fine on 57.0.2987.110.

On Mon, Mar 20, 2017 at 4:04 AM, Martijn Rijkeboer  wrote:
> On 03/17/17 09:53, Dimitris Papastamos wrote:
>> Hi,
>>
>> It works for me now with chromium-57.0.2987.98 and the snapshot
>> from the 16th of March.
>
> It works for me too. However, Iridium (54.0) still doesn't work.
>
> Kind regards,
>
>
> Martijn Rijkeboer
>

Re: possible chromium regression on -current

2017-03-20 Thread Martijn Rijkeboer 
On 03/17/17 09:53, Dimitris Papastamos wrote:
> Hi,
> 
> It works for me now with chromium-57.0.2987.98 and the snapshot
> from the 16th of March.

It works for me too. However, Iridium (54.0) still doesn't work.

Kind regards,


Martijn Rijkeboer

Re: possible chromium regression on -current

2017-03-17 Thread Dimitris Papastamos 
Hi,

It works for me now with chromium-57.0.2987.98 and the snapshot
from the 16th of March.

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=kgFut9FjZe6KF89SJLz8gWDHsRh6hpmBvx~geUTQu6nOLr3b4pb-JUgmCCcB70yqDbfuNV8nZpA7UJUe3HH2bFhUBJPm8v6iVZM~U6BulrbjGIDrtobkJtUJn~umf3QP67yFSTnHdrw~ZbgLAylQVASQ4oLl6HSDEAKtNG64OLxrDe5qOrRIUhz5VEPBmaqnrl~W2t78sgf20ciTQ1a17tLJGQCcox2qfcYUgaZnA3zRDJlV72iDx5RTX8riBmZUE7SDTbkwvzPTI9chgEdQ4OBY06A00F56EFRgjZBnGC3B2G1gkESl90DIVDz6IJaVfAvqyvpbGZtoIlCrrRZnpw__=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 ->

Re: possible chromium regression on -current

2017-03-03 Thread Jonathan Gray 
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.900.1p5
> Update candidates: png-1.6.28 -> png-1.6.28
> New package gdk-pixbuf-2.36.5 will run the following commands
> + @exec /usr/local/bin/gdk-pixbuf-query-loaders --update-cache
> Running update
> chromium-56.0.2924.87p0:gdk-pixbuf-2.36.5->2.36.5: ok
> Update candidates: hicolor-icon-theme-0.15 -> hicolor-icon-theme-0.15
> New package gtk-update-icon-cache-3.22.8p0 will run the following commands
> + @exec /usr/bin/find /usr/local/share/icons -type d

Re: possible chromium regression on -current

2017-03-02 Thread Mikolaj Kucharski 
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:

...

> Any ideas?

I also am unable to playback YouTube on Chromium and Firefox. Not sure when
problem started. Tested on:

OpenBSD 6.0-current (GENERIC.MP) #204: Thu Mar  2 11:20:38 MST 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

$ dmesg | grep -e ^int
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09
inteldrm0: msi
inteldrm0: 1366x768, 32bpp

$ pkg_info -qI chromium firefox
chromium-56.0.2924.87p0
firefox-51.0p0

-- 
best regards
q#

Re: possible chromium regression on -current

2017-03-02 Thread Jonathan Gray 
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.900.1p5
Update candidates: png-1.6.28 -> png-1.6.28
New package gdk-pixbuf-2.36.5 will run the following commands
+ @exec /usr/local/bin/gdk-pixbuf-query-loaders --update-cache
Running update
chromium-56.0.2924.87p0:gdk-pixbuf-2.36.5->2.36.5: ok
Update candidates: hicolor-icon-theme-0.15 -> hicolor-icon-theme-0.15
New package gtk-update-icon-cache-3.22.8p0 will run the following commands
+ @exec /usr/bin/find /usr/local/share/icons -type d -mindepth 1 -maxdepth 1 
-exec /usr/local/bin/gtk-update-icon-cache -q -t -f {} \; 2>/dev/null || true
Running update
chromium-56.0.2924.87p0:gtk-update-icon-cache-3.22.8p0->3.22.8p0: ok
Update candidates: libexif-0.6.21p0 -> libexif-0.6.21p0
Update candidates:

Re: possible chromium regression on -current

2017-03-02 Thread Stuart Henderson 
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.

> chromium also tries to open linux paths

I think that's normal.

>  96872 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome/urgent"
>  96872 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome/urgent"
>  96872 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome"
>  96872 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome"
>  12575 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome/urgent"
>  12575 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome/urgent"
>  12575 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome"
>  12575 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome"
>  12575 chrome   NAMI  "/sys/class/tty/tty0/active"
>  58955 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome/urgent"
>  58955 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome/urgent"
>  58955 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome"
>  58955 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome"
>  38195 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome/urgent"
>  38195 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome/urgent"
>  38195 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome"
>  38195 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome"
>  40537 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome/urgent"
>  40537 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome/urgent"
>  40537 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome"
>  40537 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome"
>

Re: possible chromium regression on -current

2017-03-02 Thread Jonathan Gray 
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

chromium also tries to open linux paths

 96872 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome/urgent"
 96872 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome/urgent"
 96872 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome"
 96872 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome"
 12575 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome/urgent"
 12575 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome/urgent"
 12575 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome"
 12575 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome"
 12575 chrome   NAMI  "/sys/class/tty/tty0/active"
 58955 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome/urgent"
 58955 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome/urgent"
 58955 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome"
 58955 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome"
 38195 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome/urgent"
 38195 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome/urgent"
 38195 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome"
 38195 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome"
 40537 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome/urgent"
 40537 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome/urgent"
 40537 chrome   NAMI  "/sys/fs/cgroup/cpuset/chrome"
 40537 chrome   NAMI  "/sys/fs/cgroup/schedtune/chrome"

Re: possible chromium regression on -current

2017-02-23 Thread Martijn Rijkeboer 
On 02/23/17 04:35, Tobias Brodel wrote:
>> I noticed this too and mentioned it on a ports dev chat, I remember
>> it working a few weeks ago. But I'm not sure if it stopped working
>> before or after the 56.0.2924.87 update..
>>
>> It appears to affect only some HTML5 video streaming sites, like
>> Youtube and Twitch, but embedded  still works. It doesn't
>> appear to be drm(4) obviously related either as WebGL demos work
>> fine.
>>
>> At least a few people said it still works for them, so perhaps
>> it's a certain hardware combination that's causing this?
>>
>> -Bryan.
>>
> 
> I'm experiencing this too: Thinkpad T430 on recent snapshots.
> 
> inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09
> drm0 at inteldrm0
> inteldrm0: msi
> inteldrm0: 1366x768, 32bpp
> wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)

I'm having the same problem on recent snapshot with both Chromium and
Iridium. The machine has an Radeon graphics card (see below).

Kind regards,


Martijn Rijkeboer


$ sysctl kern.version
kern.version=OpenBSD 6.0-current (GENERIC.MP) #184: Mon Feb 20 22:44:10
MST 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

$ pkg_info |egrep 'chromium|iridium'
chromium-56.0.2924.87 Chromium browser
iridium-54.0Iridium browser

$ dmesg |grep drm
radeondrm0 at pci1 dev 0 function 0 "ATI Radeon HD 4350" rev 0x00
drm0 at radeondrm0
radeondrm0: msi
radeondrm0: 1920x1200, 32bpp
wsdisplay0 at radeondrm0 mux 1: console (std, vt100 emulation), using wskbd0

Re: possible chromium regression on -current

2017-02-22 Thread Tobias Brodel 



On 02/23/17 14:26, Bryan Steele 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?

I noticed this too and mentioned it on a ports dev chat, I remember
it working a few weeks ago. But I'm not sure if it stopped working
before or after the 56.0.2924.87 update..

It appears to affect only some HTML5 video streaming sites, like
Youtube and Twitch, but embedded  still works. It doesn't
appear to be drm(4) obviously related either as WebGL demos work
fine.

At least a few people said it still works for them, so perhaps
it's a certain hardware combination that's causing this?

-Bryan.



I'm experiencing this too: Thinkpad T430 on recent snapshots.

inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09
drm0 at inteldrm0
inteldrm0: msi
inteldrm0: 1366x768, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)

t/

Re: possible chromium regression on -current

2017-02-22 Thread Bryan Steele 
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?

I noticed this too and mentioned it on a ports dev chat, I remember
it working a few weeks ago. But I'm not sure if it stopped working
before or after the 56.0.2924.87 update..

It appears to affect only some HTML5 video streaming sites, like
Youtube and Twitch, but embedded  still works. It doesn't
appear to be drm(4) obviously related either as WebGL demos work
fine.

At least a few people said it still works for them, so perhaps
it's a certain hardware combination that's causing this?

-Bryan.

radeondrm0 at pci1 dev 5 function 0 "ATI Radeon HD 3000" rev 0x00
drm0 at radeondrm0

name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, 
GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, 
GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync
GLX version: 1.4
GLX extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, 
GLX_ARB_get_proc_address, GLX_ARB_multisample, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, 
GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync
Extended renderer info (GLX_MESA_query_renderer):
Vendor: X.Org (0x1002)
Device: AMD RS780 (DRM 2.29.0 / 6.0) (0x9616)
Version: 13.0.3
Accelerated: yes
Video memory: 512MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 3.1
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.0
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RS780 (DRM 2.29.0 / 6.0)
OpenGL core profile version string: 3.1 (Core Profile) Mesa 13.0.3
OpenGL core profile shading language version string: 1.40
OpenGL core profile context flags: (none)
OpenGL core profile extensions:
GL_AMD_conservative_depth, GL_AMD_draw_buffers_blend, 
GL_AMD_performance_monitor,

possible chromium regression on -current

2017-02-22 Thread Dimitris Papastamos 
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?