blocks|key|267795|text|这意味着在您的代码中的某个地方，您正在调用一个函数，而该函数又调用另一个函数，依此类推，直到您达到调用堆栈限制。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|267796|这几乎总是因为一个具有基本情况的递归函数没有得到满足。|267797|查看堆栈|267798|考虑下面的代码。|267799|(function+a()+{
++++a();
})();|code-block|syntax|javascript|267800|下面是经过几次调用后的堆栈...|267801|​|267802|📷|atomic|offset|length|267803|267804|正如您所看到的，调用堆栈不断增长，直到达到一个限制:浏览器硬编码的堆栈大小或内存耗尽。|267805|为了修复它，请确保您的递归函数具有能够满足的基本情况……|267806|(function+a(x)+{
++++//+The+following+condition+
++++//+is+the+base+case.
++++if+(+!+x)+{
++++++++return;
++++}
++++a(--x);
})(10);|267807|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/ba6ccfa84b94677d33c14e0ea16d87dd.png|imageAlt^0|0|0|0|0|0|0|0|0|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1C|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1D|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1E|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|1F|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1G|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1H|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|1I|8|@]|9|@$T|1J|U|1K|1|1L]]|A|$]]|$1|V|3|P|5|6|7|1M|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1N|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1O|8|@]|9|@]|A|$]]|$1|10|3|11|5|J|7|1P|8|@]|9|@]|A|$K|L]]|$1|12|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19|1A|-4]]]]

It means that somewhere in your code, you are calling a function which in turn calls another function and so forth, until you hit the call stack limit.
This is almost always because of a recursive function with a base case that isn't being met.
<h3>Viewing the stack</h3>
Consider this code...
<pre><code>(function a() {
 a();
})();
</code></pre>
Here is the stack after a handful of calls...
<img src="https://i.stack.imgur.com/aSwnu.png" alt="Web Inspector" />
As you can see, the call stack grows until it hits a limit: the browser hardcoded stack size or memory exhaustion.
In order to fix it, ensure that your recursive function has a base case which is able to be met...
<pre><code>(function a(x) {
 // The following condition 
 // is the base case.
 if ( ! x) {
 return;
 }
 a(--x);
})(10);
</code></pre>

blocks|key|3178478|text|如果你不小心导入/嵌入了同一个JavaScript文件两次，你有时会得到这个错误，值得在检查器的资源标签中查看一下。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3178479|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You can sometimes get this if you accidentally import/embed the same JavaScript file twice, worth checking in your resources tab of the inspector.

blocks|key|2964834|text|在我的例子中，我发送的是输入元素，而不是它们的值：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2964835|$.post(+'',{+registerName:+$('#registerName')+}+)|code-block|syntax|javascript|2964836|而不是：|2964837|$.post(+'',{+registerName:+$('#registerName').val()+}+)|2964838|这冻结了我的Chrome标签，当页面变得没有响应时，它甚至没有显示‘等待/杀死’对话框。|2964839|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

In my case, I was sending input elements instead of their values:

<pre><code>$.post( '',{ registerName: $('#registerName') } )
</code></pre>

Instead of:

<pre><code>$.post( '',{ registerName: $('#registerName').val() } )
</code></pre>

This froze my Chrome tab to a point it didn't even show me the 'Wait/Kill' dialog for when the page became unresponsive...

blocks|key|3178384|text|在代码中的某个地方有一个递归循环(例如，一个函数最终一次又一次地调用自己，直到堆栈被填满)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3178385|其他浏览器要么有更大的堆栈(所以你会得到一个超时)，要么因为某种原因(可能是一个放置不当的try-catch)吞下了错误。|3178386|发生错误时，使用调试器检查调用堆栈。|3178387|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

There is a recursive loop somewhere in your code (i.e. a function that eventually calls itself again and again until the stack is full).

Other browsers either have bigger stacks (so you get a timeout instead) or they swallow the error for some reason (maybe a badly placed try-catch).

Use the debugger to check the call stack when the error happens.

blocks|key|3178732|text|检测堆栈溢出的问题是，有时堆栈跟踪会展开，您将无法看到实际发生的情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3178733|我发现Chrome的一些新的调试工具在这方面很有用。|3178734|点击Performance+tab，确保启用了Javascript+samples，你就会得到类似这样的东西。|offset|length|style|CODE|3178735|这是非常明显的溢出在这里！如果单击extendObject，您将能够实际看到代码中的确切行号。|3178736|​|3178737|📷|atomic|3178738|3178739|您还可以看到可能有帮助或没有帮助的时间安排，或者是转移注意力的问题。|3178740|3178741|3178742|3178743|3178744|如果您实际上找不到问题，另一个有用的技巧是将大量console.log语句放在您认为问题所在的位置。上面的上一步可以帮助你做到这一点。|3178745|在Chrome中，如果你重复输出相同的数据，它会像这样显示出来，更清楚地显示出问题所在。在这种情况下，堆栈在最终崩溃之前达到了7152帧：|3178746|3178747|3178748|3178749|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/9e282a31d2e05d2bee9092d16d281f5e.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/c067db15db74001b356f57c16919842e.png|2|https://ask.qcloudimg.com/http-save/yehe-900000/fbbecdbd5be8a14b4edee6f7d52cf4e8.png^0|0|0|2|F|N|I|0|H|C|0|0|0|1|0|0|0|0|0|0|1|1|0|0|0|O|B|0|0|0|0|1|2|0|0^^$0|@$1|2|3|4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1J|8|@$F|1K|G|1L|H|I]|$F|1M|G|1N|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1O|8|@$F|1P|G|1Q|H|I]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1R|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|1S|8|@]|9|@$F|1T|G|1U|1|1V]]|A|$]]|$1|Q|3|M|5|6|7|1W|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1X|8|@]|9|@]|A|$]]|$1|T|3|M|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|U|3|O|5|P|7|1Z|8|@]|9|@$F|20|G|21|1|22]]|A|$]]|$1|V|3|M|5|6|7|23|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|24|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|25|8|@$F|26|G|27|H|I]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|28|8|@]|9|@]|A|$]]|$1|11|3|M|5|6|7|29|8|@]|9|@]|A|$]]|$1|12|3|O|5|P|7|2A|8|@]|9|@$F|2B|G|2C|1|2D]]|A|$]]|$1|13|3|M|5|6|7|2E|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|2F|8|@]|9|@]|A|$]]]|15|$16|$5|17|18|19|A|$1A|1B|1C|-4]]|1D|$5|17|18|19|A|$1A|1E|1C|-4]]|1F|$5|17|18|19|A|$1A|1G|1C|-4]]]]

