[ Sorry for top-posting - the web-mailer is awful and breaks any
formatting...] Hi Stuart, thank you for the info - is the change to glib2
already in the packages? My system has those as of Sunday. As soon as my
system has the latest packages I will reenable 'gst-plugin-scanner' and
see what happens. STEFAN Gesendet: Montag, 24. November 2014 um 11:08 Uhr
Von: "Stuart Henderson" <s...@spacehopper.org>
An: misc@openbsd.org
Betreff: Re: Is this a gstreamer-issue?On 2014-11-22, Stefan Wollny
<stefan.wol...@web.de> wrote:
> Hi there!
>
> The following errors are 100% reproducible on my system:
>
> ~ $ firefox https://google.de
> 1416671415148 GMPInstallManager.simpleCheckAndInstall INFO Last
> check was: 55940 seconds ago, minimum seconds: 86400
> 1416671415154 GMPInstallManager.simpleCheckAndInstall INFO Will not
> check for updates.
>
/usr/local/libexec/gstreamer-1.0/gst-plugin-scanner:/usr/lib/libstdc++.so.57.0:
> /usr/local/lib/libestdc++.so.16.0 : WARNING:
> symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your
> program
> gst-plugin-scanner(5187) in free(): error: bogus pointer (double free?)
> 0xef1f24f8340
> ^C
>
> ~ $ xombrero https://google.de
> xombrero:/usr/local/lib/libestdc++.so.16.0: /usr/lib/libstdc++.so.57.0
:
> WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch,
> relink your program
>
/usr/local/libexec/gstreamer-1.0/gst-plugin-scanner:/usr/lib/libstdc++.so.57.0:
> /usr/local/lib/libestdc++.so.16.0 : WARNING:
> symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your
> program
> gst-plugin-scanner(7894) in free(): error: bogus pointer (double free?)
> 0x8ab0c4f3340
> ^C
>
> This error does not show up with only one regular http-site, but (at
> least with Firefox) happens with 7+ tabs opened.
>
> Both browsers stop responding altogether. I can't even close the
window:
> If started in an xterm (like shown above) I have to kill the app with
> STRG-C; otherwise via "kill -9".

I saw something which looked like this, which went away after I rebuilt
glib2 (just rebuilding/forcibly reinstalling the same version was
enough).
I am wondering if somehow a broken package was built. I committed a minor
tweak to glib2 which will trigger packages to update, so I'm hoping that
just updating to the newest package snapshot will help things, though it
would be nice to know how this happened in the first place.

Reply via email to