[BUG] FFmpeg worker crashes

[patelnitya54]

Bug description

When exporting long-duration videos, the FFmpeg worker fails during processing and shows an "FFmpeg worker error". After this error, the export process stops unexpectedly and the UI may remain stuck in a loading or processing state.
This issue occurs especially with longer videos and results in incomplete exports.

Steps to reproduce
Steps to reproduce the behavior:

1. Go to the Reframe editor/dashboard
2. Upload a long-duration video file (e.g. >10–15MB or longer clip)
3. Select an export preset (e.g. Instagram Reels / 1080p)
4. Click on "Export Rapidly"
5. Wait for processing to continue
6. See error: "FFmpeg worker error"

Expected behavior

• Video should export successfully without worker failure
• FFmpeg should complete processing even for long video
• UI should properly handle errors and reset state if export fails

Actual behavior

• FFmpeg worker crashes during processing
• Export fails unexpectedly
• UI shows "FFmpeg worker error"
• Processing state may remain stuck or inconsistent

Browser and OS info

• OS: Windows 11 / Ubuntu (use your system)
• Browser: Chrome
• Version: 136

Video format (if relevant)

• Input video format: MP4
• Export preset used: Instagram Reels / 1080p
• File size: Large video (long-duration clip ~10–20MB+)

Screenshots/screen recording

[github-actions]

👋 Thanks for opening an issue, @patelnitya54!

Our maintainers will review this shortly 🚀

Before you start working

• 📖 Read the CONTRIBUTING.md guide
• 💬 Wait for a maintainer to assign you the issue before starting work
• 🔍 Search for existing issues to avoid duplicates

For GSSoC'26 contributors

If you're contributing under GirlScript Summer of Code 2026, please mention it in your comment when requesting assignment:

"I'd like to work on this — contributing under GSSoC'26"

Architecture notes

Reframe is a static Next.js app with output: "export". Key points:

• All video processing uses FFmpeg.wasm (client-side, no server)
• headers() in next.config.ts won't work — use vercel.json instead
• not-found.tsx requires public/404.html + vercel.json routes config

Happy contributing! ⭐ Star the repo if you find it useful!

[patelnitya54]

I'd like to work on this — contributing under GSSoC'26

[mrdeyroy]

/assign

I would love to work on this issue. Thanks!

[github-actions]

Hey @mrdeyroy, this issue has been assigned to you! 🎉 Please make progress within 5 days or it will be automatically unassigned due to inactivity.

[patelnitya54]

/assign
I'd like to work on this — contributing under GSSoC'26

[github-actions]

Hey @patelnitya54, this issue is already assigned to @mrdeyroy. Please pick another issue or wait for it to become available. You can browse open unassigned issues here: https://github.com/magic-peach/reframe/issues?q=is%3Aissue+is%3Aopen+no%3Aassignee

[mrdeyroy]

/assign I'd like to work on this — contributing under GSSoC'26

Transferring assigned issue maybe not possible otherwise i would transfer it to you!

[github-actions]

Hey @mrdeyroy, this issue is already assigned to @mrdeyroy. Please pick another issue or wait for it to become available. You can browse open unassigned issues here: https://github.com/magic-peach/reframe/issues?q=is%3Aissue+is%3Aopen+no%3Aassignee

[patelnitya54]

/assign I'd like to work on this — contributing under GSSoC'26

Transferring assigned issue maybe not possible otherwise i would transfer it to you!

no problem

[github-actions]

Hey @patelnitya54, this issue is already assigned to @mrdeyroy. Please pick another issue or wait for it to become available. You can browse open unassigned issues here: https://github.com/magic-peach/reframe/issues?q=is%3Aissue+is%3Aopen+no%3Aassignee