-
Notifications
You must be signed in to change notification settings - Fork 165
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
favicons seem to never call back in some cases #318
Comments
Because it is async, we don't support it |
What do you mean ? |
callback is async and we don't use |
oh i see, but that is not the issue. what I mean is that the callback never get called (removing async here will not change that) |
@wighawag please create reproducible test repo |
In this repo https://github.com/wighawag/purple-warlock |
I'm actually having the same issue and my callback is completely sync (saying that looking at the code that wouldn't really make a difference). I think it was not happening on V5.4.1 |
I created this super simple example and I explained how to make it fail. I also added the module "why-is-node-running" to it and like that it's possible to see the handles that are holding the process https://github.com/jdmerinor/testFavicons |
@alexander-akait On the repo mentioned above I added also the logs that I got when it failed and thew handles taken, I'm adding those here for reference, this was basically my output:
|
I think this is why the program hangs when I use favicons-webpack-plugin. |
Is there an update on this? With the new version of Node JS it gets stuck even worse... now not even with a retry it will be able to come back to life :( |
Same thing happens to me. Randomly stalls to the same Windows 11 and Node v16.14.2 |
@peksipatongeis may you try to reproduce the issue with favicons 7.0.0-beta.4? |
Tested with
Edit. I wonder if this issue is similar to what we have in here? |
I was not able to reproduce this on Linux, but somehow this happens from time to time on Windows virtual machine. I am afraid, this is some sort of low-level concurrency issue with |
I have the following code
and sometime, the callback never get called. I have to stop the process
any idea ?
The text was updated successfully, but these errors were encountered: