• Hi
    I have a problem with my wordpress site
    in this page i got this error:
    Uncaught RangeError: Maximum call stack size exceeded
    at RegExp.exec (<anonymous>)
    at RegExp.[Symbol.replace] (<anonymous>)
    at String.replace (<anonymous>)
    at Function.ea.matchesSelector (jquery-1.12.4-wp.js:2)
    at Function.n.filter (jquery-1.12.4-wp.js:2)
    at z (jquery-1.12.4-wp.js:2)
    at a.fn.init.is (jquery-1.12.4-wp.js:2)
    at Object.<anonymous> (c277e05225e0ddc4448aa137b5ab659c.js:104)
    at Function.each (jquery-1.12.4-wp.js:2)
    at lfb_checkConditions (c277e05225e0ddc4448aa137b5ab659c.js:104)

    how can i fix that?

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hey @naderi9,

    Have you tried temporarily switching off your plugins to see if the error goes away?

    Adding to @dvaer.

    @naderi9, I see that you are using an optimization plugin to minify and combine your CSS and JS. Request you to test the site after disabling at least that plugin.

    We would be able to see which specific plugin code is resulting in this error.

    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.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Uncaught RangeError: Maximum call stack size exceeded’ is closed to new replies.