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 575388 - [aacparse] deadlocks in busy loop when seeking
[aacparse] deadlocks in busy loop when seeking
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other Linux
: Normal normal
: 0.10.12
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-14 21:29 UTC by René Stadler
Modified: 2009-03-23 19:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description René Stadler 2009-03-14 21:29:12 UTC 
The AAC parser can easily get stuck in an endless loop when seeking (at least in pull mode). This was found using Insanity when -bad was frozen already.

I'll fix this after the freeze, keeping this bug as a reminder :)

BTW no need to have/had this as a blocker, Wim has dropped the rank of this element for reasons like these I guess.
Comment 1 René Stadler 2009-03-23 19:05:16 UTC 
commit 83016fa9dc4d3229aae00ce53488a6375ca43132
Author: René Stadler <mail@renestadler.de>
Date:   Thu Mar 19 01:17:25 2009 +0200

    aacparse: Fix busyloop when seeking. Fixes #575388
    
    The problem is that after a discont, set_min_frame_size(1024) is called when
    detect_stream returns FALSE. However, detect_stream calls check_adts_frame
    which sets the frame size on its own to something larger than 1024. This is the
    same situation as in the beginning, so the base class ends up calling
    check_valid_frame in an endless loop.