chokidar icon indicating copy to clipboard operation
chokidar copied to clipboard

Error: EBUSY: resource busy or locked, lstat 'C:\DumpStack.log.tmp'

Open Ratstail91 opened this issue 3 years ago • 2 comments
trafficstars

Describe the bug

The following error occurs regularly every 2-10 minutes on my machine - it's happened almost consistently for over a year now, and it's driving me nuts, because I have to reboot webpack. I don't use chokidar directly, but one of my dependencies do.

[watch:client] node:events:368
[watch:client]       throw er; // Unhandled 'error' event
[watch:client]       ^
[watch:client]
[watch:client] Error: EBUSY: resource busy or locked, lstat 'C:\DumpStack.log.tmp'
[watch:client] Emitted 'error' event on FSWatcher instance at:
[watch:client]     at FSWatcher._handleError (C:\Users\kayne\Desktop\core-server\node_modules\chokidar\index.js:647:10)
[watch:client]     at ReaddirpStream.NodeFsHandler._boundHandleError (C:\Users\kayne\Desktop\core-server\node_modules\chokidar\lib\nodefs-handler.js:303:43)
[watch:client]     at ReaddirpStream.emit (node:events:390:28)
[watch:client]     at emitErrorNT (node:internal/streams/destroy:157:8)
[watch:client]     at emitErrorCloseNT (node:internal/streams/destroy:122:3)
[watch:client]     at processTicksAndRejections (node:internal/process/task_queues:83:21) {
[watch:client]   errno: -4082,
[watch:client]   code: 'EBUSY',
[watch:client]   syscall: 'lstat',
[watch:client]   path: 'C:\\DumpStack.log.tmp'
[watch:client] }

Versions (please complete the following information):

  • Chokidar version 3.5.3
  • Node version v16.13.1
  • OS version: Windows 10, via cygwin

To Reproduce:

I think if you get this project up and running entirely on windows, webpack will crash eventually:

https://github.com/krgamestudios/MERN-template

Expected behavior No crashes.

Additional context I don't use chokidar directly, but my dependencies do (webpack-dev-server, nodemon).

Nodemon uses version 3.5.2.

Ratstail91 avatar Aug 01 '22 08:08 Ratstail91

I need the exact code that reproduces the crash. Otherwise, any part of your stack could cause this. Webpack could cause this. We don't fix webpack issues.

Also, the "file" could be actually locked for writing / reading.

paulmillr avatar Aug 01 '22 16:08 paulmillr

The file doesn't exist, but I did get crashes with that MERN-template after all.

I've tried updating everything, even my node version, but the crash still happens - I'm totally lost as to what to do about it.

Edit: I just realized it has to be nodemon's usage, since the crash never happens in production.

Ratstail91 avatar Aug 01 '22 22:08 Ratstail91

Make sure the listening directory/file exists in your system, this error usually occurs when chokidar is trying to listen to a directory which don't exist in the system. Maybe a case of production vs local env directory structure.

rhtpandeyIN avatar Aug 29 '22 07:08 rhtpandeyIN