Progress® Telerik® Test Studio® Feedback Portal
Back to Feed
Request a Feature Report a Bug
Completed
Last Updated: 15 Oct 2014 10:20 by ADMIN
ADMIN
Cody
Created on: 07 Feb 2013 00:24
Type: Bug Report
2
Appears to be a memory leak in VS plug-in opening and closing tests
After opening and closing tests in Visual Studio 2010, the memory use keeps climbing. Even closing the solution doesn't release the memory.
5 comments
ADMIN
Daniel Djambov
Posted on: 15 Oct 2014 10:20 
Telerik: opening and closing tests in Visual Studio performance improvement and memory leak for WPF tests has been implemented and will be available in our next internal product releas eplanned by the end of October 2014
ADMIN
Konstantin Petkov
Posted on: 08 Oct 2014 10:20 
Hi All,

Just an update about recent improvements in this areas (open/close tests performance in VS).

There have been a set of updates addressing memory leaks included in R3'14 release. Another portion of improvements is coming with next internal and official builds:
- Closing WPF tests memory leaks
- Open each test getting slower in large projects - this is related to Elements Explorer updates we actually don't need.

We will keep digging for improvements in the area.

Thanks!
ADMIN
Konstantin Petkov
Posted on: 17 Jul 2013 06:07 
Hi Ewin,

We have partial success with 2013 R1 however the complete solution will likely make it in the R1 Service Pack.

Thanks!
Ewin
Posted on: 16 Jul 2013 20:35 
Just out of curiousity, is this being addressed in 2013 r1?
Ewin
Posted on: 08 Mar 2013 18:53 
This also occurs in VS 2012
Create an account Log In
View
Type
Status