- Operating System: Alpine 3.12
- Node Version: 14.16.1
- NPM Version: yarn 1.22.5
- webpack Version: 5.38.1
- thread-loader Version: 3.0.4
Expected Behavior
The build completes.
Actual Behavior
The build hangs, it never terminates, it stops with webpack 5.38.1 compiled successfully in XXX ms but never displays the Done in XXXs. neither quits.
How Do We Reproduce?
I isolated that it comes from the warmup statement. I think the loader never exits because of the new cache API (the filesystem one from the v5) which surely does fulfill its caching purpose but as a consequence no job is being launched so the warmup workers are pending/zombies.
You can reproduce with that branch from your example: https://github.com/eytienne/thread-loader/tree/repro_build_hangs
Expected Behavior
The build completes.
Actual Behavior
The build hangs, it never terminates, it stops with
webpack 5.38.1 compiled successfully in XXX msbut never displays theDone in XXXs.neither quits.How Do We Reproduce?
I isolated that it comes from the
warmupstatement. I think the loader never exits because of the new cache API (the filesystem one from the v5) which surely does fulfill its caching purpose but as a consequence no job is being launched so the warmup workers are pending/zombies.You can reproduce with that branch from your example: https://github.com/eytienne/thread-loader/tree/repro_build_hangs