After pinning down the source of the memory leak in my application, I saw that a huge portion of it came from your library, specifically perlin.js:41.
I understand the motive behind it (it's much faster to retrieve this data from memory), but in my case it led to the application crashing after one hour of perlin-driven motion.
I'd recommend to add some kind of flag to disable the memory, or to stop putting anything in it once it reaches a critical size.
Also, your library has no LICENSE file, so I can't contribute to it.
After pinning down the source of the memory leak in my application, I saw that a huge portion of it came from your library, specifically
perlin.js:41.I understand the motive behind it (it's much faster to retrieve this data from memory), but in my case it led to the application crashing after one hour of perlin-driven motion.
I'd recommend to add some kind of flag to disable the
memory, or to stop putting anything in it once it reaches a critical size.Also, your library has no LICENSE file, so I can't contribute to it.