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

<syncstream>: std::osyncstream memory leak #2819

Closed
segeter opened this issue Jun 23, 2022 · 6 comments
Closed

<syncstream>: std::osyncstream memory leak #2819

segeter opened this issue Jun 23, 2022 · 6 comments
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@segeter
Copy link

segeter commented Jun 23, 2022

Problem Description:
Memory leak occurs when I use std::setw(32)。
Not sure if it's the same issue as #2763 and #2760

My test code:
image

Before the cycle starts:
image

Cycle after a while:
2

@segeter
Copy link
Author

segeter commented Jun 23, 2022

Track analysis, tips here:
1

@CaseyCarter CaseyCarter added the bug Something isn't working label Jun 23, 2022
@CaseyCarter
Copy link
Member

CaseyCarter commented Jun 23, 2022

Thanks for the report, @segeter - we'll determine if this is a duplicate or not and get a fix out as needed.

@fsb4000 do you want to take a look at this and determine if it's a duplicate? Feel free to say no and I'll investigate - I just thought I'd give you first right of refusal since you last touched this.

@fsb4000
Copy link
Contributor

fsb4000 commented Jun 23, 2022

Sure, I will build against main and test it.

@fsb4000
Copy link
Contributor

fsb4000 commented Jun 23, 2022

Yeah, it is not reproducible on main
изображение
изображение

(I'm showing "committed memory" instead of "working set" in the task manager)

@fsb4000
Copy link
Contributor

fsb4000 commented Jun 23, 2022

and yes, on Visual Studio 2022 Professional 17.2.4, I also have the memory leak.

@CaseyCarter CaseyCarter added the duplicate This issue or pull request already exists label Jun 23, 2022
@CaseyCarter
Copy link
Member

CaseyCarter commented Jun 23, 2022

Thanks, @fsb4000! Looks like this is definitely a duplicate of #2760, the fix for which should ship in VS2022 17.4 preview 1.

@CaseyCarter CaseyCarter closed this as not planned Won't fix, can't repro, duplicate, stale Jun 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants