Side navigation
#5680 closed bug (invalid)
Opened December 19, 2009 10:36AM UTC
Closed June 13, 2010 07:14PM UTC
Last modified June 02, 2012 01:20AM UTC
RangeError: Maximum call stack size exceeded.
Reported by: | MathieuMa | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 1.4 |
Component: | unfiled | Version: | 1.4a1 |
Keywords: | Cc: | mathieuma@users.sourceforge.net | |
Blocked by: | Blocking: |
Description
I get the following error when using 1.4a2 with Safari on OSX :
The error occurs at line 1485 : proxy: function( fn, proxy, thisObject ) {
Plugins used on the page : JqueryUI (tabs, datepicker, dialog, core), autocomplete, and some custom code/plugins.
1.4a1 works as expected on Safari.
Attachments (0)
Change History (10)
Changed December 20, 2009 02:50AM UTC by comment:1
Changed June 13, 2010 07:14PM UTC by comment:2
resolution: | → invalid |
---|---|
status: | new → closed |
Pre-release bug?
Changed August 12, 2011 07:46PM UTC by comment:3
I just began getting this same error in Chrome 13.0.782.112 m and the latest jquery on the google repository.
The Chrome inspector is giving this error message:
Uncaught RangeError: Maximum call stack size exceeded jquery.min.js:16
It could be pretty hard to narrow it down to a test case...
Changed August 12, 2011 07:50PM UTC by comment:4
If it helps any the web page involved is http://www.parrocchiasanlino.org/index.php?mod=database, but you need specific user access to view the page...
Changed October 12, 2011 01:08AM UTC by comment:5
It happens to me in the UI's calendar when I write this code:
dates.not(this).datepicker("option", option, date);
Here's the full example:
var dates = $("#date_init, #date_end").datepicker( { firstDay: 1, onSelect: function( selectedDate ) { var option = this.id == "date_init" ? "minDate" : "maxDate", instance = $( this ).data( "datepicker" ), date = $.datepicker.parseDate( instance.settings.dateFormat || $.datepicker._defaults.dateFormat, selectedDate, instance.settings ); dates.not(this).datepicker("option", option, date); } });
Changed November 07, 2011 04:24PM UTC by comment:6
Why is this marked as closed? I'm still seeing this issue.
Changed November 07, 2011 04:28PM UTC by comment:7
We don't see it, because there was never a test case. Please provide a reduced test case.
Changed May 31, 2012 09:28AM UTC by comment:8
I have the same problem during an jquery replaceWith of an huge div element with another div of about 10 lines.
It can be reproduced, but it seems to be size dependent.
That makes it hard to provide a "reduced test case"
In my case is the threshold between 5MB and 8MB of HTML size.
Changed May 31, 2012 03:03PM UTC by comment:9
Replying to [comment:8 anonymous]:
I have the same problem during an jquery replaceWith of an huge div element with another div of about 10 lines. It can be reproduced, but it seems to be size dependent. That makes it hard to provide a "reduced test case" In my case is the threshold between 5MB and 8MB of HTML size.
I solved my problem by replacing the following statement:
element.replaceWith(val);
into
var parent = element.parent(); parent.empty(); parent.append(val);
element was the huge part of the HTML DOM
Changed June 02, 2012 01:20AM UTC by comment:10
In my case is the threshold between 5MB and 8MB of HTML size.
ಠ_ಠ
Can you narrow this down to a simple test case?