-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
pathUtils | joinCache memory leak #414
Comments
Oh, it was for cache, how many run do you have? |
@alexander-akait The service runs (potentially) infinite bundling processes |
I can create a PR for adding a clearCache function, WDYT? By the way, there is a third option to use LRU cache object with fixed size |
created a fork with the fix |
Well, seems like it works, can we do something similar for enhanced-resolve? |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Hey guys,
We use webpack in our services to bundle code.
A webpack compiler is being created for each bundling process by importing
webpack
creator function fromwebpack
.Webpack is using enhanced-resolve to resolve module paths.. We also have custom resolvers that extends
ResolvePluginInstance
which is aenhanced-resolve
resolver AFAIK.Those resolvers are injected to webpack using the
plugins
propertyAfter a while, we saw that as the service bundle code a memory leak is increasing in our service.
(for each bundle a new compiler of webpack is created)
As you can see in the heap-dump picture, it is related to
joinCache
property.This property can be found here. this is a non-exported global variable that never cleans.
As I can see it, you can help us in 2 ways,
LMK if you need any further data/explanations,
Thanks 🙏🏼🙏🏼
The text was updated successfully, but these errors were encountered: