nextjs - 💡(How to fix) Fix Turbopack panic [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#89950Fetched 2026-04-08 00:20:59
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×2closed ×1commented ×1issue_type_added ×1

Error Message

When I run pnpm run dev and navigate to the page /staff of my application (somehow /admin works fine but /staff has the bug) It uses all my CPU cores and freezes for around 30 seconds. Then I get this error log from turbopack.

Code Example

web:dev: thread 'tokio-runtime-worker' (27495) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1285954 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
web:dev:
web:dev: thread 'tokio-runtime-worker' (27496) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1286033 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27492) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1285956 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27498) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1285829 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27497) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1286195 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27501) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1286018 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27500) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1286254 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27499) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1286203 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27493) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1286212 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27494) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1285947 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27496) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1285834 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower ed

---

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.2.0: Tue Nov 18 21:07:05 PST 2025; root:xnu-12377.61.12~1/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 24.13.0
  npm: 11.6.2
  Yarn: N/A
  pnpm: 10.29.2
Relevant Packages:
  next: 16.1.6 // Latest available version is detected (16.1.6).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: standalone
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

No reproduction repo

To Reproduce

It happens on my repository, It's quite big and the logs are not helping me narrow it down so I don't know how to create a reproduction repository.

Current vs. Expected behavior

Hi,

When I run pnpm run dev and navigate to the page /staff of my application (somehow /admin works fine but /staff has the bug) It uses all my CPU cores and freezes for around 30 seconds. Then I get this error log from turbopack.

web:dev: thread 'tokio-runtime-worker' (27495) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1285954 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
web:dev:
web:dev: thread 'tokio-runtime-worker' (27496) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1286033 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27492) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1285956 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27498) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1285829 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27497) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1286195 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27501) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1286018 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27500) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1286254 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27499) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1286203 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27493) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1286212 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27494) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1285947 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower edges
web:dev:
web:dev: thread 'tokio-runtime-worker' (27496) panicked at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs:1818:17:
web:dev: inner_of_upper_lost_followers is not able to remove followers TaskId 1285834 (<DiskFileSystem as FileSystem>::write) from TaskId 1130731 (emit_assets) as they don't exist as upper or follower ed

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.2.0: Tue Nov 18 21:07:05 PST 2025; root:xnu-12377.61.12~1/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 24.13.0
  npm: 11.6.2
  Yarn: N/A
  pnpm: 10.29.2
Relevant Packages:
  next: 16.1.6 // Latest available version is detected (16.1.6).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: standalone

Which area(s) are affected? (Select all that apply)

Turbopack

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

No response

extent analysis

Quick Fix

The panic is a known Turbopack bug that is triggered by the output: "standalone" build mode when a large number of files are emitted.
The easiest way to get your dev server back is to disable Turbopack for next dev (fallback to Webpack) or upgrade to a patched Next.js version where the issue is fixed.


Step‑by‑Step Fix

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix Turbopack panic [1 comments, 2 participants]