-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
datepicker: memory leak #1852
datepicker: memory leak #1852
Conversation
8d95a3d
to
543fa24
Compare
Hey @jigar140291 thanks for your contribution and sorry for the delay. Sounds reasonable to me and I'm able to debug this, but not within memory debugger functionality. Can you help me out here? @arschmitz What do you think about this? |
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.
This makes sense to me but it'd perhaps be good to have a unit test verifying the field is cleared.
@jigar140291 Would you mind adding a test for this? |
@fnagel Sorry for the delay. I will look into the test cases. |
@fnagel I have added test cases. could you please review it. |
@mgol unit test case updated. |
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! @fnagel @arschmitz what do you think?
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! Only one thing left before merging:
- Squash commit into one
- Improve commit message (e.g. "Datepicker: Fix current instance memory leak and add tests")
I can do this for you too if needed.
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.
Working on it. Thanks for the feedback.
@fnagel it's done. could you please review and merge. |
@jigar140291 Sorry but now there are even more commits. Wanna try again or should I do this for you? |
@fnagel seems like I squash it incorrectly. Could you do that for me. Thanks!! |
ef4f20e
to
a35c0b1
Compare
@fnagel I have squashed commits into one single commit. please check and merge. |
@arschmitz Could you please review and merge it. |
Ticket: 15250