dev server constantly crashing with "Error: EBUSY: resource busy or locked, lstat 'C:\DumpStack.log.tmp'"

[mklueh]

Describe the bug

I have the feeling that this happens after a while when a few reloads have happened, and I'm not sure if it is even related to this library, as I'm facing the same with Nuxt as well. Might be Vite related, but maybe sb has the same problem and has found a workaround.

WXT 0.19.13
✔ Started dev server @ http://localhost:3001
ℹ Pre-rendering chrome-mv3 for development with Vite 5.4.9
- Preparing...
✔ Built extension in 5.507 s
  ├─ .output\chrome-mv3\manifest.json                1.37 kB
  ├─ .output\chrome-mv3\popup.html                   636 B
  ├─ .output\chrome-mv3\background.js                89.43 kB
  ├─ .output\chrome-mv3\chunks\popup-CMB-8dTp.js     3.1 kB
  ├─ .output\chrome-mv3\content-scripts\content.js   701.24 kB
  ├─ .output\chrome-mv3\content-scripts\content.css  2.36 kB
  ├─ .output\chrome-mv3\icon\128.png                 3.07 kB
  ├─ .output\chrome-mv3\icon\16.png                  559 B
  ├─ .output\chrome-mv3\icon\32.png                  916 B
  ├─ .output\chrome-mv3\icon\48.png                  1.33 kB
  ├─ .output\chrome-mv3\icon\96.png                  2.37 kB
  └─ .output\chrome-mv3\wxt.svg                      1.07 kB
Σ Total size: 807.45 kB
node:events:497
      throw er; // Unhandled 'error' event
      ^
Error: EBUSY: resource busy or locked, lstat 'C:\DumpStack.log.tmp'
Emitted 'error' event on FSWatcher instance at:
    at FSWatcher._handleError (file:///C:/Users/MyPC/Workspace/my-project/node_modules/vite/dist/node/chunks/dep-Cyk9bIUq.js:44469:10)
    at ReaddirpStream.NodeFsHandler._boundHandleError (file:///C:/Users/MyPC/Workspace/my-project/node_modules/vite/dist/node/chunks/dep-Cyk9bIUq.js:42942:43)
    at ReaddirpStream.emit (node:events:519:28)
    at ReaddirpStream.emit (node:domain:488:12)
    at emitErrorNT (node:internal/streams/destroy:170:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at processTicksAndRejections (node:internal/process/task_queues:90:21) {
  errno: -4082,
  code: 'EBUSY',
  syscall: 'lstat',
  path: 'C:\\DumpStack.log.tmp'
}
Node.js v22.9.0

Reproduction

Not sure, but I have this with Nuxt too, but not with my express server

Steps to reproduce

No response

System Info

System:
    OS: Windows 11 10.0.22631
    CPU: (8) x64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
    Memory: 1.95 GB / 15.77 GB
  Binaries:
    Node: 22.9.0 - ~\AppData\Local\Volta\tools\image\node\22.9.0\node.EXE
    Yarn: 4.5.1 - ~\AppData\Local\Volta\tools\image\yarn\4.5.1\bin\yarn.CMD
    npm: 10.8.3 - ~\AppData\Local\Volta\tools\image\node\22.9.0\npm.CMD
  Browsers:
    Chrome: 130.0.6723.59
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    vite: 5.4.9 => 5.4.9 
    wxt: 0.19.13 => 0.19.13

Used Package Manager

yarn

Validations

• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[1natsu172]

@mklueh I think you should submit a minimal reproduction. Can you submit it?

[aklinker1]

If it's happening with Nuxt, it's probably related to a dependency we share... Maybe Chokidar? What versions of chokidar are listed in your lockfile?

[mklueh]

Good point. I was on chokidar 3.6.0 before, and now I've enforced 4.0.1 but facing the same problem

[mklueh]

Haven't faced it with Nuxt anymore for a while now, but the Wxt issue remains. Are you guys developing on Windows?

[aklinker1]

I don't have a windows machine. Did Nuxt have an issue for this that got closed that we can reference?