Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Website F# film intermittently stalls after seeking in Linux Chromium

Open
  • Is something wrong?
#445 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
html, playwright, typescript
Domain
testing

Research direction

Start with src/website/tests/video-playback.spec.js and the existing expectFramesAdvance helper, then run the supplied Playwright command for the iPhone SE and chromium projects. Inspect the retained failing trace and the listed Linux logs to compare failed and passing runs; the issue does not establish a root cause. Done means identifying and resolving the intermittent stall while preserving the existing pause, timing, seek, frame-count, and elapsed-time assertions.

Written by the indexing model from the issue text.

Description

The existing real-browser regression intermittently stalls after seeking the F# language film to its midpoint in Linux Chromium. No test assertions or production assets were changed while reproducing it.

Reproduction uses the branch's installed Playwright/Chromium and Eleventy development server:

cd src/website
CI=1 npx playwright test tests/docs-nav.spec.js tests/video-playback.spec.js --project="iPhone SE" --project=chromium --workers=1 --retries=0 --repeat-each=3 --trace=retain-on-failure

The /docs/fsharp/ video 0 decodes, pauses, seeks and resumes case fails in expectFramesAdvance after the second play() call. error remains null and paused remains false, but advancing and decoding remain false for the entire 15-second assertion deadline. The initial full website run also failed this case once, then passed it on its configured retry. The first repeated Chromium iteration failed again; the next two passed unchanged. The other inspected films passed.

The actual asset is fsharp-language.mp4, H.264 High level 5.1 at 30 fps plus AAC LC, duration 115.21 seconds. FFmpeg decodes the midpoint region without errors. Three separate cold Chromium probes using the same existing expectFramesAdvance helper passed unchanged. These results establish intermittency, not a confirmed encoder or browser root cause.

The retained failing browser trace shows byte-range requests and no reported HTMLMediaElement error. Keep the existing pause, exact-time, seek, frame-count and elapsed-time assertions intact. Investigate before claiming a clean website release gate. This is a separate observation from the Windows one-frame failure tracked in #394.

Local evidence: target/ci-submit/linux-website.log, linux-website-focused-repeat.log, linux-fsharp-media-inspect.log, linux-media-probe.log; retained trace under the Linux validation copy's website test-results directory.

Dominant language
TypeScript
Stars
168
Forks
9
Avg merge
2h 51m
Merged PRs (30d)
59

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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.

More from Nimblesite/SharpLsp

All issues in Nimblesite/SharpLsp

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.