EBUSY: resource busy or locked, access '\\\\.\\pipe\\nitro\\worker-11280-1.sock' about nuxt HOT 4 OPEN

Would you see if you can reproduce this in pure Nitro (reproduction sandbox), and if so, raise there? 🙏

from nuxt.

@danielroe Sure, I'm on it. Thank you!

from nuxt.

I'm also getting this, basically a transient issue when the dev server is spammed with too many requests (these are performing MSSQL queries, maybe this is impacting it)

from nuxt.

@danielroe @pi0 I was able to make a simplified Nuxt app to reproduce the issue on Windows: https://stackblitz.com/edit/nuxt-apollo-demo-cd35uc?file=nuxt.config.ts

Please let me know if you prefer to continue the discussion here or if we should move it to Nitro.

I don't why, but it my case, an EBUSY is only thrown by the Nodejs Event Loop when there are too many requests to the API and they are passing by a proxy. By disabling the proxy, the operation don't get locked.

I found this in node/deps/uv/docs/src/loop.rst that might bring some light:

Releases all internal loop resources. Call this function only when the loop
has finished executing and all open handles and requests have been closed,
or it will return UV_EBUSY. After this function returns, the user can free
the memory allocated for the loop.

from nuxt.