The problem with detecting stackoverflows is sometimes the stack trace will unwind and you won't be able to see what's actually going on.

I've found some of Chrome's newer debugging tools useful for this.

Hit the <code>Performance tab</code>, make sure <code>Javascript samples</code> are enabled and you'll get something like this.

It's pretty obvious where the overflow is here! If you click on <code>extendObject</code> you'll be able to actually see the exact line number in the code. 

<a href="https://i.stack.imgur.com/qtrDa.png" rel="noreferrer"><img src="https://i.stack.imgur.com/qtrDa.png" alt="enter image description here"></a>

You can also see timings which may or may not be helpful or a red herring.

<a href="https://i.stack.imgur.com/sGnvq.png" rel="noreferrer"><img src="https://i.stack.imgur.com/sGnvq.png" alt="enter image description here"></a>

<hr>

Another useful trick if you can't actually find the problem is to put lots of <code>console.log</code> statements where you think the problem is. The previous step above can help you with this.

In Chrome if you repeatedly output identical data it will display it like this showing where the problem is more clearly. In this instance the stack hit 7152 frames before it finally crashed:

<a href="https://i.stack.imgur.com/8wVYn.png" rel="noreferrer"><img src="https://i.stack.imgur.com/8wVYn.png" alt="enter image description here"></a>

blocks|key|271286|text|在我的例子中，我使用以下代码将一个大的字节数组转换为一个字符串：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|271287|String.fromCharCode.apply(null,+new+Uint16Array(bytes))|code-block|syntax|javascript|271288|bytes包含数百万个条目，太大了，无法放入堆栈。|offset|length|style|CODE|271289|entityMap^0|0|0|0|5|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

In my case, I was converting a large byte array into a string using the following:

<pre><code>String.fromCharCode.apply(null, new Uint16Array(bytes))
</code></pre>

<code>bytes</code> contained several million entries, which is too big to fit on the stack.

blocks|key|2964902|text|在我的例子中，单击事件在子元素上传播。因此，我不得不写下以下内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2964903|2964904|+e.stopPropagation()|blockquote|2964905|2964906|2964907|单击事件时：|2964908|+$(document).on("click",+".remove-discount-button",+function+(e)+{
+++++++++++e.stopPropagation();
+++++++++++//some+code
++++++++});
+$(document).on("click",+".current-code",+function+()+{
+++++$('.remove-discount-button').trigger("click");
+});|code-block|syntax|javascript|2964909|下面是html代码：|2964910|+<div+class="current-code">++++++++++++++++++++++++++++++++++++++
++++++<input+type="submit"+name="removediscountcouponcode"+value="
title="Remove"+class="remove-discount-button">
+++</div>|2964911|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|W|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|10|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|11|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|12|8|@]|9|@]|A|$M|N]]|$1|S|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|T|$]]

In my case, click event was propagating on child element. So, I had to put the following:

<blockquote>
 e.stopPropagation()
</blockquote>

on click event:

<pre><code> $(document).on("click", ".remove-discount-button", function (e) {
 e.stopPropagation();
 //some code
 });
 $(document).on("click", ".current-code", function () {
 $('.remove-discount-button').trigger("click");
 });
</code></pre>

Here is the html code:

<pre><code> &lt;div class="current-code"&gt; 
 &lt;input type="submit" name="removediscountcouponcode" value="
title="Remove" class="remove-discount-button"&gt;
 &lt;/div&gt;
</code></pre>

blocks|key|2964715|text|在Chrome+dev工具栏控制台中查看错误详细信息，这将为您提供调用堆栈中的函数，并引导您指向导致错误的递归。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2964716|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Check the error details in the Chrome dev toolbar console, this will give you the functions in the call stack, and guide you towards the recursion that's causing the error.

blocks|key|265628|text|如果您出于某种原因需要无限进程/递归运行，您可以在单独的线程中使用webworker。http://www.html5rocks.com/en/tutorials/workers/basics/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|265629|如果要操作dom元素并重绘，请使用动画http://creativejs.com/resources/requestanimationframe/。|265630|entityMap|0|LINK|mutability|MUTABLE|url|http://www.html5rocks.com/en/tutorials/workers/basics/|1|http://creativejs.com/resources/requestanimationframe/^0|17|1I|0|0|J|1I|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

