memory and performance optimizations #13097

sokra · 2021-04-08T15:16:27Z

What kind of change does this PR introduce?
bugfix

Did you add tests for your changes?
no

Does this PR introduce a breaking change?
no

What needs to be documented once your changes are merged?
nothing

webpack-bot · 2021-04-08T15:16:32Z

For maintainers only:

This needs to be documented (issue in webpack/webpack.js.org will be filed when merged)
This needs to be backported to webpack 4 (issue will be created when merged)

and may copy small existing buffers into the larger one

webpack-bot · 2021-04-08T18:40:04Z

@sokra The most important CI builds failed. This way your PR can't be merged.

Please take a look at the CI results from azure (1 errors / 0 warnings) and appveyor (success) and fix these issues.

sokra added 2 commits April 7, 2021 20:48

avoid leaking processed assets

3caf3e9

avoid leaking memory

a3be72b

webpack-bot added the PR: unreviewed label Apr 8, 2021

webpack-bot added the PR: CI-not-ok label Apr 8, 2021

sokra added 3 commits April 8, 2021 18:26

reduce number of write syscalls by creating larger buffers

c1b8a6c

and may copy small existing buffers into the larger one

remove unused method

51bd62d

dispose code generation results after sealing the compilation

cef2a8f

sokra force-pushed the pref/memory branch from b63005a to cef2a8f Compare April 8, 2021 16:34

webpack-bot added PR: CI-ok and removed PR: CI-not-ok labels Apr 8, 2021

sokra enabled auto-merge April 8, 2021 18:39

webpack-bot added PR: CI-not-ok and removed PR: CI-ok labels Apr 8, 2021

sokra merged commit abf0b4e into master Apr 8, 2021

sokra deleted the pref/memory branch April 8, 2021 19:06

Provide feedback