Summary

Resolve segmentation faults and bus errors during webpack production builds by implementing memory optimizations.

Problem

When building the webpack production bundle, developers encounter build failures on high-core-count systems:

• Exit code 135 (bus error) or 139 (segmentation fault)
• Error occurs during the webpack compilation step: npm run webpack:production

Root Cause: Webpack's TerserPlugin and CssMinimizerPlugin spawn parallel workers equal to CPU core count. On systems with many cores (e.g., 32 cores), this causes memory exhaustion as each worker consumes
significant RAM simultaneously.

Solution

This PR implements two optimizations:

1. Increase Node.js heap size (services/web/Dockerfile)

   • Set --max-old-space-size=12288 (12GB heap)
   • Allows Node.js to handle larger memory requirements during build

2. Limit parallel workers (services/web/webpack.config.prod.js)

   • Set parallel: 2 for both TerserPlugin and CssMinimizerPlugin
   • Reduces peak memory usage by limiting concurrent compression workers
   • Maintains reasonable build times while preventing crashes

Testing

• ✅ Verified successful webpack production build on 32-core system (previously failing)
• ✅ No increase in build time beyond acceptable limits
• ✅ Generated bundle integrity confirmed

Trade-offs

• Slightly longer build times due to reduced parallelism (acceptable for stability)
• Increased memory allocation requirement (12GB heap, reasonable for modern systems)