If you need a infinite process/recursion running for some reason, you can use a webworker in a seperate thread.
<a href="http://www.html5rocks.com/en/tutorials/workers/basics/" rel="noreferrer">http://www.html5rocks.com/en/tutorials/workers/basics/</a>

if you want to manipulate dom elements and redraw, use animation
<a href="http://creativejs.com/resources/requestanimationframe/" rel="noreferrer">http://creativejs.com/resources/requestanimationframe/</a>

blocks|key|2965071|text|这也可能导致Maximum+call+stack+size+exceeded错误：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2965072|var+items+=+[];
[].push.apply(items,+new+Array(1000000));+//Bad|code-block|syntax|javascript|2965073|这里也一样：|2965074|items.push(...new+Array(1000000));+//Bad|2965075|从Mozilla+Docs|2965076|2965077|但要注意:使用这种方式应用时，可能会超出JavaScript引擎的参数长度限制。使用太多参数(假设参数超过数万)的函数的后果因引擎而异(JavaScriptCore的硬编码参数限制为65536)，因为限制(甚至是任何过大堆栈行为的本质)都是未指定的。一些引擎会抛出异常。更有害的是，其他函数会任意限制实际传递给所应用函数的参数数量。为了说明后一种情况:如果这样的引擎有四个参数的限制(实际限制当然要高得多)，就好像在上面的示例中传递了参数5，6，2，3来应用，而不是整个数组。|blockquote|2965078|2965079|2965080|所以试试吧：|2965081|var+items+=+[];
var+newItems+=+new+Array(1000000);
for(var+i+=+0;+i+<+newItems.length;+i%2B%2B){
++items.push(newItems[i]);
}|2965082|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/apply^0|6|W|0|0|0|0|1|C|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1B|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1C|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|1D|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1E|8|@]|D|@$9|1F|A|1G|1|1H]]|E|$]]|$1|Q|3|-4|5|6|7|1I|8|@]|D|@]|E|$]]|$1|R|3|S|5|T|7|1J|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1K|8|@]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]|$1|W|3|X|5|6|7|1M|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|H|7|1N|8|@]|D|@]|E|$I|J]]|$1|10|3|-4|5|6|7|1O|8|@]|D|@]|E|$]]]|11|$12|$5|13|14|15|E|$16|17]]]]

This can also cause a <code>Maximum call stack size exceeded</code> error:

<pre><code>var items = [];
[].push.apply(items, new Array(1000000)); //Bad
</code></pre>

Same here:

<pre><code>items.push(...new Array(1000000)); //Bad
</code></pre>

From the <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/apply" rel="nofollow noreferrer">Mozilla Docs</a>:

<blockquote>
 But beware: in using apply this way, you run the risk of exceeding the
 JavaScript engine's argument length limit. The consequences of
 applying a function with too many arguments (think more than tens of
 thousands of arguments) vary across engines (JavaScriptCore has
 hard-coded argument limit of 65536), because the limit (indeed even
 the nature of any excessively-large-stack behavior) is unspecified.
 Some engines will throw an exception. More perniciously, others will
 arbitrarily limit the number of arguments actually passed to the
 applied function. To illustrate this latter case: if such an engine
 had a limit of four arguments (actual limits are of course
 significantly higher), it would be as if the arguments 5, 6, 2, 3 had
 been passed to apply in the examples above, rather than the full
 array.
</blockquote>

So try:

<pre><code>var items = [];
var newItems = new Array(1000000);
for(var i = 0; i &lt; newItems.length; i++){
 items.push(newItems[i]);
}
</code></pre>

blocks|key|268010|text|这里几乎每个答案都指出，这只能由无限循环引起。事实并非如此，否则您可能会通过深度嵌套的调用使堆栈溢出(这并不是说这是有效的，但它肯定在可能的范围内)。如果您可以控制JavaScript虚拟机，则可以调整堆栈大小。例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|268011|node+--stack-size=2000|offset|length|style|CODE|268012|另请参阅：How+can+I+increase+the+maximum+call+stack+size+in+Node.js|268013|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/11332422/how-can-i-increase-the-maximum-call-stack-size-in-node-js^0|0|0|M|0|5|1L|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

Nearly every answer here states that this can only be caused by an infinite loop. That's not true, you could otherwise over-run the stack through deeply nested calls (not to say that's efficient, but it's certainly in the realm of possible). If you have control of your JavaScript VM, you can adjust the stack size. For example:

<code>node --stack-size=2000</code>

See also: <a href="https://stackoverflow.com/questions/11332422/how-can-i-increase-the-maximum-call-stack-size-in-node-js">How can I increase the maximum call stack size in Node.js</a>

blocks|key|269479|text|我们最近添加了一个字段到一个管理网站，我们正在工作-+contact_type...很简单，对吧？好吧，如果你调用select+"type“，并试图通过jquery+ajax调用发送它，它会失败，因为这个错误隐藏在jquery.js中。不要这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|269480|$.ajax({
++++dataType:+"json",
++++type:+"POST",
++++url:+"/some_function.php",
++++data:+{+contact_uid:contact_uid,+type:type+}
});|code-block|syntax|javascript|269481|问题是type:type+-我相信是我们将参数命名为"+type“-拥有一个名为type的值变量不是问题。我们将其更改为：|269482|$.ajax({
++++dataType:+"json",
++++type:+"POST",
++++url:+"/some_function.php",
++++data:+{+contact_uid:contact_uid,+contact_type:type+}
});|269483|并相应地重写了some_function.php+-问题解决了。|269484|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

