The command 'turbo build' is stuck.

[mushroomyuan]

Summary

The turbo version is 2.5.5.
I use pnpm build to execute the packaging command. build script is"build": "cross-env NODE_OPTIONS=--max-old-space-size=8192 turbo build",but it's stuck. It was running good before, but recently it gets stuck during execution.
Sometimes it will execute successfully, but it will get stuck for a long time.It worked once, but it took a full half an hour.

Then I use pnpm turbo run build -vvv to build any sub-package under the project, it will get stuck and won't even reach the build stage.I added --no-cache --no-daemon but it didn't work, it still gets stuck.
Because I added some prompts under the command in package.json, hoping to see which package is stuck, like "build": "echo '[start] @vben-core/icons' && pnpm unbuild && echo '[done] @vben-core/icons'". However, the execution markers did not print out, so I concluded that the build stage was not reached at all. Additionally, if I directly execute pnpm run build in the directory, both vite and unbuild packaging can complete quickly.
I want to know what is wrong with my turbo and this is a screenshot of the stuck position.

this is my turbo.json

{
  "$schema": "https://turbo.build/schema.json",
  "globalDependencies": [
    "pnpm-lock.yaml",
    "**/.env.*local",
    "**/tsconfig*.json",
    "internal/node-utils/*.json",
    "internal/node-utils/src/**/*.ts",
    "internal/tailwind-config/src/**/*.ts",
    "internal/vite-config/*.json",
    "internal/vite-config/src/**/*.ts",
    "scripts/*/src/**/*.ts",
    "scripts/*/src/**/*.json"
  ],
  "globalEnv": ["NODE_ENV"],
  "tasks": {
    "build": {
      "dependsOn": ["^build"],
      "outputs": [
        "dist/**",
        "dist.zip",
        ".vitepress/dist.zip",
        ".vitepress/dist/**"
      ]
    },
    "preview": {
      "dependsOn": ["^build"],
      "outputs": ["dist/**"]
    },
    "build:analyze": {
      "dependsOn": ["^build"],
      "outputs": ["dist/**"]
    },
    "@vben/backend-mock#build": {
      "dependsOn": ["^build"],
      "outputs": [".nitro/**", ".output/**"]
    },
    "test:e2e": {},
    "dev": {
      "dependsOn": [],
      "outputs": [],
      "cache": false,
      "persistent": true
    },
    "typecheck": {
      "outputs": []
    }
  }
}

Additional information

No response

Example

No response

[SametDulger]

Hi mushroomyuan,

From your description, it seems like Turbo is hanging before it even reaches the build scripts, which suggests the issue is likely related to Turbo’s task graph resolution or caching rather than the build commands themselves.

Here are some troubleshooting steps and ideas:

Check for cyclic dependencies
Turbo can hang if there are circular dependencies in your monorepo tasks. Review your package dependencies and dependsOn config to make sure no cycles exist.

Simplify your turbo.json temporarily
Try commenting out all tasks except build and remove dependsOn fields to isolate if a specific dependency causes the hang.

Clear Turbo cache and daemon
You mentioned --no-cache and --no-daemon didn’t help, but try manually removing the cache folder .turbo in your repo root as well, and restart your terminal session.

Verbose logs
Running with pnpm turbo run build -vvv is good; watch for the last logged step before it hangs. Sometimes Turbo outputs subtle info on what it’s waiting on.

Check your globalDependencies
Since you have many entries there, verify none of these files are missing or locked by another process.

Inspect node process
While Turbo is stuck, check your system’s CPU and memory usage. Also, try pausing the process with a debugger or sending SIGUSR1 signal to get a stack trace to see where it’s stuck.

Upgrade Turbo
Version 2.5.5 is stable but check if a newer version fixes related issues.

Build locally per package
Since running pnpm run build in each package works fine, consider temporarily using this while isolating the issue.

If after these you still can’t solve it, sharing a minimal repro repo or opening an issue on Turbo’s GitHub with detailed logs would be helpful.

[mushroomyuan]

Thank you so much for your help. The ideas you provided were very valuable. Although I eventually discovered that the issue didn't actually come from Turbo, but rather from the built-in computer management software on my PC. After I uninstalled it, everything went back to normal. Thanks again for your support.