Yes, but when I click on the 'clean' button, Im unbinding and clearing out
the event, to avoid memory leak, but somehow the leak is still there.
When I click in the clean button, this code gets executed...
var p = $("#container").find("p");
p.unbind();
p.get(0).onclick = null;
$
The purpose of the bigString expando is just to create a huge object and make
it easier to spot that there's a memory leak.
Citrus wrote:
>
> I think that the reloadandbind call may be creating a closure that you're
> not intending. But, that's just me looking at the code for 5 minutes, I
> mi
Ethan Hannagan schrieb:
> Thanks for your reply. I downloaded the latest from SVN and built it, but I
> still have the same memory leak. Anyhow I still can't figure out where the
> memory leak is, I'm not sure if it's my code or jQuery.
I think it's because you have a circular reference here, crea
I think that the reloadandbind call may be creating a closure that you're
not intending. But, that's just me looking at the code for 5 minutes, I
might not be seeing it straight.
Also, it's a bad idea to stick custom js objects onto DOM objects -
specifically "bigString". It causes conflicts bet
Thanks for your reply. I downloaded the latest from SVN and built it, but I
still have the same memory leak. Anyhow I still can't figure out where the
memory leak is, I'm not sure if it's my code or jQuery.
Brandon Aaron wrote:
>
> Please grab the latest from SVN as it fixes the memory leak in
Please grab the latest from SVN as it fixes the memory leak in IE.
--
Brandon Aaron
On 12/11/06, Ethan Hannagan <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Can you help me spot what is causing the memory leak in the following code?
>
> If I click "reload", "bind", and "clean" several times, the memory
That appears to take care of it. Thanks for the pointer!
--- Brandon Aaron <[EMAIL PROTECTED]> wrote:
> On 12/7/06, Jeff Ober <[EMAIL PROTECTED]> wrote:
> > Version 1.0.3. Also, yahoo rewrote my syntax there a bit - those yes/no
> links
> > should actually be written out:
>
> I'm having troubl
Thanks for pointing that out. It doesn't seem to make a difference, though,
when I take it out. The dom objects are still getting left behind.
--- Klaus Hartl <[EMAIL PROTECTED]> wrote:
> Jeff Ober schrieb:
> > Version 1.0.3. Also, yahoo rewrote my syntax there a bit - those yes/no
> links
> >
On 12/7/06, Jeff Ober <[EMAIL PROTECTED]> wrote:
> Version 1.0.3. Also, yahoo rewrote my syntax there a bit - those yes/no links
> should actually be written out:
I'm having trouble remembering now but I believe a memory leak was
introduced in 1.0.3 and the latest in SVN should resolve this. Can
Jeff Ober schrieb:
> Version 1.0.3. Also, yahoo rewrote my syntax there a bit - those yes/no links
> should actually be written out:
>
> $('#question').append($('Yes / id="no" href="#" class="answer">No'));
>
> ...hopefully that won't get rewritten :)
There's a redundant jQuery object...:
$(
Daggone it. One more try:
$('#question').append($('Yes / No'));
--- Jeff Ober <[EMAIL PROTECTED]> wrote:
> Version 1.0.3. Also, yahoo rewrote my syntax there a bit - those yes/no
> links
> should actually be written
Version 1.0.3. Also, yahoo rewrote my syntax there a bit - those yes/no links
should actually be written out:
$('#question').append($('Yes / No'));
...hopefully that won't get rewritten :)
Jeff
--- Brandon Aaron <[EMAIL PROTECTED]> wrote:
> Which version/revision of jQuery are you using?
>
>
Which version/revision of jQuery are you using?
--
Brandon Aaron
On 12/7/06, Jeff Ober <[EMAIL PROTECTED]> wrote:
> I'm getting a memory leak in this function, which iterates over a series of
> items in the object allSections, showing a question set in the object and a
> yes/no answer, which then
13 matches
Mail list logo
