-
Notifications
You must be signed in to change notification settings - Fork 127
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 crash due to subscribing observer twice to notification center #37074
Fix crash due to subscribing observer twice to notification center #37074
Conversation
71c5fa9
to
033be36
Compare
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.
Tested and it fixes the crash. Hopefully making using interfaces more stable. Happy to approve this.
As a general question, do you know why is there any limitation to the number of observers that can be subscribed to the ads?
Any number of observers can be subscribed. Its more that the same observer should not be subscribed twice to the notification center. When you close an interface, you tend to remove the observer from the notification center. This will only remove the first instance of the subscription, so if your observer is subscribed twice, then your observer is still subscribed |
Maybe in future we can look at adding a check within |
The |
It might be better to get
|
@mantidproject/gatekeepers Please can we merge this before end of today? 🙂 |
Report to: Franz Demmel
Description of work
This PR fixes a consistent crash when using multiple of the Indirect and Inelastic interfaces. It is possible to cause this crash in multiple different ways, from multiple different interfaces. It is caused by adding the same observer to the notification center more than once, and the solution was easy - not to add the observer if it is already subscribed to the notification center.
Fixes #37071
To test:
Data Manipulations
Preview
, then clickRun
Data Analysis
interfaceGaus
functionRun
. There should be no crashReviewer
Please comment on the points listed below (full description).
Your comments will be used as part of the gatekeeper process, so please comment clearly on what you have checked during your review. If changes are made to the PR during the review process then your final comment will be the most important for gatekeepers. In this comment you should make it clear why any earlier review is still valid, or confirm that all requested changes have been addressed.
Code Review
Functional Tests
Does everything look good? Mark the review as Approve. A member of
@mantidproject/gatekeepers
will take care of it.Gatekeeper
If you need to request changes to a PR then please add a comment and set the review status to "Request changes". This will stop the PR from showing up in the list for other gatekeepers.