[v1.0.0-beta.2 (Windows)] Stuck in chunk assets optimization when parallelization is enabled (`options.parallel`)

[jinker]

webpack 3.5
windows 7

[michael-ciniawsky]

Please provide more info on your current setup webpack.config.js, package.json && Error Logs etc

[kumarharsh]

+1 it's not working under Windows 10 CU - tested in two different systems with different processors and SSD/HDDs. The webpack process takes about 1GB memory but 0% CPU utilization.

This is the uglify config:

          uglifyOptions: {
            compress: { warnings: false },
          },
          sourceMap: true,
          parallel: {
            cache: path.join(CACHE_DIR, 'uglifyjs'),
            workers: true,
          },

Turning parallel off via parallel: false lets me build it. Setting parellel:true and workers: false also makes it work. Could it be an issue with node-worker-farm?

[alexander-akait]

@kumarharsh @jinker known issue, should be fixed in #108. Because parallel (workers) don't use as expected.

[WillooWisp]

I experience similar issues with parallel enabled.

[alexander-akait]

@WillooWisp #118 (comment)

[kumarharsh]

@evilebottnawi great job on the PR. Quick question: does it address parallelization issue in Windows where the webpack process just hangs?

[alexander-akait]

@kumarharsh this PR should fix this, but need tests, can you test this PR on windows?

[kumarharsh]

Unfortunately, seems like it gets stuck at the same place. The children spawned by worker-farm seem to not respond - no CPU is being used, and my build process is stuck at the uglify step. The Memory value also is static for a long time.

---

Edit

So the memory usage for the worker-farm spawns did come down, but the uglify process still hasn't completed.

---

Update

So, after terminating the process, I got the error at the end, though I have no idea where it came from.

Assertion failed: handle->pending_signum == 0, file src\win\signal.c, line 272

[alexander-akait]

@kumarharsh can you create minimum reproducible test repo?