Memory leak with std::vector<std::string>.insert using const std::string - by raic

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 596565 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 9/9/2010 1:32:45 PM
Access Restriction Public


Each time you insert a const std::string into a std::vector<std::string> you leak 16 bytes. It's unclear as what the root problem is, so this is just one example which causes the symptoms.
Sign in to post a comment.
Posted by Microsoft on 9/23/2010 at 5:46 PM

Thanks for reporting this bug. We've already fixed it, and the fix will appear in VC11. We're also looking into releasing the fix for VC10.

If you have any further questions, feel free to E-mail me at .

Stephan T. Lavavej
Visual C++ Libraries Developer
Posted by Microsoft on 9/12/2010 at 9:55 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by raic on 9/10/2010 at 5:51 AM
I've attached a demo project (hasn't shown up yet here). Simply open the project and hit ctrl+F5, the memory leaks will show up in the console window.
Posted by Microsoft on 9/9/2010 at 9:16 PM
Thanks for reporting this issue. In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

Please give us a demo project to demonstrate this issue so that we can conduct further research.

It would be greatly appreciated if you could provide us with that information as quickly as possible. If we do not hear back from you within 7 days, we will close this issue.

Thanks again for your efforts and we look forward to hearing from you.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 9/9/2010 at 5:03 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(