Something’s changed ever so slightly since I last ran into this error. Plus, there are some sweet new features coming out that I want to use! Have to spend some time trying to fix this now. It’s difficult to debug because it happens as soon as the server starts up and it’s not pointing to anything specific in my code. Has anyone seen it before? Any ideas what to do about it? api | GraphQL endpoint at /graphqlĪpi | 01:44:49 □ Server listening at api | RangeError: Maximum call stack size exceededĪpi | at rewireType | at rewireType | at rewireType | at rewireType | at rewireFields | at fields | at resolveObjMapThunk (/Users/tobbe/dev/redwood/acm-store-rw/node_modules/graphql/type/definition.js:504:40)Īpi | at defineFieldMap (/Users/tobbe/dev/redwood/acm-store-rw/node_modules/graphql/type/definition.js:760:20)Īpi | at GraphQLObjectType._fields (/Users/tobbe/dev/redwood/acm-store-rw/node_modules/graphql/type/definition.js:685:26)Īpi | at GraphQLObjectType.getFields (/Users/tobbe/dev/redwood/acm-store-rw/node_modules/graphql/type/definition.js:704:27)Īpi | at collectReferencedTypes (/Users/tobbe/dev/redwood/acm-store-rw/node_modules/graphql/type/schema.js:387:51)Īlso tried upgrading to RW 1.2.0 but still seeing the same error. In some programming languages this can be solved with tail call optimization, where the recursion call is transformed under the hood into a loop so no maximum stack size reached error exists.I just upgraded from RW 0.48 to v1.0.1 and when I run yarn rw dev api I get the following error. That’s when it’s useful to wrap your recursive function call into a. 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. It’s possible to cause infinite recursion in a fully promisified code, too. 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.īe considerate while calling functions, also dry run is the best practice to prevent them. 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. ‘Maximum call stack size Exceeded’ error. I am running Metabase 0.31.2ĭEPRECATED: metabase/redux/metadata fetchDatabaseMetadata I have a dashboard with 2 charts and whenever I open it, I am getting ‘Maximum call stack size Exceeded’ error.
0 Comments
Leave a Reply. |