You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! We are using @diplodoc/transform, and our users have noticed that when rapidly switching between screens containing markdown content, the memory usage of the tab keeps increasing. We found the cause in these lines of code. In short, due to the initializations of markdown-it and its plugins for each markdown transformation, a memory leak occurs.
We made some modifications in the code within node_modules: now, the initMarkdownIt function is called only once:
And the issue was resolved. The memory consumption stopped increasing.
What is the expected behavior?
It is expected that with each use of the transform function, markdown-it along with its plugins will not be initialized uncontrollably, thereby preventing memory clutter.
What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered:
Package version
4.41.0
Node version
20.10.0
Platform
No response
What steps will reproduce the bug?
Hi! We are using @diplodoc/transform, and our users have noticed that when rapidly switching between screens containing markdown content, the memory usage of the tab keeps increasing. We found the cause in these lines of code. In short, due to the initializations of markdown-it and its plugins for each markdown transformation, a memory leak occurs.
We made some modifications in the code within node_modules: now, the initMarkdownIt function is called only once:
And the issue was resolved. The memory consumption stopped increasing.
What is the expected behavior?
It is expected that with each use of the transform function, markdown-it along with its plugins will not be initialized uncontrollably, thereby preventing memory clutter.
What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: