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 767513 - filesink: create empty files if no buffer was received when doing quick play/stop
filesink: create empty files if no buffer was received when doing quick play/...
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
unspecified
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-06-10 20:24 UTC by Xavier Claessens
Modified: 2016-11-11 17:15 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
test case (411 bytes, text/x-csrc)
2016-06-10 20:24 UTC, Xavier Claessens 		Details

Description Xavier Claessens 2016-06-10 20:24:10 UTC 
Created attachment 329584 [details]
test case

If I quickly set my pipeline to PLAYING state then NULL state, and no buffer had time to arrive to the filesink, it leaves an empty file.

The file is opened in GstBaseSrc::start(), I think it should be deleted in GstBaseSrc::stop() if nothing was received inbetween. No?
Comment 1 Tim-Philipp Müller 2016-06-10 20:46:23 UTC 
I would say no :)
Comment 2 Sebastian Dröge (slomo) 2016-06-10 22:07:31 UTC 
I agree, it shouldn't delete the file. It did exactly what was requested IMHO: filesink was started, created the file, no data was received, the file is empty.

If anything this should be a property ("delete-empty-file").