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

[Bug]: Rivet screen blanks out; Uncaught RangeError: Maximum call stack size exceeded #411

Open
1 task done
jcobol opened this issue May 11, 2024 · 3 comments
Open
1 task done
Labels
bug Something isn't working

Comments

@jcobol
Copy link

jcobol commented May 11, 2024

What happened?

While using a project with 16 subgraphs for awhile during a single session, I've occasionally had the Rivet application screen go completely blank (gray) when right-clicking on the Graphs area to create a new Subgraph. After this, I cannot save the project or do anything with the UI.

In the F12 console, I found "Uncaught RangeError: Maximum call stack size exceeded".

What was the expected functionality?

UI should not go blank.

Describe your environment

Windows 11
Node v20.11.1
Rivet 1.7.12

Relevant log output

See attachment in next comment.

Relevant screenshots

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@jcobol jcobol added the bug Something isn't working label May 11, 2024
@jcobol
Copy link
Author

jcobol commented May 11, 2024

rivet-blank-screen-RangeError.log

Attached console log file.

@abrenneke
Copy link
Collaborator

This is really weird, I wish I had more to go on, if it's indeed that call stack error. If you can reliably reproduce this, can you possibly run rivet from source so that we get a better stack trace for that error?

@abrenneke
Copy link
Collaborator

It's possible that's a red herring and this is the local storage size limitation, too, but I don't see that in the logs...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants