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
The docs team hasn't been able to complete rolling out the latest version of Batfish (with Webpack 4) as some of our larger sites are running into issues. The most notable issue is that mapbox-gl-js-docs runs out of memory during build.
This site has had problems in the past with running out of memory: #311
(Unfortunately I think the build logs expired since they aren't recent. I waited too long to move this into its own issue from #317 but here is a most recent log which is pretty much the same failure for all failed builds.)
Here's a progression of the commits and Batfish versions made to mapbox-gl-docs:
Batfish@1.9.8
This Batfish version uses Webpack@3, I'm providing the latest build on this version in case it's helpful to compare the logs.
When debugging with node --inspect, the code had pointed at writing the stats.json file as running out of memory. So we shipped #307 in Batfish@1.11.0 to place stats.json behind a flag.
However, I'm seeing in this build log that it was also pointing the the terser plugin which handles minification. It's likely failing because the chunks are too large (the api and style-spec pages are long).
Batfish@1.11.0
This Batfish version places the generation of stats.json behind a flag. #307
Note: we reverted this change in 1.11.2 because increases maxAsyncRequests and maxInitialRequests effects performance on older mobile devices.
Batfish@1.11.2
This version reverted 1.11.1 and fixed an issue where markdown and JS files were not being watched locally and md and js files were being copied on production.
We could increase the memory via --max-old-space-size to the build script, which would provide mapbox-gl-js-docs enough memory to build. However, this doesn't solve the root problem, but could buy us time until we are able find a fix.
cc @mapbox/docs
The text was updated successfully, but these errors were encountered:
We were able to track this issue to a utility that transformed lots of markdown to JavaScript in the Mapbox GL JS site. The issue is unrelated to Batfish 😅
The docs team hasn't been able to complete rolling out the latest version of Batfish (with Webpack 4) as some of our larger sites are running into issues. The most notable issue is that mapbox-gl-js-docs runs out of memory during build.
This site has had problems in the past with running out of memory: #311
No other sites have logged this error.
Progression of error
(Unfortunately I think the build logs expired since they aren't recent. I waited too long to move this into its own issue from #317 but here is a most recent log which is pretty much the same failure for all failed builds.)
Here's a progression of the commits and Batfish versions made to mapbox-gl-docs:
Batfish@1.9.8
This Batfish version uses Webpack@3, I'm providing the latest build on this version in case it's helpful to compare the logs.
Batfish@1.10.2
This Batfish version upgrades to Webpack@4 (plus bug fixes).
When debugging with node --inspect, the code had pointed at writing the stats.json file as running out of memory. So we shipped #307 in Batfish@1.11.0 to place stats.json behind a flag.
However, I'm seeing in this build log that it was also pointing the the terser plugin which handles minification. It's likely failing because the chunks are too large (the api and style-spec pages are long).
Batfish@1.11.0
This Batfish version places the generation of stats.json behind a flag. #307
Batfish@1.11.0 + increased Node memory
Batfish@1.11.1
This Batfish version increased maxAsyncRequests and maxInitialRequests. #317
Note: we reverted this change in 1.11.2 because increases maxAsyncRequests and maxInitialRequests effects performance on older mobile devices.
Batfish@1.11.2
This version reverted 1.11.1 and fixed an issue where markdown and JS files were not being watched locally and md and js files were being copied on production.
Possible options
minimize: false
: mapbox-gl-js-docs built without running out of memory and in a fraction of the time.--max-old-space-size
to the build script, which would provide mapbox-gl-js-docs enough memory to build. However, this doesn't solve the root problem, but could buy us time until we are able find a fix.cc @mapbox/docs
The text was updated successfully, but these errors were encountered: