vercel/next.js · error

Profiling is enabled. Note: This may affect performance.

Error message

Profiling is enabled. Note: This may affect performance.

What it means

Informational warning printed by the next-analyze CLI at startup when the --profile flag is set. It tells the developer that CPU profiling instrumentation is active for the analysis run and that collecting the profile adds overhead, so timings and metrics measured during this run are not representative of normal performance.

Source

Thrown at packages/next/src/cli/next-analyze.ts:40

  process.on('SIGTERM', () => {
    saveCpuProfile()
    process.exit(143)
  })
  process.on('SIGINT', () => {
    saveCpuProfile()
    process.exit(130)
  })

  const { profile, mangling, experimentalAppOnly, output, port } = options

  if (!mangling) {
    warn(
      `Mangling is disabled. ${italic('Note: This may affect performance and should only be used for debugging purposes.')}`
    )
  }

  if (profile) {
    warn(
      `Profiling is enabled. ${italic('Note: This may affect performance.')}`
    )
  }

  const dir = getProjectDir(directory)

  if (!existsSync(dir)) {
    printAndExit(`> No such directory exists as the project root: ${dir}`)
  }

  return analyze({
    dir,
    reactProductionProfiling: profile,
    noMangling: !mangling,
    appDirOnly: experimentalAppOnly,
    output,
    port,
  })

View on GitHub (pinned to 0eb3775416)

Solutions

1. Disable profiling when not needed to avoid the performance overhead.

When it happens

Trigger: Thrown at packages/next/src/cli/next-analyze.ts:40 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of vercel/next.js@0eb3775416 (2026-08-19). Data as JSON: /api/errors/41c7d09aa6d3902d. Report an issue: GitHub.