We recently added a field to an admin site we are working on - contact_type... easy right? Well, if you call the select "type" and try to send that through a jquery ajax call it fails with this error buried deep in jquery.js Don't do this:

<pre><code>$.ajax({
 dataType: "json",
 type: "POST",
 url: "/some_function.php",
 data: { contact_uid:contact_uid, type:type }
});
</code></pre>

The problem is that type:type - I believe it is us naming the argument "type" - having a value variable named type isn't the problem. We changed this to:

<pre><code>$.ajax({
 dataType: "json",
 type: "POST",
 url: "/some_function.php",
 data: { contact_uid:contact_uid, contact_type:type }
});
</code></pre>

And rewrote some_function.php accordingly - problem solved.

blocks|key|2964856|text|在我的例子中，两个jQuery模态显示堆叠在一起。阻止它解决了我的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2964857|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, two jQuery modals were showing stacked on top of each other. Preventing that solved my problem.

blocks|key|2965091|text|对于作为TypeScript初学者的我来说，这是_var1的getter和setter的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2965092|class+Point2{
++++
++++constructor(private+_var1?:+number,+private+y?:+number){}

++++set+var1(num:+number){
++++++++this._var1+=+num++//+problem+was+here,+it+was+this.var1+=+num
++++}
++++get+var1(){
++++++++return+this._var1+//+this+was+return+this.var1
++++}
}|code-block|syntax|javascript|2965093|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

For me as a beginner in TypeScript, it was a problem in the getter and the setter of _var1.
<pre><code>class Point2{
 
 constructor(private _var1?: number, private y?: number){}

 set var1(num: number){
 this._var1 = num // problem was here, it was this.var1 = num
 }
 get var1(){
 return this._var1 // this was return this.var1
 }
}
</code></pre>

blocks|key|268020|text|在我的例子中，我基本上忘记了获取input的value。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|268021|错误的|BOLD|268022|let+name=document.getElementById('name');
param={"name":name}|code-block|syntax|javascript|268023|正确的|268024|let+name=document.getElementById('name').value;
param={"name":name}|268025|entityMap^0|G|5|M|5|0|0|3|0|0|0|3|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Y|8|@$9|Z|A|10|B|H]]|D|@]|E|$]]|$1|I|3|J|5|K|7|11|8|@]|D|@]|E|$L|M]]|$1|N|3|O|5|6|7|12|8|@$9|13|A|14|B|H]]|D|@]|E|$]]|$1|P|3|Q|5|K|7|15|8|@]|D|@]|E|$L|M]]|$1|R|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|S|$]]

In my case, I basically forget to get the <code>value</code> of <code>input</code>.
Wrong
<pre><code>let name=document.getElementById('name');
param={&quot;name&quot;:name}
</code></pre>
Correct
<pre><code>let name=document.getElementById('name').value;
param={&quot;name&quot;:name}
</code></pre>

blocks|key|271195|text|下面两个相同代码的调用都可以在我的电脑上的Chrome32中工作，例如17905和17904。如果按原样运行，它们将产生错误"RangeError:超出最大调用堆栈大小“。这一限制似乎不是硬编码的，而是取决于您的机器的硬件。看起来，如果作为函数调用，这种自我施加的限制比作为方法调用时要高，也就是说，当作为函数调用时，这个特定的代码使用更少的内存。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|271196|作为方法调用：|271197|var+ninja+=+{
++++chirp:+function(n)+{
++++++++return+n+>+1+?+ninja.chirp(n-1)+%2B+"-chirp"+:+"chirp";
++++}
};

ninja.chirp(17905);|code-block|syntax|javascript|271198|作为函数调用：|271199|function+chirp(n)+{
++++return+n+>+1+?+chirp(+n+-+1+)+%2B+"-chirp"+:+"chirp";
}

chirp(20889);|271200|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Both invocations of the identical code below if decreased by 1 work in Chrome 32 on my computer e.g. 17905 vs 17904. If run as is they will produce the error "RangeError: Maximum call stack size exceeded". It appears to be this limit is not hardcoded but dependant on the hardware of your machine. It does appear that if invoked as a function this self-imposed limit is higher than if invoked as a method i.e. this particular code uses less memory when invoked as a function.

Invoked as a method:

<pre><code>var ninja = {
 chirp: function(n) {
 return n &gt; 1 ? ninja.chirp(n-1) + "-chirp" : "chirp";
 }
};

ninja.chirp(17905);
</code></pre>

Invoked as a function:

<pre><code>function chirp(n) {
 return n &gt; 1 ? chirp( n - 1 ) + "-chirp" : "chirp";
}

chirp(20889);
</code></pre>

