Skip to content
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

find a way to drop all information related to diagnostics on close solution. #10703

Closed
heejaechang opened this issue Apr 19, 2016 · 3 comments
Closed
Assignees

Comments

@heejaechang
Copy link
Contributor

currently, we use async events fired to let all listener to clean itself up rather than having special logic for solution close.

this cause async events to accumulate when solution is opened/closed repeatedly in quick succession.

think a way to drop all those at once when solution is closed.

@heejaechang
Copy link
Contributor Author

this new model reduce number of events we fire on solution close. so with v2, this might not an issue anymore.

#10509

@heejaechang
Copy link
Contributor Author

with v2, I didn't see this being issue anymore. moving out milestone to see whether we get any report from users.

@heejaechang heejaechang modified the milestones: 2.0 (Preview 1), 1.3 May 10, 2016
@srivatsn srivatsn modified the milestones: 2.0 (Preview 1), 2.0 (RC) May 10, 2016
@heejaechang
Copy link
Contributor Author

we didn't get any issue reported related to this anymore. closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants