57 bug high cpu usage when chaining ffdecoder with writegear#59
Merged
abhiTronix merged 6 commits intoApr 18, 2026
Merged
Conversation
- Enable navigation.prune for better sidebar performance - Add creation date and fallback to git-revision-date plugin - Configure mkdocstrings filters and fix options nesting - Add mermaid diagram support via superfences custom fences - Enable generic arithmatex and magiclink shorthand options - Replace exclude plugin with exclude_docs directive - Fix typo: "Recipies" -> "Recipes" in nav section
abhiTronix
added
Documentation 📑
3 tasks
abhiTronix
added
CI : Skipped 🎲
github-project-automation
Bot
moved this from In Progress
to Done
in VidGear + Deffcode
abhiTronix
deleted the
57-bug-high-cpu-usage-when-chaining-ffdecoder-with-writegear
branch
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brief Description
When using FFdecoder and WriteGear (from vidgear) together to decode and re-encode video frames, users may experience very high CPU utilization.
Requirements / Checklist
Related Issue
#57
Context
When running FFdecoder.generateFrame() directly into WriteGear.write(), the CPU usage spikes to its absolute maximum. This PR adds a "Best Practices" or "Troubleshooting" section in the documentation explaining why this CPU spike happens and providing parameters to mitigate it depending on the user's goal.
Types of changes
Miscellaneous (if available):
None