I know what you're saying, unfortunately i can't share the code right
now.. I'll try and see if i can get it down to a small enough subset
that i could pass something along. I figured i would just put the
issue out there to see if anything obvious clicked for anyone. Not
surprising that it doesn't.

thanks.

On Apr 2, 1:43 pm, Ricardo <ricardob...@gmail.com> wrote:
> Sometimes when I flush my toilet the water takes longer to actually
> come down, I wonder if any of you guys know what could be the problem?
>
> j/k :)
>
> Do you have any code you are allowed to share? Start stripping the JS
> to the point where you only have the code necessary to cause the
> error, then you have an useful test-case.
>
> cheers,
> - ricardo
>
> On Apr 2, 3:33 pm, Matt Critchlow <matt.critch...@gmail.com> wrote:
>
> > I should add, sometimes IE gives a stack overflow notice also, but
> > again, not on every load() or history plugin pageload() call. In case
> > this triggers anything in anyone's mind. Thanks.
>
> > On Apr 2, 11:16 am, Matt Critchlow <matt.critch...@gmail.com> wrote:
>
> > > I am making a lot of use of jQuery's load method to replace my main
> > > content, then firing a callback function to either just bind some
> > > events or do an ajax call to load some data into the page(search
> > > results for example). I do this in the pageload function for the
> > > history plugin to manage everything. This all seems very normal and
> > > trivial to me though(for jQuery to handle), so I'm not sure it has
> > > anything to do with the issue..
>
> > > Thanks for sharing your experience too.
>
> > > On Apr 2, 11:10 am, Donny Kurnia <donnykur...@gmail.com> wrote:
>
> > > > Matt wrote:
> > > > > Hi All,
>
> > > > > I realize this is kind of vague, but I can't link to the site yet
> > > > > since we're still in development. I'm using the latest jquery, and the
> > > > > history plugin to dynamically load html into a "main" div section
> > > > > depending on user action. In Firebug, I sometimes notice 3 "too much
> > > > > recursion" messages, one in jquery, one in sizzle, and then one in
> > > > > firebug itself. Then in IE i actually get a message popup that says
> > > > > "Outofmemory". It's frustrating because it doesn't happen every
> > > > > time, and the site continues to function fine. This feels like a
> > > > >memoryleak to me, but I'm not sure how to dig into it. Does anyone
> > > > > know anything regarding how the history plugin with the latest version
> > > > > of jquery might introduce this?
>
> > > > > Thanks all,
>
> > > > > Matt
>
> > > > I got the same message in firebug. I'm only use Malsup's form plugins to
> > > > submit one form via ajax, and some code to load ajax data as json. I'm
> > > > still use jquery 1.2.6.
>
> > > > I never had this message before in old version of firebug. I wonder
> > > > whether this is firebug's bug, or something else.
>
> > > > --
> > > > Donny 
> > > > Kurniahttp://hantulab.blogspot.comhttp://www.plurk.com/user/donnykurnia

Reply via email to