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

Deleting a graph will mess with Godot rendering #6

Closed
j20001970 opened this issue Apr 2, 2022 · 1 comment
Closed

Deleting a graph will mess with Godot rendering #6

j20001970 opened this issue Apr 2, 2022 · 1 comment

Comments

@j20001970
Copy link
Owner

Symptom: deleting a graph object will break Godot's rendering.

  • On desktop linux, it become unresponsive while other systems like audio are still working, but no error message observed in editor or stderr.
  • On Android, it's the same except the screen become blank and produced a EGL_BAD_DISPLAY error in logcat.

The current workaround is to not deleting the graph object, but definitively not the best way as every created graph will pile up memory usage and probably slow down performance until restart.

I have no idea how to further debugging this for now, probably require someone who is more experienced to troubleshoot the issue.

@j20001970
Copy link
Owner Author

The issue has been (kind of) fixed in 0e0175a by stopping the graph in a std::thread.
Although I have no idea why it would work and EGL_BAD_DISPLAY error still present on Android, now Godot's rendering still works after stopping a graph or even explicit deleting it, tested on both desktop Linux and Android, so the issue will be closed.

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

1 participant