blocks|key|269437|text|我在这里也遇到过类似的问题，就是使用下拉logo上载框上传logo时的详细信息|type|unstyled|depth|inlineStyleRanges|entityRanges|data|269438|<div>
++++++<div+class="uploader+greyLogoBox"+id="uploader"+flex="64"+onclick="$('#filePhoto').click()">
++++++++<img+id="imageBox"+src="{{+$ctrl.companyLogoUrl+}}"+alt=""/>
++++++++<input+type="file"+name="userprofile_picture"++id="filePhoto"+ngf-select="$ctrl.createUploadLogoRequest()"/>
++++++++<md-icon+ng-if="!$ctrl.isLogoPresent"+class="upload-icon"+md-font-set="material-icons">cloud_upload</md-icon>
++++++++<div+ng-if="!$ctrl.isLogoPresent"+class="text">Drag+and+drop+a+file+here,+or+click+to+upload</div>
++++++</div>
++++++<script+type="text/javascript">
++++++++++var+imageLoader+=+document.getElementById('filePhoto');
++++++++++imageLoader.addEventListener('change',+handleImage,+false);

++++++++++function+handleImage(e)+{
++++++++++++++var+reader+=+new+FileReader();
++++++++++++++reader.onload+=+function+(event)+{

++++++++++++++++++$('.uploader+img').attr('src',event.target.result);
++++++++++++++}
++++++++++++++reader.readAsDataURL(e.target.files[0]);
++++++++++}
++++++</script>
++++++</div>|code-block|syntax|javascript|269439|CSS.css|269440|.uploader+{
++position:relative;
++overflow:hidden;
++height:100px;
++max-width:+75%25;
++margin:+auto;
++text-align:+center;

++img{
++++max-width:+464px;
++++max-height:+100px;
++++z-index:1;
++++border:none;
++}

++.drag-drop-zone+{
++++background:+rgba(0,+0,+0,+0.04);
++++border:+1px+solid+rgba(0,+0,+0,+0.12);
++++padding:+32px;
++}
}

.uploader+img{
++max-width:+464px;
++max-height:+100px;
++z-index:1;
++border:none;
}



.greyLogoBox+{
++width:+100%25;
++background:+#EBEBEB;
++border:+1px+solid+#D7D7D7;
++text-align:+center;
++height:+100px;
++padding-top:+22px;
++box-sizing:+border-box;
}


#filePhoto{
++position:absolute;
++width:464px;
++height:100px;
++left:0;
++top:0;
++z-index:2;
++opacity:0;
++cursor:pointer;
}|269441|在更正之前，我的代码是：|269442|function+handleImage(e)+{
++++++++++++++var+reader+=+new+FileReader();
++++++++++++++reader.onload+=+function+(event)+{
++++++++++++++++++onclick="$('#filePhoto').click()"
++++++++++++++++++$('.uploader+img').attr('src',event.target.result);
++++++++++++++}
++++++++++++++reader.readAsDataURL(e.target.files[0]);
++++++++++}|269443|控制台中的错误：|269444|​|269445|📷|atomic|offset|length|269446|269447|我通过从div标签中删除onclick="$('#filePhoto').click()"解决了这个问题。|style|CODE|269448|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/4c9ab6fefb8bf14b525a47aeae20f18e.png|imageAlt^0|0|0|0|0|0|0|0|0|0|1|0|0|0|C|X|0^^$0|@$1|2|3|4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1C|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1D|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|1E|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|1F|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|1G|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|1H|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1I|8|@]|9|@]|A|$]]|$1|S|3|T|5|U|7|1J|8|@]|9|@$V|1K|W|1L|1|1M]]|A|$]]|$1|X|3|R|5|6|7|1N|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1O|8|@$V|1P|W|1Q|10|11]]|9|@]|A|$]]|$1|12|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19|1A|-4]]]]

I also faced similar issue here is the details
 when uploading logo using dropdown logo upload box

<pre><code>&lt;div&gt;
 &lt;div class="uploader greyLogoBox" id="uploader" flex="64" onclick="$('#filePhoto').click()"&gt;
 &lt;img id="imageBox" src="{{ $ctrl.companyLogoUrl }}" alt=""/&gt;
 &lt;input type="file" name="userprofile_picture" id="filePhoto" ngf-select="$ctrl.createUploadLogoRequest()"/&gt;
 &lt;md-icon ng-if="!$ctrl.isLogoPresent" class="upload-icon" md-font-set="material-icons"&gt;cloud_upload&lt;/md-icon&gt;
 &lt;div ng-if="!$ctrl.isLogoPresent" class="text"&gt;Drag and drop a file here, or click to upload&lt;/div&gt;
 &lt;/div&gt;
 &lt;script type="text/javascript"&gt;
 var imageLoader = document.getElementById('filePhoto');
 imageLoader.addEventListener('change', handleImage, false);

 function handleImage(e) {
 var reader = new FileReader();
 reader.onload = function (event) {

 $('.uploader img').attr('src',event.target.result);
 }
 reader.readAsDataURL(e.target.files[0]);
 }
 &lt;/script&gt;
 &lt;/div&gt;
</code></pre>

CSS.css

<pre><code>.uploader {
 position:relative;
 overflow:hidden;
 height:100px;
 max-width: 75%;
 margin: auto;
 text-align: center;

 img{
 max-width: 464px;
 max-height: 100px;
 z-index:1;
 border:none;
 }

 .drag-drop-zone {
 background: rgba(0, 0, 0, 0.04);
 border: 1px solid rgba(0, 0, 0, 0.12);
 padding: 32px;
 }
}

.uploader img{
 max-width: 464px;
 max-height: 100px;
 z-index:1;
 border:none;
}



.greyLogoBox {
 width: 100%;
 background: #EBEBEB;
 border: 1px solid #D7D7D7;
 text-align: center;
 height: 100px;
 padding-top: 22px;
 box-sizing: border-box;
}


