After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 610017 - Regresses WebKitGTK+'s audio-data-url layout test
Regresses WebKitGTK+'s audio-data-url layout test
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.10.26
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-02-15 18:04 UTC by Gustavo Noronha (kov)
Modified: 2010-12-30 12:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
the failing log (472.56 KB, application/octet-stream)
2010-02-15 18:06 UTC, Gustavo Noronha (kov)
Details

Description Gustavo Noronha (kov) 2010-02-15 18:04:41 UTC
This is the error message our debugging prints:

Error: 12, The autoaudiosink element is not working.
Unhandled GStreamer message type: async-done
Error: 1, GStreamer encountered a general stream error.

This test opens an audio URL using a data: scheme, plays it, and then queries it for its duration. The data's MIME type is audio/3gpp.

Test: http://trac.webkit.org/browser/trunk/LayoutTests/media/audio-data-url.html

I'm attaching the G_DEBUG log of a passing test (before upgrade), and a failing test.
Comment 1 Gustavo Noronha (kov) 2010-02-15 18:06:16 UTC
Created attachment 153849 [details]
the failing log
Comment 2 Gustavo Noronha (kov) 2010-02-15 18:11:54 UTC
Bugzilla won't let me attach very big files, it seems. heh

Here's the passing log:

http://people.collabora.co.uk/~kov/passing-log.gz

 I am filling it under core, but it seems likely that this is something else failing, I'm leaving assigning it properly to your judgement, since I'm not really sure. Also, please let me know of ways I can provide more useful information.
Comment 3 Tim-Philipp Müller 2010-02-15 18:25:33 UTC
That does not look like a bug to me:

0:00:00.732456081 16454      0x21b0410 DEBUG             autodetect gstautoaudiosink.c:303:gst_auto_audio_sink_find_best:<audiosink> error message error message from element 'audiosink-actual-sink-alsa': GstMessageError, gerror=(GstGError)NULL, debug=(string)"gstalsasink.c\(686\):\ gst_alsasink_open\ \(\):\ /GstAlsaSink:audiosink-actual-sink-alsa:\012Device\ \'default\'\ is\ busy";

So basically the audio device on the computer is in use and no other device works, so autoaudiosink errors out and that's that. Seems like expected behaviour to me. (You should ignore all error messages on the bus after the first error).

You may want to configure playbin2 with audio-sink="fakesink sync=true" or "alsasink device=null" or so.
Comment 4 Gustavo Noronha (kov) 2010-02-15 18:38:17 UTC
(In reply to comment #3)
> So basically the audio device on the computer is in use and no other device
> works, so autoaudiosink errors out and that's that. Seems like expected
> behaviour to me. (You should ignore all error messages on the bus after the
> first error).

That makes sense to me, except for the fact that the other audio tests pass, and that just downgrading gstreamer makes this specific test pass again (both in my machine, and in the buildbot, which uses the dummy kernel module). Also, I can play audio files with aplay.
Comment 5 Tim-Philipp Müller 2010-02-15 19:22:13 UTC
Does the gst-launch command from bug #608036 work for you?
Comment 6 Tim-Philipp Müller 2010-02-15 19:22:35 UTC
oh nevermind, I guess that will only work with -bad from git.
Comment 7 Gustavo Noronha (kov) 2010-02-15 20:17:14 UTC
(In reply to comment #6)
> oh nevermind, I guess that will only work with -bad from git.

I'll build the whole gstreamer stack from git to be able to help track these, I'll get back to you on this =)
Comment 8 Sebastian Dröge (slomo) 2010-02-22 19:00:22 UTC
Any news on this?
Comment 9 Philippe Normand 2010-02-23 10:02:23 UTC
Yes having a "failing" log using a correct audio sink would maybe help here.
Comment 10 Tim-Philipp Müller 2010-03-01 10:27:58 UTC
Unmarking as blocker, since we still don't have a bug description in GStreamer terms as far as I can tell, and no one's working on this (and I'm guessing Philippe can't reproduce this either, otherwise he wouldn't have asked for a failing log).
Comment 11 Gustavo Noronha (kov) 2010-03-02 21:08:03 UTC
Just like 610025, this regression seems to have been introduced by this commit:

commit af34d2c1f8c70c9e02d0621a5b72003164fba759
Author: Sebastian Dröge <sebastian.droege@collabora.co.uk>
Date:   Wed Nov 18 09:22:39 2009 +0100

    playbin2: Don't handle DURATION queries during group switches

    During a group switch return the cached duration of the old group
    because the old group still didn't finish playback. If we have no
    cached duration return FALSE.

    Fixes bug #585969.

I just finished bisecting this one (I bisected them separately).
Comment 12 Tobias Mueller 2010-08-23 12:44:47 UTC
Reopening as I can't see any open question.
Comment 13 Tim-Philipp Müller 2010-08-31 09:34:17 UTC
The question is: what's the problem in GStreamer terms? ie. why is this a bug in GStreamer and not in webkit's gstreamer code or the webkit unit tests, and what is the bug/regression?

Also: does this still happen with recent versions?
Comment 14 Tim-Philipp Müller 2010-10-08 17:15:05 UTC
I don't know what to do about this, we still don't have a description of the problem in GStreamer terms. Could just as well be a bug in the test suite. Without more details, we can't do anything about this, so closing this for now. Please re-open if you have more for us to go on.
Comment 15 Philippe Normand 2010-12-30 12:22:46 UTC
For the record, the WebKitGTK buildslaves now have latest gstreamer release and the test runs fine.