bytedance/deer-flow

[Stability][BUG-010] Workspace negative performance timestamp runtime error

Closed

#3,121 opened on May 21, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Python (9,005 forks)batch import
help wanted

Repository metrics

Stars
 (67,767 stars)
PR merge metrics
 (Avg merge 2d 5h) (229 merged PRs in 30d)

Description

Parent stability dashboard: #3107

This issue tracks BUG-010 from #3107.

Problem

Opening the workspace can trigger a full-screen Next.js runtime error overlay:

Runtime TypeError
Failed to execute 'measure' on 'Performance': 'WorkspacePage' cannot have a negative time stamp.

Representative frontend log:

Source: frontend browser console log captured by the local frontend service.

[browser] Uncaught TypeError: Failed to execute 'measure' on 'Performance': 'WorkspacePage' cannot have a negative time stamp.

Impact

  • A tester/user can see a framework error instead of the workspace.
  • It disrupts the core entry flow even if persisted thread data is not corrupted.

Open question

This needs confirmation outside the local dev/Turbopack-style environment. If it only happens in development, it may be lower priority; if it can happen in the Docker/release path, it should be fixed before stable tagging.

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.