#filePhoto{
 position:absolute;
 width:464px;
 height:100px;
 left:0;
 top:0;
 z-index:2;
 opacity:0;
 cursor:pointer;
}
</code></pre>

before correction my code was :

<pre><code>function handleImage(e) {
 var reader = new FileReader();
 reader.onload = function (event) {
 onclick="$('#filePhoto').click()"
 $('.uploader img').attr('src',event.target.result);
 }
 reader.readAsDataURL(e.target.files[0]);
 }
</code></pre>

The error in console: 

<a href="https://i.stack.imgur.com/ZbGVS.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ZbGVS.png" alt="enter image description here"></a>

I solved it by removing <code>onclick="$('#filePhoto').click()"</code> from div tag.

blocks|key|269450|text|我也遇到了同样的问题，我已经通过删除一个在ajax上使用了两次的字段名来解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|269451|++++jQuery.ajax({
++++url+:+'/search-result',
++++data+:+{
++++++searchField+:+searchField,
++++++searchFieldValue+:+searchField,
++++++nid++++:++nid,
++++++indexName+:+indexName,
++++++indexType+:+indexType
++++},
.....|code-block|syntax|javascript|269452|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I was facing same issue
I have resolved it by removing a field name which was used twice on ajax 
e.g

<pre><code> jQuery.ajax({
 url : '/search-result',
 data : {
 searchField : searchField,
 searchFieldValue : searchField,
 nid : nid,
 indexName : indexName,
 indexType : indexType
 },
.....
</code></pre>

blocks|key|271325|text|在我的例子中，问题是因为我的子路由与父路由具有相同的路径：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|271326|const+routes:+Routes+=+[
++{
++++path:+'',
++++component:+HomeComponent,
++++children:+[
++++++{+path:+'',+redirectTo:+'home',+pathMatch:+'prefix'+},
++++++{+path:+'home',+loadChildren:+'./home.module#HomeModule'+},
++++]
++}
];|code-block|syntax|javascript|271327|所以我不得不去掉了孩子路线的线路|271328|const+routes:+Routes+=+[
++{
++++path:+'',
++++component:+HomeComponent,
++++children:+[
++++++{+path:+'home',+loadChildren:+'./home.module#HomeModule'+},
++++]
++}
];|271329|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

The issue in my case is because I have children route with same path with the parent :

<pre><code>const routes: Routes = [
 {
 path: '',
 component: HomeComponent,
 children: [
 { path: '', redirectTo: 'home', pathMatch: 'prefix' },
 { path: 'home', loadChildren: './home.module#HomeModule' },
 ]
 }
];
</code></pre>

So I had to remove the line of the children route

<pre><code>const routes: Routes = [
 {
 path: '',
 component: HomeComponent,
 children: [
 { path: 'home', loadChildren: './home.module#HomeModule' },
 ]
 }
];
</code></pre>

blocks|key|271331|text|检查是否有调用自身的函数。例如|type|unstyled|depth|inlineStyleRanges|entityRanges|data|271332|export+default+class+DateUtils+{
++static+now+=+():+Date+=>+{
++++return+DateUtils.now()
++}
}|code-block|syntax|javascript|271333|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Check if you have a function that calls itself. For example 

<pre><code>export default class DateUtils {
 static now = (): Date =&gt; {
 return DateUtils.now()
 }
}
</code></pre>

blocks|key|3178845|text|dtTable.dataTable({
++++sDom:+"<'row'<'col-sm-6'l><'col-sm-6'f>r>t<'row'<'col-sm-6'i><'col-sm-6'p>>",
++++"processing":+true,
++++"serverSide":+true,
++++"order":+[[6,+"desc"]],
++++"columnDefs":+[
++++++++{className:+"text-right",+"targets":+[2,+3,+4,+5]}
++++],
++++"ajax":+{
++++++++"url":+"/dt",
++++++++"data":+function+(d)+{
++++++++++++d.loanRef+=+loanRef;
++++++++}
++++},
++++"fnRowCallback":+function+(nRow,+aData,+iDisplayIndex,+iDisplayIndexFull)+{
++++++++var+editButton+=+'';
++++++++//+The+number+of+columns+to+display+in+the+datatable
++++++++var+cols+=+8;
++++++++//+Th+row+element's+ID
++++++++var+id+=+aData[(cols+-+1)];
++++}
});|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|3178846|在上面的data函数中，我使用了相同的名称d.loanRef+=+loanRef，但是没有创建变量loanRef，因此递归地声明了它自己。|unstyled|offset|length|style|CODE|3178847|解决方案:声明一个loanRef变量，或者更好的方法是使用与d.loanRef上使用的名称不同的名称。|3178848|entityMap^0|0|4|4|L|J|1D|7|0|9|7|U|9|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|P|8|@$G|Q|H|R|I|J]|$G|S|H|T|I|J]|$G|U|H|V|I|J]]|9|@]|A|$]]|$1|K|3|L|5|F|7|W|8|@$G|X|H|Y|I|J]|$G|Z|H|10|I|J]]|9|@]|A|$]]|$1|M|3|-4|5|F|7|11|8|@]|9|@]|A|$]]]|N|$]]

