fix: memory leak caused by function cache

[wang1212]

🤔 This is a ...

• New feature
• Bug fix
• Site / Document optimization
• TypeScript definition update
• Refactoring
• Performance improvement
• Code style optimization
• Test Case
• Branch merge
• Other (about what?)

🔗 Related issue link

💡 Background and solution

In some frequently called function scenarios, such as attribute parsing, a cache strategy is used for tool functions to optimize performance. However, this part of the cache is not released in time when the canvas instance is destroyed, resulting in serious memory leaks.

By clearing the function cache in time when the canvas instance is destroyed, the memory leak problem can be safely fixed.

📝 Changelog

Language	Changelog
🇺🇸 English	fix: memory leak caused by function cache
🇨🇳 Chinese	fix: 函数缓存引起的内存泄露

☑️ Self Check before Merge

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• TypeScript definition is updated/provided or not needed
• Changelog is provided or not needed

[petercat-assistant]

Walkthrough

This pull request addresses a critical memory leak issue caused by function caching in the canvas instance. The solution involves clearing the function cache when the canvas instance is destroyed, ensuring that memory is properly released and preventing leaks.

Changes

File	Summary
.changeset/wise-birds-begin.md	Added a changeset note for the patch fixing the memory leak caused by function cache.
packages/g-lite/src/Canvas.ts	Added a call to memoize.clearCache() in the destroy method to clear the function cache when the canvas instance is destroyed.
packages/g-lite/src/utils/memoize.ts	Implemented memoize.cacheList and memoize.clearCache() to manage and clear function caches effectively.