set/unset per method package is using memoize, not memoizeCapped as in lodash proper

[justinbarry]

We discovered an unbounded usage of memory recently while using the per method packages.

Demonstrated here: https://github.com/justinbarry/lodash-mem-leak-example

Individual unset package

lodash/lodash.unset/index.js

Line 655 in b4e9284

var stringToPath = memoize(function(string) {

Individual set package

lodash/lodash.set/index.js

Line 654 in ca149bd

var stringToPath = memoize(function(string) {

In lodash proper:

lodash/.internal/stringToPath.js

Line 26 in aff1928

const stringToPath = memoizeCapped((string) => {

[jdalton]

Hi @justinbarry!

The per method packages are soft deprecated. For the most up-to-date v4 you should stick with the primary lodash package and cherry-pick your methods lodash/unset.

[justinbarry]

@jdalton is that information documented anywhere? If not, could I help with that?

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.