You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have faced a similar issue where source location object utilised additional memory(about 150KB, 15% of schema object).
Any updates on the fix for this issue @andimarek
We are facing the same issue where out of 16 MB [Total size of GraphQL], nearly 2 MB is occupied by this SourceLocation objects. Kindly let me know if any solution is already released or in near future.
graphql.parser.ParserOptions#isCaptureSourceLocation can be set to false to stop the parser from creating SourceLocation objects. It's on by default but it can be turned off
Activity
[-]Rethink memory overhead of SourLocation [/-][+]Rethink memory overhead of SourceLocation [/+]deepakguruu commentedon May 5, 2021
We have faced a similar issue where source location object utilised additional memory(about 150KB, 15% of schema object).
Any updates on the fix for this issue @andimarek
thalapura-alapurom commentedon Nov 21, 2023
Hi
We are facing the same issue where out of 16 MB [Total size of GraphQL], nearly 2 MB is occupied by this
SourceLocation objects.Kindly let me know if any solution is already released or in near future.bbakerman commentedon Nov 23, 2023
graphql.parser.ParserOptions#isCaptureSourceLocationcan be set to false to stop the parser from creatingSourceLocationobjects. It's on by default but it can be turned offThis was added July 2021
thalapura-alapurom commentedon Nov 30, 2023
Thanks @bbakerman