Hi Max,
   thanks for your help.

I ran sIEve and pointed it the homepage of my application.
It didn't detect any leak, but three cycle dependencies and an orphan. I
cannot post the output of the scan because it's humongous!
However, if I run "Auto-refresh" on my app for few seconds, I can see the
memory usage increasing linearly with increments between 380Kb and 1500Kb
per refresh. Meanwhile, the number of nodes used in the DOM never exceed 92.

At this point I suppose Trnidad is not leaking any memory, but somehow IE is
not releasing memory while navigating through the pages of my app. I don't
see this behaviour in IE if I "Auto-refresh" other websites (ex. google.com),
where the memory used by IE is stable.

I also have to correct my previous post: a deeper analysis shows me that
Firefox is deallocating the memory correctly while using my app (too bad my
client wants to use IE7).

I don't know if this problem is worthed a deeper investigation.

Thanks
Bye
Davide


On Thu, Mar 27, 2008 at 9:53 AM, Max Starets <[EMAIL PROTECTED]> wrote:

> Hi Davide,
>
> If Trinidad's Javascipt library  leaks memory when user navigates from
> page to page, it is not normal
> or acceptable. There are tools, such as "drip" and "sIEve" that van help
> us diagnose the problem.
>
> Regards,
> Max Starets
>
> Davide Bonicelli wrote:
> > Hi everybody,
> >     I'm developing an application based on Trinidad 1.0.7,
> > JSF-Facelets 1.1.14, Spring 2.5.2 and Hibernate 3.2.3ga running on
> > Tomcat 5.5.
> > I noticed that while navigating through the pages of the application,
> > the browser keep consuming more and more memory (both IE7 and Firefox
> > 2). Every time I visit a page (even one I already visited in the same
> > session), the memory used by the browser increases by about 1.5MB (I
> > monitored it with Sysinternal).
> > If I disable javascript in IE7 and load different pages of my
> > application, this behavior stops and the memory used by the browser is
> > stable, but logically the application doesn't work anymore.
> >
> > Is it normal that the browser consumes all this memory when using
> > Trinidad? Did anybody else experienced this problem?
> > I suppose the problem is connected with Common1_0_7.js.
> > My concern is that I had the browser eating up to 350MB of memory in a
> > session of less than an hour and I don't want to have problems related
> > with memory consumption when the application goes into production and
> > is used for 8 hours a day by a user.
> >
> > Thanks for your help
> > Bye
> > Davide
> >
>
>

Reply via email to