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

Issue of Web.gl crashing the render process #14

Open
Lysodium opened this issue Feb 5, 2021 · 3 comments
Open

Issue of Web.gl crashing the render process #14

Lysodium opened this issue Feb 5, 2021 · 3 comments

Comments

@Lysodium
Copy link

Lysodium commented Feb 5, 2021

Currently I've been running a version really similar to the makehuman-example repository provided, and I've had issues where when making a constant amount of modifications to the body, the webpage will rapidly white-out and the model completely disappears from the screen. It occurs pretty consistently after 10-15 minutes, and has been recreated on the wassname example page. When refreshing the page, the plug-in no longer loads and it gives the error that "web.gl refused to connect". Any help would be great

Turning off the animations makes it take a bit longer, but the issue still occurs.

Crash_web gl

@wassname
Copy link
Member

wassname commented Feb 7, 2021

Turning off the animations makes it take a bit longer, but the issue still occurs.

Looks like i'ts a webgl memory leaks in the threejs webgl renderer. See here for where it's used. So you could try updating the threejs version from 0.84 to something newer (it's at 1.7 right now), that should be easy.

You could also try searching for "three js webgl memory leak" and follow the debugging and suggestions you find. I see some people remaking the webgl context periodidally, which would be a bit harder to implement, but at least there is lots of material online.

It's good to see you using it, I welcome pull requests BTW.

@Lysodium
Copy link
Author

Thanks for getting back to me so quickly. I've been messing around with different package versions of threejs, and it seems that after a certain version ~1.0.0 the file structure changes enough so that detector.js will return issues. It's just something I wanted to note incase you decide to revamp the repository. If I also find another workaround to the memory leaks, I'll also add an update.

@wassname
Copy link
Member

Good to know, thanks. Appreciate the updates

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

2 participants