OpenCut-app / OpenCut-app/OpenCut
[BUG] Excessive RAM/CPU usage and browser crash when importing large file video
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 89.9k
- Forks
- 8.9k
- PR merge metrics
- No merged PRs in 30d
Description
Platform
Window 11
Browser
Egde
Current Behavior
When I attempting to import a 2K resolution video file with duration of approximately 50 minutes, the application rapidly consumes excessive system resource. RAM usage spikes dramatically(eventually exhausting available memory), CPU usage remains at or near 100%, and browser unresponsive. After a short period, the browser tab crashes entirely.
Expected Behavior
The video should import successfully without causing extreme memory or CPU usage, and the browser should remain stable and responsive throughout the process.
Recurrence Probability
Always
Steps To Reproduce
- Access opencut.app
- Click Import and select a 2K resolution video file (~50 minutes in length).
- Wait for the import process to begin.
- Play video.
- Observe RAM and CPU usage in Task Manager.
- Browser becomes unresponsive and eventually crashes.
Anything else?
The issue occurs regardless of whether other tabs or applications are running.
Tested with multiple 2K 50‑minute video files; results are consistent.
No error message is displayed before the crash.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the import flow on opencut.app and reproduce with a 2K, approximately 50-minute video while monitoring Task Manager. Trace the import and playback path to identify the source of the RAM and CPU spike; done means the video imports and plays without exhausting memory, maxing CPU, or crashing the browser.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100