ffmpegwasm/ffmpeg.wasm

Playground throws DataCloneError on Safari

Open

#528 opened on Jul 31, 2023

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C (17,474 stars) (1,071 forks)batch import
help wanted

Description

Describe the bug Ran playground (https://ffmpegwasm.netlify.app/playground/) on Safari 15.6.1 and it halts after loading the wasm bundle. A DataCloneError is thrown in console.

To Reproduce Steps to reproduce the behavior:

  1. Go to playground on Safari
  2. Wait until the error throws in console.

Expected behavior The wasm bundle should load on Safari.

Desktop (please complete the following information):

  • OS: macOS Monterey
  • Browser: Safari
  • Version: 15.6.1

Contributor guide

Tech stack
wasmjavascript
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of WebAssemblyFamiliarity with Safari WebKit differences
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate the DataCloneError thrown when loading the wasm bundle in Safari. Check the WebAssembly instantiation code in the playground (likely in a file like src/playground.js or similar). The error suggests that some data (likely a wasm module or response) cannot be cloned via structured clone algorithm. Look into whether the issue is related to SharedArrayBuffer or cross origin isolation, as Safari has stricter requirements. Also check for any recent changes to the loading logic. Refer to related issue #528 and comments for additional context.