OpenCut-app / OpenCut-app/OpenCut

[BUG]

Open
#608 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
89.8k
Forks
8.9k
PR merge metrics
No merged PRs in 30d

Description

Platform

Arch Linux [Hyprland]

Browser

Firefox 143.0.1

Current Behavior

When I attempting to import a mp3 audio file with duration of approximately 4 minutes, the web 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 about 5mins my system regained 'consciousnesses'.

Expected Behavior

The audio file 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
  1. Access opencut.app
  2. Click Import and select an audio file (~4 minutes in length).
  3. Wait for the import process to begin.
  4. Play video
  5. Observe RAM and CPU usage in Task Manager.
  6. Browser and system becomes unresponsive
Anything else?

No error message is displayed before the crash.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue at opencut.app through Import with an approximately four-minute MP3, then play the video while monitoring RAM and CPU in Firefox. Trace the audio import and playback entry points to identify the resource spike; done means the file imports successfully without exhausting memory, saturating CPU, or making the browser unresponsive.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
audio-video-rtc, frontend, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.