Michael, please try the 1.1.4 release to see if it resolves the memory
issues you were having.
--
Brandon Aaron
On 8/6/07, Brandon Aaron <[EMAIL PROTECTED]> wrote:
>
> Nothing yet Michael ...
>
> --
> Brandon Aaron
>
> On 8/6/07, Michael Schwarz [MVP] <[EMAIL PROTECTED] > wrote:
> >
> >
> > Any news about this topic?
> >
> > Michael
> >
> >
> > On Jul 24, 1:37 pm, "Brandon Aaron" < [EMAIL PROTECTED]> wrote:
> > > Thanks for the ticket Michael. Memory leaks are always a high
> > priority. You
> > > should see a fix for this show up in SVN soon.
> > >
> > > --
> > > Brandon Aaron
> > >
> > > On 7/24/07, Michael Schwarz [MVP] <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > >
> > >
> > >
> > > > Hi,
> > >
> > > > I added some months ago a ticket for memory problems, and as I found
> > > > it should be fixed already, but I'm still not sure if it is
> > correctly
> > > > fixed or if there is maybe a different way of doing the same. I have
> >
> > > > following JavaScript:
> > >
> > > > var h = [];
> > > > for(var i=0; i<20; i++) {
> > > > h.push("<button _idx=" + i + ">Button " + i + "</button>");
> > > > }
> > >
> > > > $("#display/button").unbind("click", onClick);
> > > > $("#display").html(h.join("<br/>"));
> > > > $("#display/button").bind("click", onClick);
> > >
> > > > If I run this several times memory will grow in IE7 (maybe in IE6,
> > > > too). When using the sIEve (http://home.wanadoo.nl/jsrosman/) I see
> > > > "#inUse" and "usage" growing.
> > >
> > > > So, what I'm still doing wrong (with the latest jQuery bits)?
> > >
> > > > What I found is that "delete this.global[type][index];" in
> > > > events.remove will set the object to undefined but will remain the
> > > > arrays length, maybe that is a problem, too.
> > >
> > > > I know that it is not a problem for short running Web pages, but if
> > > > you are creating a terminal application that is running 24hrs a day
> > > > you should be aware of this.
> > >
> > > > Michael- Hide quoted text -
> > >
> > > - Show quoted text -
> >
> >
>
