掲示板

Uncaught RangeError: Maximum call stack size exceeded with Bootstrap 3

9年前 に Chirdeep Tomar によって更新されました。

Uncaught RangeError: Maximum call stack size exceeded with Bootstrap 3

New Member 投稿: 7 参加年月日: 13/11/20 最新の投稿
I have an issue specifically when I use the Microblogs portlet. It works perfectly fine with the welcome / classic theme and the minute I change it to my theme and click in the textarea of the microblogging portlet the browser freezes for a bit and then throws the RangeError in the console.

Through debugging I have narrowed down the issue to when I @import url(bs3.css); in my custom.css in the diff folder.

I think that when I import bootstap3 css and subsequently the javascript accompanying it causes this error to happen but I am not sure.

Any help with this would be appreciated.

Thanks in advance
8年前 に juan meza によって更新されました。

RE: Uncaught RangeError: Maximum call stack size exceeded with Bootstrap 3

Regular Member 投稿: 228 参加年月日: 14/01/06 最新の投稿
did you ever solved this?
im having the same issue

thanks!
8年前 に George Gray によって更新されました。

RE: Uncaught RangeError: Maximum call stack size exceeded with Bootstrap 3

New Member 投稿: 4 参加年月日: 15/06/24 最新の投稿
Hi,
did anyone succeed in solving this problem?
8年前 に juan meza によって更新されました。

RE: Uncaught RangeError: Maximum call stack size exceeded with Bootstrap 3

Regular Member 投稿: 228 参加年月日: 14/01/06 最新の投稿
i did not, not yet... at the moment im not currently trying to solve it, since i will be the webmaster of the site... i will just change the theme to classic if i need to update the template (web content template in my case, with custom structure)... it works showing it, so its just the edit part...

i may be revisiting this issue in a couple of months tho
8年前 に George Gray によって更新されました。

RE: Uncaught RangeError: Maximum call stack size exceeded with Bootstrap 3

New Member 投稿: 4 参加年月日: 15/06/24 最新の投稿
I understand. Would you be so kind to post any updates if you find something?
Thanks anyway!
8年前 に juan meza によって更新されました。

RE: Uncaught RangeError: Maximum call stack size exceeded with Bootstrap 3

Regular Member 投稿: 228 参加年月日: 14/01/06 最新の投稿
of course, i always try to post answers when i find them emoticon

expect you to do the same emoticon
8年前 に George Gray によって更新されました。

RE: Uncaught RangeError: Maximum call stack size exceeded with Bootstrap 3

New Member 投稿: 4 参加年月日: 15/06/24 最新の投稿
Solution found! emoticon

There is a fix by Nate Cavanaugh at this link: AUI autosize deprecated infinit loop

Here you can find javascript code: AUI autosize deprecate FIX

It worked for me: now Microblogs portlet works perfectly
8年前 に juan meza によって更新されました。

RE: Uncaught RangeError: Maximum call stack size exceeded with Bootstrap 3

Regular Member 投稿: 228 参加年月日: 14/01/06 最新の投稿
great George!!

quick noob question, where is that file located?
and did you just replaced it?

thanks!
8年前 に George Gray によって更新されました。

RE: Uncaught RangeError: Maximum call stack size exceeded with Bootstrap 3

New Member 投稿: 4 参加年月日: 15/06/24 最新の投稿
You can find the file at the following location:

liferay-VERSION/tomcat-VERSION/webapps/ROOT/html/js/aui/aui-autosize-deprecated/aui-autosize-deprecated.js

I replaced it and restarted

Bye
thumbnail
6年前 に alex alex によって更新されました。

RE: Uncaught RangeError: Maximum call stack size exceeded with Bootstrap 3

New Member 投稿: 24 参加年月日: 17/02/15 最新の投稿
didn't found any solution for this until now emoticon
4年前 に Jefry Arch によって更新されました。

RE: Uncaught RangeError: Maximum call stack size exceeded with Bootstrap 3

New Member 投稿: 1 参加年月日: 20/04/13 最新の投稿
This error is almost always means you have a problem with recursion in JavaScript code, as there isn't any other way in JavaScript to consume lots of stack.  Sometimes calling a recursive function over and over again, causes the browser to send you Maximum call stack size exceeded error message as the memory that can be allocated for your use is not unlimited. It's possible to cause infinite recursion in a fully promisified code, too. That can happen if the promises in a chain don't actually perform any asynchronous execution , in which case control never really returns to the event loop, even though the code otherwise appears to be asynchronous. That's when it's useful to wrap your recursive function call into a -
setTimeout
setImmediate or
process.nextTick
Also, you can localize the issue by setting a breakpoint on RangeError type of exception , and then adjust the code appropriately. Moreover, you can managed to find the point that was causing the error by 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.
http://net-informations.com/js/err/range.htm