SSR Memory leak

[Shenmin-Z]

I recently added this package in our project and I was told it's causing memory leak in our prod env.

After reading the code, it seems like it's the sanitized cache that's causing the problem.

sanitized[s] = true;

Every generated html string(s) would be stored in this cache, and it seems to have caused our server run out of memory and keeps restarting.

[atlas1119]

Has it been solved?

[developit]

This is still an issue. Switching to a WeakMap would likely help. I opened a PR with a basic implementation.

[zhuscat]

It seems like the problem has not been solved yet. Is there any plan? 😭

[luwes]

I'm integrating part of this library in an experiment and ran into this issue.

another potential solution is to add an indicator to the "child" that it was generated by h() so no need to store any global collection. the child could add a property to the html string it returns (not sure if this has browser memory implications and it's kind of hacky).

or instead of returning the string s maybe return lightest possible object structure with a toString() method
e.g. { h: true, toString() { return s; } }

[geminigeek]

memory leak still happening , anyone found a fix ?

[TimDaub]

Would be good if this was getting fixed, this is taking down a prod server of mine