Memory leak SF BO with DevExpress ASPxDataGridView

StrataFrame Forum

Back

Memory leak SF BO with DevExpress ASPxDataGridView

Author	Message
ChanKK	ChanKK posted 15 Years Ago Post Details Share Post
Group: Forum Members Posts: 190, Visits: 1.3K	Hi any update? Sorry it is show stopper for us.
	Reply Like 1
Ivan George Borges	Ivan George Borges posted 15 Years Ago Post Details Share Post
Group: StrataFrame MVPs Posts: 1.9K, Visits: 21K	Sorry Chan, not yet.
	Reply Like 1
ChanKK	ChanKK posted 15 Years Ago Post Details Share Post
Group: Forum Members Posts: 190, Visits: 1.3K	Hi Could you reproduce the memory leak issue? I need solution ASAP. Thank you
	Reply Like 1
Ivan George Borges	Ivan George Borges posted 15 Years Ago Post Details Share Post
Group: StrataFrame MVPs Posts: 1.9K, Visits: 21K	Got it. That is always a best practice on a disconnected scenario.
	Reply Like 1
ChanKK	ChanKK posted 15 Years Ago Post Details Share Post
Group: Forum Members Posts: 190, Visits: 1.3K	Ivan George Borges (10/20/2010) Were you able to hit the insufficient memory error? Hi, Beside of memory leak, we found that it utilize huge memory. We are in progress to add filtering and limit # of records to be retrieved from every query.
	Reply Like 1
Ivan George Borges	Ivan George Borges posted 15 Years Ago Post Details Share Post
Group: StrataFrame MVPs Posts: 1.9K, Visits: 21K	Hi Chan. Currently we are concerning about the memory usage since each page hold its own data/BO and not been released until session expired. It might cause memory insufficient issue. Were you able to hit the insufficient memory error? I have downloaded your sample and will alocate some time to have a look at it as soon as possible. Will let you know of my tests here once I have something. Cheers.
	Reply Like 1
ChanKK	ChanKK posted 15 Years Ago Post Details Share Post
Group: Forum Members Posts: 190, Visits: 1.3K	Hi Just would like to know if SF team able to reproduce it. Thank you
	Reply Like 2
ChanKK	ChanKK posted 15 Years Ago Post Details Share Post
Group: Forum Members Posts: 190, Visits: 1.3K	Trent L. Taylor (10/17/2010) Chan, I think that your logic is sound, it was just an observation. At this point I think that you have the web development with SF down anyway, so I wasn't concerned, just curious Any better way of doing this? Currently we are concerning about the memory usage since each page hold its own data/BO and not been released until session expired. It might cause memory insufficient issue. Beside, I have redo and attach new project, it connects to Northwind employees table. Just launch default.aspx, and keep refresh it (F5). I also included the SF dll that I am using. Please find the snapshot below I captured from memory profiler
	Reply Like 2
Trent Taylor	Trent Taylor posted 15 Years Ago Post Details Share Post
Group: StrataFrame Developers Posts: 6.6K, Visits: 7K	Chan, I think that your logic is sound, it was just an observation. At this point I think that you have the web development with SF down anyway, so I wasn't concerned, just curious
	Reply Like 2
ChanKK	ChanKK posted 15 Years Ago Post Details Share Post
Group: Forum Members Posts: 190, Visits: 1.3K	Hi, I will double check and send you correct DB later. One other thing I noticed is that this is not a StrataFrame wired web application. Clearly you can do this, but you may have Session issues, etc. since we wire things up through the ApplicationBasePage and the global.asax. I noticed that you created your own TestBasePage.cs....this is really not related to the issue, just an observation. I am following SF way to wire global.asax, just that I use this to do so that I can have common "BaseApplication" <%@ Application Inherits="Vfs.Testing.UI.Web.TestApplication" Language="C#" %> Regarding ApplicationBasePage, I am using seperate BasePage for each web form. It reason is we don't have to share same BOs among all forms. The reasons are: 1. We don't want to use unique BO property in each form for same BO. i.e. EmployeesBO in form A might contains difference data. If we use single ApplicationBasePage, the data might be "corrupted" by other form. 2. Also, we might have thread-safe issue need to take into account. Please advice if any issue with this design. Regarding SF dll, I have check the SF dll version in bin folder (deployment folder) and it shown 1.7.0.7. We compiled it via source code. Anyway, I will attach the SF dll together in next future Thank you
	Reply Like 2