You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specifically if I import this library - the process always exits with a write EPIPE or "This socket has been ended by the other party," presumably between a thread-loader WorkerPool communicating with its children. If I do not import this library it exits with one of those errors 15% of the time and hangs ~85% of the time.
I don't think this is reproducible any longer, nor do I know how we would even start diagnosing it considering it would need a large stack to reproduce. Since the specific issue was fixed under webpack-contrib/thread-loader#33 I think we can go ahead an close this. If anyone has a reproducible use-case feel free to log a new issue.
I'm trying to debug an issue where sending SIGINT to the running process results in a hang - the process refuses to exit.
However, the mere act of adding a
require
for this library causes the issue to disappear.The actual hang is somewhere in a mess of webpack-serve, webpack-dev-middleware, webpack, and something called thread-loader.
Do you have any hypotheses for why that could happen?
The text was updated successfully, but these errors were encountered: