Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GraphQL voyager breaks with large schemas (only with mutations) #204

Open
Saud-Ahmad opened this issue Aug 12, 2021 · 6 comments
Open

GraphQL voyager breaks with large schemas (only with mutations) #204

Saud-Ahmad opened this issue Aug 12, 2021 · 6 comments

Comments

@Saud-Ahmad
Copy link

Saud-Ahmad commented Aug 12, 2021

When I try to switch queries to mutation GraphQL voyager with a schema that is about 400,000 lines long it breaks, (it just displays a blank screen). It seems though that this schema is just big enough to cause this issue. Can you fix this problem on online version ?

@Saud-Ahmad
Copy link
Author

When a schema loaded, Queries are fine

graph1

But when i switched to mutations

graph2

After few minutes display a blank screen

graph3

This is first time for me. I used this tool frequently, this is the best tool to understand and representation of GraphQL Schema. I have already put 200,000 lines of code but never got this error. Can you fix this online version of graphql voyager @IvanGoncharov ?

@Saud-Ahmad
Copy link
Author

Saud-Ahmad commented Aug 13, 2021

Now I open console when i switch to mutations and then blank screen occur, got error.

graph_error

@IvanGoncharov

@Saud-Ahmad
Copy link
Author

can you fix this error on online version @IvanGoncharov @RomanHotsiy @knidarkness ?

@orefalo
Copy link

orefalo commented Nov 30, 2021

the way I see it you have two options-

  • break your schema in subdomains
  • try with another browser/OS
  • increase your machine memory
    Would recommend closing - as this is not an issue.

@flexiblefactory
Copy link

We are also having this 'non-issue' ;) Is there a reason why ALLOW_MEMORY_GROWTH cannot be used? Can you point to the part of the project where this emscripten compilation is done?

@orefalo
Copy link

orefalo commented Dec 3, 2021

The issue seems to be coming from viz.js - it has a limit to 256mb.
Looks like this fork https://github.com/aduh95/viz.js would solve the issue. as it has support for ALLOW_MEMORY_GROWTH

Now I am not sure what it will take to reimplement voyager around it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants