Skip to content
This repository was archived by the owner on Jun 20, 2019. It is now read-only.

Fix websocket close handshake issue and race condition when websocket… #151

Merged
merged 1 commit into from
Sep 12, 2017

Conversation

pan-wang
Copy link
Contributor

… client disconnect without close handshake #77

… client disconnect without close handshake
@@ -376,6 +376,7 @@ ASPNETCORE_CONFIG::Populate(
strExpandedEnvValue.Reset();
pEnvVar->Release();
pEnvVar = NULL;
pEntry->Dereference();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this related to the fix or is it unrelated.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this fixes a memory leak

Copy link
Contributor

@jhkimnew jhkimnew left a 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.

@pan-wang
Copy link
Contributor Author

thanks

@pan-wang pan-wang merged commit a732b10 into dev Sep 12, 2017
@pan-wang pan-wang deleted the panwang/websocket branch September 12, 2017 23:24
@risogolo
Copy link

So, when this bugfix will be released as a part of new version of nuget package for websockets?

@Tratcher
Copy link
Member

@risogolo the bugfix is not in the websocket nuget package, it's in the AspNetCoreModule which installs via MSI. Expect the MSI with 2.1.0-preview.

@risogolo
Copy link

but this bug is also in 1.x

@Tratcher
Copy link
Member

ANCM does not version like packages, it's an in place update. The next MSI released will affect all versions of ASP.NET Core.

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

Successfully merging this pull request may close these issues.

6 participants