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 765241 - glimagesink: need to clean window_id when state change form READY to NULL
glimagesink: need to clean window_id when state change form READY to NULL
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
1.8.0
Other Linux
: Normal normal
: 1.8.1
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-04-19 03:08 UTC by Haihua Hu
Modified: 2016-04-19 06:36 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
limagesink: need to clean window_id when state change form READY to NULL (1.16 KB, patch)
2016-04-19 03:09 UTC, Haihua Hu 		committed Details | Review

Description Haihua Hu 2016-04-19 03:08:04 UTC 
When application change pipeline state NULL->READY and then READY->NULL, glimagesink will not clear glsink->window_id. After that, when application change state NULL->READY, the new_window_id is equal to window_id, glimagesink will not set window handle. It will use the internal window but not the window create by application.
Comment 1 Haihua Hu 2016-04-19 03:09:18 UTC 
Created attachment 326304 [details] [review]
limagesink: need to clean window_id when state change form READY to NULL
Comment 2 Sebastian Dröge (slomo) 2016-04-19 06:29:39 UTC 
commit 9b0b7d8eca418e84ae44eb1629a70f915342205e
Author: Haihua Hu <jared.hu@nxp.com>
Date:   Tue Apr 19 10:51:14 2016 +0800

    glimagesink: need to clean window_id when state change form READY to NULL
    
    When application change pipeline state NULL->READY and then READY->NULL,
    glimagesink will not clear glsink->window_id. After that, when application
    change state NULL->READY, the new_window_id is equal to window_id, glimagesink
    will not set window handle. It will use the internal window but not the window
    create by application.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=765241