Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gstreamer
gstreamer
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 409
    • Issues 409
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 83
    • Merge Requests 83
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gstreamergstreamer
  • Issues
  • #3

Closed
Open
Opened Jun 27, 2005 by Bugzilla Migration User@bugzilla-migration

filesink: non-fatal out of disk space handling

Submitted by Tim Müller @tpm

Link to original bug (#309117)

Description

What would be really nice to have in filesink (and gnomevfssink as well probably
if possible) is non-fatal out-of-disk-space handling.

File sink could fire an out-of-diskspace signal and put the buffer it wanted to
write in an internal queue. The application can pause the pipeline at this point
and show a warning to the user. Once the user has freed some space, the
application can continue doing what it was doing before, without a single byte lost.

This would be a very neat function to have for (non-realtime) encoders,
transcoders, sound-juicer IMHO.

Cheers
-Tim

Blocking

  • Bug 318853
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gstreamer/gstreamer#3