9Rays.Net - Forums - .NET - FlyTreeView (ASP.NET) - Post#31882 - Previous version of FlyTreeView v4.0

Home - Forums-.NET - FlyTreeView (ASP.NET) - Previous version of FlyTreeView v4.0 - major memory leak

FlyTreeView (ASP.NET)

Technical support and KB related to the FlyTreeView control

This forum related to following products: FlyTreeView for ASP.NET

Previous version of FlyTreeView v4.0 - major memory leak

Link Posted: 03-Nov-2006 03:24

yzhitnit

Total Posts:0

Joined:11/23/2024

My team was in the process of upgrading our website. We realized that we start getting heavy memory leak on our web server. To find a problem two developers were working full time for two days to realize that the problem is coming from FlyTreeView control. We upgrade to latest version 4.1 and problem disappears. FlyTreeView control was holding reference to the Page. Page could not release reference to its objects. GC could not Dispose anything because of these references ( including FlyTreeView itself). One of the our web pages have a DataGrid control with a lot of data. We load its DataSource from DataSet, which could not be Disposed also. After 2 hours of work the Web Server was out of memory.

I recommend that if you experience the same issue you should upgrade to latest version. Problem is fixed there.

My recommendation to the FlyTreeView software Team: Please be more specific what was fixed when you release new version. And if there is a major issues don’t get Quiet. Let us know and we will deal with it. Otherwise we have to spend hours to figure this out.

Thanks.
Yuri.

Link Posted: 03-Nov-2006 03:44

yzhitnit

Total Posts:0

Joined:11/23/2024

You can download 14 days free trial ANTS Profiler™ - Code and memory profiling for .NET developers from http://www.red-gate.com and see how you using your application Pool memory.

Yuri.

Link Posted: 03-Nov-2006 08:09

EvgenyT

Total Posts:0

Joined:11/23/2024

[quote="yzhitnit"]My recommendation to the FlyTreeView software Team: Please be more specific what was fixed when you release new version. And if there is a major issues don’t get Quiet. Let us know and we will deal with it.

Thank you for your post.
Yuri, we didn't even know about this bug. The thing that fixes the issue is in optimization of some internal control code that refers to styles rendering. It was solved when this code was optimized and cleaned, its our luck that it also fixed a critical bug.

Thank you for your posts again.

Link Posted: 08-Jan-2007 04:09

epitka

Total Posts:0

Joined:11/23/2024

So was this an issue with 3.6 (.net 1.1 version), and has it been fixed in that version?

Link Posted: 08-Jan-2007 04:09

epitka

Total Posts:0

Joined:11/23/2024

So was this an issue with 3.6 (.net 1.1 version), and has it been fixed in that version?

Link Posted: 08-Jan-2007 04:27

yzhitnit

Total Posts:0

Joined:11/23/2024

I'm not sure. We never tested previous versions. But we never experience any problems using it. As soon as we upgraded to the version 4.x and released it in to production, only then we start getting unexpected server errors. By the time we discover the problem, 9Rays released a new version, which was OK according to our testing. As soon as we upgrade our software with it, all problems disappeared.

Link Posted: 08-Jan-2007 13:38

EvgenyT

Total Posts:0

Joined:11/23/2024

3.x versions do not have this bug since it do not use ASP.NET 2.0 styles registration feature.

The 4.x version contains a fix for the issue.