-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"all goroutines are asleep - deadlock!" on a build #3636
Comments
@amrgamal97 I have a seen a similar issue, though it is intermittent for me. At one point, I got it consistently, but after updating my submodules & another |
We're seeing this in our project when running on Linux, it seems to happen almost every time with Node 20.11.0, and almost not at all (but still sometimes) with Node 18.19.1 or Node 20.11.1 |
we're also seeing this in our environment: stack trace:
|
I am also encountering the Interestingly, when I stop the Angular server and the Additionally, it's worth noting that my setup involves building the Angular application (version 17.1.3) inside a Docker container based on the I am looking for any guidance or suggestions on how to resolve or work around this issue. Has anyone else experienced something similar in a Dockerized environment, particularly with the mentioned versions of Node.js and Angular, on a Mac M1 Pro Max? Any insights or recommendations would be greatly appreciated. Thank you in advance for your assistance. |
This error occurred for me around 50% of the cases when I was building our Angular project within a docker container. So this deadlock might be related to the available system memory running out. |
This solved my issue. I was running into the same stack trace with the error.
I was building locally on M1 pro 16GB where everything was working fine but the build was failing on VM. |
I have plenty of available memory. But it's now happening consistently on my build. Edit: It was due to timeouts being triggered. Due to tailwind taking a very long time. |
I agree with btakita, i have enough memory also encountered this bug, this bug takes some time to occur. |
Thanks to a comment from @kentcdodds #3287 (comment) I was able to fix the same error in our pipelines that use playwright bdd tests after starting the angular dev server (using vite/esbuild under the hood). I added a |
The error occurs consistently when attempting to build the Angular v17 project on the DigitalOcean server.
No issues encountered when building the project locally.
steps I take:
error message:
Environment:
please fix it ASAP.
The text was updated successfully, but these errors were encountered: