-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Merge microupdate into master #12258
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
found one more case where documentId can be null
…ng is in progress.
port of #12041 for microupdate
…sion-number Update the Roslyn version to 1.3.2
This commit makes it so that we will always try to generate release nugets except if they depend on prerelease packages. If one of our nuget packages happens to depend on prerelease packages, then when building release nugets, we will simply print a message in the build output and skip release nuget generation for that package (and allow the overall build to succeed).
… instead of adding custom logic in the script for this.
Enable release nugets in microupdate-3.2 branch
this leak was responsible for about 14% of managed memory in customer's dump. basically, in certain condition, if cancellation exception is thrown, we will not close difference viewer which cause all text views to leak. that cause all taggers and text buffers to leak and that cause our preview workspaces to alive. which in turn cause all solutions to alive and so on. all those objects (view, buffer, workspace, solution) are quite big graphs. so ends up eat up 14% of memory. added assert to make sure if we leak viewers again, we get some kind of notification.
fixed DifferenceViewer leak
@dotnet-bot test vsi please |
…into-microupdate Merge microupdate 3.2 into microupdate
@jmarolf something seems up here. There shouldn't be all those commits listed in this PR. |
@dotnet-bot, test vsi please, since I did a push. |
# Conflicts: # build/Targets/VSL.Versions.targets # src/EditorFeatures/Test/CodeActions/AbstractCodeActionTest.cs # src/VisualStudio/Core/Def/Implementation/PreviewPane/PreviewPane.xaml.cs
test vsi please |
test windows_vsi_p0_open_prtest please |
test windows_vsi_p0_open_prtest please |
test windows_vsi_p0_open_prtest please |
1 similar comment
test windows_vsi_p0_open_prtest please |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automatically generated pull request from microupdate into master.
@dotnet/roslyn-infrastructure:
Once the merge can be made and all the tests pass, you are free to merge the pull request.