<pre><code>dtTable.dataTable({
 sDom: &quot;&lt;'row'&lt;'col-sm-6'l&gt;&lt;'col-sm-6'f&gt;r&gt;t&lt;'row'&lt;'col-sm-6'i&gt;&lt;'col-sm-6'p&gt;&gt;&quot;,
 &quot;processing&quot;: true,
 &quot;serverSide&quot;: true,
 &quot;order&quot;: [[6, &quot;desc&quot;]],
 &quot;columnDefs&quot;: [
 {className: &quot;text-right&quot;, &quot;targets&quot;: [2, 3, 4, 5]}
 ],
 &quot;ajax&quot;: {
 &quot;url&quot;: &quot;/dt&quot;,
 &quot;data&quot;: function (d) {
 d.loanRef = loanRef;
 }
 },
 &quot;fnRowCallback&quot;: function (nRow, aData, iDisplayIndex, iDisplayIndexFull) {
 var editButton = '';
 // The number of columns to display in the datatable
 var cols = 8;
 // Th row element's ID
 var id = aData[(cols - 1)];
 }
});
</code></pre>
In the <code>data</code> function above, I used the same name <code>d.loanRef = loanRef</code> but had not created a variable <code>loanRef</code> therefore recursively declaring itself.
Solution: Declare a <code>loanRef</code> variable or better still, use a different name from the one used on <code>d.loanRef</code>.

blocks|key|271354|text|在我的例子中，我有两个同名的变量！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|271355|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, it was that I have 2 variables with the same name!

blocks|key|3178850|text|发送输入元素而不是它们的值很可能会像FK提到的那样解决这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3178851|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Sending input elements instead of their values will most likely resolve it like FK mentioned

blocks|key|2964819|text|您可以在crome浏览器中找到您的递归函数，按ctrl%2Bshift%2Bj，然后按源代码选项卡，这将为您提供代码编译流程，您可以在代码中找到使用断点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2964820|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

you can find your recursive function in crome browser,press ctrl+shift+j and then source tab, which gives you code compilation flow and you can find using break point in code.

blocks|key|269454|text|我知道这个帖子很老了，但我认为值得一提的是我发现这个问题的场景，这样它就可以帮助其他人。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|269455|假设您有如下嵌套元素：|269456|<a+href="#"+id="profile-avatar-picker">
++++<span+class="fa+fa-camera+fa-2x">
++++<input+id="avatar-file"+name="avatar-file"+type="file"+style="display:+none;"+/>
</a>|code-block|syntax|javascript|269457|您不能在其父元素的事件内操作子元素事件，因为它会传播到自身，进行递归调用，直到引发异常为止。|269458|所以这段代码将失败：|269459|$('#profile-avatar-picker').on('click',+(e)+=>+{
++++e.preventDefault();

++++$('#profilePictureFile').trigger("click");
});|269460|有两种方法可以避免这种情况：|269461|269462|将子元素移到父元素的外部。|unordered-list-item|269463|对子元素应用stopPropagation函数。|offset|length|269464|269465|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.mozilla.org/en-US/docs/Web/API/Event/stopPropagation^0|0|0|0|0|0|0|0|0|0|6|F|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|18|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|19|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|1A|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1B|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|1C|8|@]|9|@]|A|$G|H]]|$1|O|3|P|5|6|7|1D|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|R|3|S|5|T|7|1F|8|@]|9|@]|A|$]]|$1|U|3|V|5|T|7|1G|8|@]|9|@$W|1H|X|1I|1|1J]]|A|$]]|$1|Y|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|10|$11|$5|12|13|14|A|$15|16]]]]

I know this thread is old, but i think it's worth mentioning the scenario i found this problem so it can help others.

Suppose you have nested elements like this:

<pre><code>&lt;a href="#" id="profile-avatar-picker"&gt;
 &lt;span class="fa fa-camera fa-2x"&gt;&lt;/span&gt;
 &lt;input id="avatar-file" name="avatar-file" type="file" style="display: none;" /&gt;
&lt;/a&gt;
</code></pre>

You cannot manipulate the child element events inside the event of its parent because it propagates to itself, making recursive calls until the exception is throwed.

So this code will fail:

<pre><code>$('#profile-avatar-picker').on('click', (e) =&gt; {
 e.preventDefault();

 $('#profilePictureFile').trigger("click");
});
</code></pre>

You have two options to avoid this:

<ul>
<li>Move the child to the outside of the parent.</li>
<li>Apply <a href="https://developer.mozilla.org/en-US/docs/Web/API/Event/stopPropagation" rel="nofollow noreferrer">stopPropagation</a> function to the child element.</li>
</ul>

blocks|key|3178785|text|我出现这个错误是因为我有两个同名的JS函数|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3178786|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had this error because I had two JS Functions with the same name

blocks|key|2965048|text|如果您正在使用google+map，那么请检查传入new+google.maps.LatLng最新lng的格式是否正确。在我的例子中，它们是作为未定义的传递的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2965049|entityMap^0|P|M|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

If you are working with google maps, then check if the lat lng are being passed into <code>new google.maps.LatLng</code> are of a proper format. In my case they were being passed as undefined.

blocks|key|265788|text|有时会因为convert数据类型而发生，例如，你有一个你认为是字符串的对象。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|265789|以js客户端为例，nodejs中的socket.id不是字符串。要将其用作字符串，您必须在前面添加单词string：|265790|String(socket.id);|code-block|syntax|javascript|265791|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Sometimes happened because of convert data type , for example you have an object that you considered as string.

socket.id in nodejs either in js client as example, is not a string. to use it as string you have to add the word String before:

<pre><code>String(socket.id);
</code></pre>

