Bug Report – Gyroflow Adobe Plugin (Premiere Pro + Media Encoder)
Severe memory leak in Gyroflow plugin 2.1.1 – Adobe Media Encoder commits 100–116 GB during export, causing system resource exhaustion and GPU driver crash
Description
When using the Gyroflow Adobe plugin (v2.1.1) inside Premiere Pro and exporting via Adobe Media Encoder, the encoder process (Adobe Media Encoder.exe) commits an extremely large amount of virtual memory (105–116 GB). This exhausts the system commit limit, triggers Windows low virtual memory warnings, and causes GPU driver TDR/reset (screen rotation on secondary monitor, system GUI freeze).
Downgrading the Gyroflow plugin to v2.0.2 completely resolves the issue — export finishes successfully with normal memory usage.
Versions
- Gyroflow plugin: 2.1.1 (broken) → 2.0.2 (working)
- Premiere Pro: 26.2.0 (build 65)
- Adobe Media Encoder: 26.2.0.52
- GPU: AMD (Radeon RX6600 series, driver updated to latest on 30 Apr 2026)
- OS: Windows 11 (64-bit)
- Plugin installed via: Gyroflow app "Video editor plugins" panel, downgraded manually.
Steps to Reproduce
- Apply Gyroflow effect to a clip in Premiere Pro timeline.
- Send the sequence to Adobe Media Encoder for H.264 export.
- Start the export queue.
- Memory usage of
Adobe Media Encoder.exe skyrockets.
Expected Behavior
Normal memory usage by Media Encoder (few GB at most), successful export without system instability.
Actual Behavior + Logs
Event Viewer – System log (Event ID 2004 – Resource Exhaustion)
First occurrence (04:38:31):
Adobe Media Encoder.exe (18376) – CommitCharge: 105386131456 bytes (~105 GB)
Adobe Premiere Pro.exe (10020) – CommitCharge: 10749956096 bytes (~10 GB)
SystemCommitCharge: 130917552128 bytes (out of 131030728704 limit)
Second occurrence (04:44:03) – export failure point:
Adobe Media Encoder.exe (18376) – CommitCharge: 116587016192 bytes (~116 GB)
SystemCommitCharge: 130792816640 bytes (critical exhaustion)
Additional symptoms observed:
- Windows warning: "System has low virtual memory. Increase pagefile size."
- GPU driver reset (AMD) → secondary vertical monitor image rotates horizontally, system GUI becomes unresponsive.
- Export fails in Media Encoder with
GPU Render Error / low-level exception (consistent with system under extreme memory pressure).
- After downgrading Gyroflow plugin to 2.0.2 the same project exports without any memory spike or crash.
Environment
- CPU: AMD Ryzen 9 5900X
- RAM: 64 GB
- GPU: AMD Radeon RX6600 (driver 32.0.21043.5001)
- Storage: SSD (pagefile on fast drive)
Additional Context
- The issue only occurs with Gyroflow plugin v2.1.1. Version 2.0.2 works flawlessly on the same timeline and settings. 2.1.0 not tested.
- Plugin was loaded successfully according to Premiere Pro UXP logs.
- No other third-party effects were active during the failing exports.
- This is a regression — the plugin worked fine before the 2.1 update.
Bug Report – Gyroflow Adobe Plugin (Premiere Pro + Media Encoder)
Severe memory leak in Gyroflow plugin 2.1.1 – Adobe Media Encoder commits 100–116 GB during export, causing system resource exhaustion and GPU driver crash
Description
When using the Gyroflow Adobe plugin (v2.1.1) inside Premiere Pro and exporting via Adobe Media Encoder, the encoder process (
Adobe Media Encoder.exe) commits an extremely large amount of virtual memory (105–116 GB). This exhausts the system commit limit, triggers Windows low virtual memory warnings, and causes GPU driver TDR/reset (screen rotation on secondary monitor, system GUI freeze).Downgrading the Gyroflow plugin to v2.0.2 completely resolves the issue — export finishes successfully with normal memory usage.
Versions
Steps to Reproduce
Adobe Media Encoder.exeskyrockets.Expected Behavior
Normal memory usage by Media Encoder (few GB at most), successful export without system instability.
Actual Behavior + Logs
Event Viewer – System log (Event ID 2004 – Resource Exhaustion)
First occurrence (04:38:31):
Second occurrence (04:44:03) – export failure point:
Additional symptoms observed:
GPU Render Error/ low-level exception (consistent with system under extreme memory pressure).Environment
Additional Context