Lightrun
question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"Maximum call stack size exceeded"

See original GitHub issue

Recursion bug on svelte > 3.6.6 when creating a component using client-side component API. To reproduce: https://svelte.dev/repl/6fbeea34d77f43b9a6d57e1da71668fc?version=3.6.7 This works on 3.5.4.

Error bundle.js:18532 Uncaught (in promise) RangeError: Maximum call stack size exceeded

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:11
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

4reactions
rob-balfrecommented, Jul 18, 2019

Hideous hack but works until a fix is released…

import { onMount, tick } from 'svelte';

onMount(async() => { 
    await tick();
    new RedChild({ target: document.body })
})

https://svelte.dev/repl/3692752c2bfc4c3f9292bdf84023f852?version=3.6.7

4reactions
prashantsailcommented, Jul 12, 2019

Was about to file a new issue, when I stumbled upon this one. My app worked fine until version 3.6.3, I am running into this issue since 3.6.4

My Observation

This issue occurs when you create a child component using client side api new Component(options) inside parent’s life cycle functions(like onMount, afterUpdate, etc)

Simple repro scenario

😃 https://svelte.dev/repl/d90c6f4e19594c28a4e454b5016570e2?version=3.6.3 🤕 https://svelte.dev/repl/d90c6f4e19594c28a4e454b5016570e2?version=3.6.4

Read more comments on GitHub >

github_iconTop Results From Across the Web

javascript - Maximum call stack size exceeded error
It means that somewhere in your code, you are calling a function which in turn calls another function and so forth, until you...
Read more >
JavaScript Error: Maximum Call Stack Size Exceeded
If you see the “Maximum Call Stack Size Exceeded” error, there's likely a problem with a recursive function within your JavaScript code.
Read more >
Uncaught RangeError: Maximum call ... - Net-Informations.Com
Maximum call stack size exceeded error ... This error is almost always means you have a problem with recursion in JavaScript code, as...
Read more >
RangeError: Maximum call stack size exceeded - Educative.io
The most common source for this error is infinite recursion. You must have a recursive function in your code whose base case is...
Read more >
Maximum Call Stack Size Exceeded (Typescript Error) - Medium
Scenario for Maximum Call Stack Size Exceeded Error ... In your code, the possibility is, You are calling a function that is calling...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found
Previous page

bind:files doesn't work on safari. But works in chrome

Next page

deleting object properties doesn't trigger a render