blocks|key|269476|text|在我的例子中，我在ajax调用时得到了这个错误，并且我试图传递的变量的数据还没有定义，这显示了这个错误，但没有描述没有定义的变量。我添加了变量n取值的定义。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|269477|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

in my case I m getting this error on ajax call and the data I tried to pass that variable haven't defined, that is showing me this error but not describing that variable not defined. I added defined that variable n got value.

blocks|key|2965063|text|我试图给一个变量赋值，而那个变量还没有被声明。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2965064|声明变量修复了我的错误。|2965065|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I was trying to assign a variable, a value, when that variable had not been declared.

Declaring the variable fixed my error.

blocks|key|3178818|text|都遇到了同样的问题，找不到问题所在，开始责怪巴别塔;)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3178819|使代码在浏览器中不返回任何异常：|3178820|if+(typeof+document.body.onpointerdown+!==+('undefined'+%7C%7C+null))+{|code-block|syntax|javascript|3178821|问题创建错误%7C%7C+(或)部分，因为babel创建了自己的类型检查：|3178822|function+_typeof(obj){if(typeof+Symbol==="function"&&_typeof(Symbol.iterator)==="symbol")|3178823|所以移除|3178824|%7C%7C+null|3178825|让巴别塔转音起作用了。|3178826|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

Have come accross the same issue, coulnd't figured out what's wrong started blaming Babel ;)

Having code not returning any exception in browsers : 

<pre><code>if (typeof document.body.onpointerdown !== ('undefined' || null)) {
</code></pre>

issue was badly created || (or) part as babel creates its own type check:

<pre><code>function _typeof(obj){if(typeof Symbol==="function"&amp;&amp;_typeof(Symbol.iterator)==="symbol")
</code></pre>

so removing 

<pre><code>|| null
</code></pre>

made babel transpilation worked.

blocks|key|271344|text|在我的例子中，我错误地为val函数指定了相同的变量名"class_routine_id“|type|unstyled|depth|inlineStyleRanges|entityRanges|data|271345|var+class_routine_id+=+$("#class_routine_id").val(class_routine_id);|code-block|syntax|javascript|271346|它应该是这样的：|271347|+var+class_routine_id+=+$("#class_routine_id").val();+|271348|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

In my case 
I by mistake i have assigned same variable name , and to val function "class_routine_id" 

<pre><code>var class_routine_id = $("#class_routine_id").val(class_routine_id);
</code></pre>

it should be Like : 

<pre><code> var class_routine_id = $("#class_routine_id").val(); 
</code></pre>

blocks|key|2965087|text|在Angular中，如果您使用mat-select并具有400%2B选项，则可能会在https://github.com/angular/components/issues/12504中出现此错误|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2965088|你必须更新@angular/material版本|2965089|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/angular/components/issues/12504^0|14|1E|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

in Angular, if you're using mat-select and have 400+ options, this error may occur
<a href="https://github.com/angular/components/issues/12504" rel="nofollow noreferrer">https://github.com/angular/components/issues/12504</a>

you have to update @angular/material version

blocks|key|269486|text|我正在使用React-Native+0.61.5和(npm+6.9.0+&+node+10.16.1)|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|269487|当我在Project中安装任何新的库时，我得到了一个|269488|(例如，npm+install+@react-navigation/native+--save)|269489|超出最大调用堆栈大小错误|269490|为此，我试着|269491|sudo+npm缓存清理--强制|269492|(注意：-下面的命令通常需要1到2分钟的时间，这取决于您的npm缓存大小)|269493|entityMap^0|I|6|Q|O|0|0|0|2|A|0|0|0|G|0|K|H|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Y|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|13|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|S|$]]

I am using React-Native 0.61.5 along with (npm 6.9.0 &amp; node 10.16.1)

While I am install any new libraries in Project I got an of 

(e.g. npm install @react-navigation/native --save)

Maximum call stack size exceeded error

for that, I try 

sudo npm cache clean --force

(Note:- Below command usually take time 1 to 2 minutes
depending on your npm cache size)

blocks|key|3178842|text|当MongoDB数据库的模式和我们创建的模型不匹配时，我在express/nodejs应用程序中得到了这个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3178843|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I got this error in express/nodejs app, when the schema of MongoDB database and the models which we have created don't match.

I am using a Direct Web Remoting (DWR) JavaScript library file and am getting an error only in Safari (desktop and iPad)

It says 

<blockquote>
 Maximum call stack size exceeded.
</blockquote>

What exactly does this error mean and does it stop processing completely?

Also any fix for <code>Safari</code> browser (Actually on the <code>iPad Safari</code>, it says 

<blockquote>
 JS:execution exceeded timeout
</blockquote>

which I am assuming is the same call stack issue)

Maximum call stack size exceeded error

TypeScript

数据库

虚拟机

调试器

MongoDB

路由

jQuery

我使用的是Direct Web Remoting (DWR) JavaScript库文件，并且只在Safari (桌面和iPad)中遇到错误。上面写着超出了最大调用堆栈大小。这个错误到底是什么意思，它会完全停止处理吗？还有任何针对Safari浏览器的修复(实际上是在iPad Safari上，它说 JS:执行超时我假设这是相同的调用堆栈问题)

问超出最大调用堆栈大小错误
EN

回答 35

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问超出最大调用堆栈大小错误EN

回答 35

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问超出最大调用堆栈大小错误
EN