Skip to content
This repository was archived by the owner on Mar 8, 2020. It is now read-only.

Conversation

nklincoln
Copy link
Contributor

Part of #1091

Previous behaviour was to create a new subscription to the same event upon return to page - this was resulting in actioning all subscriber callbacks when an event was emitted. This was resulting in both a memory leak, and the code being executed on out of date information.

Steps to Reproduce

Detailed within #1091

Design of the fix

Cleanup within an ngOnDestroy, that switches a flag used by a "takeWhile" applied to the subscription

Validation of the fix

Application of best practise clean-up for angular subscribers. Manual testing completed against original scenario, in addition to exploratory testing.

Automated Tests

Updated existing unit tests.

@nklincoln nklincoln merged commit a8a49cd into hyperledger-archives:master May 30, 2017
@nklincoln nklincoln deleted the mem-leak-fix branch May 30, 2017 09:13
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant