New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix memory leak & and use Map instead of list to avoid itterating an Array constantly inside a synchronized block #1635
Fix memory leak & and use Map instead of list to avoid itterating an Array constantly inside a synchronized block #1635
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thank you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think generating keys in order to use a map is overkill and is certainly not optimal when a set will do and using a concurrent implementation can avoid synchronization entirely.
data/org.eclipse.birt.data/src/org/eclipse/birt/data/engine/impl/CancelManager.java
Outdated
Show resolved
Hide resolved
It would be great if you could squash this into a single commit. I'm not sure how to actually do that with EGit though. But if you don't know how to do it either, I can try to help with that. Thanks for contributing! |
I have no idea how to actually do it ;) |
46b6a89
to
976efb5
Compare
Commits are now squashed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks better now. I just want to see a clean build before proceeding.
Thanks for contributing and for squashing too. 🏅 |
Switch from List to Map on CancelManager to improve performance,
Fix memory leak & reduce scope of synchronized block Issue #1633