Open
Conversation
|
你好，能否详细描述下内存泄漏后的表现形式吗？是页面崩溃吗？ @zyy9803 |
Author
是的，我们在使用的过程中向 windowKeyEventHandler 事件传入了 widget 的引用，结果发现对于大看板（含有 80+ widget）每次编辑/查看后都会造成 30-80Mb 的内存上涨，且无法被 gc，分析师长时间编辑保存看板后，整个网页会因内存占用过大而崩溃。 |
非常感谢，有很多次遇到这种情况，但是一直找不到原因，我还想问一下，修改后奔溃的原因是彻底没有了呢？还是奔溃的次数相对减少很多？ |
Author
彻底解决了 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
修复由于事件绑定不稳定引用引发的内存泄漏问题