-
Notifications
You must be signed in to change notification settings - Fork 34
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
Implement "render function timeouts" to prevent a specific render function e.g. doInitial*
from running for more than a configurable 500ms
#348
Comments
|
/attempt #348 I'll give it a shot
|
@ShiboSoftwareDev I've been looking into this one for a bit, I think it's basically impossible w/o webworkers, I probably should have investigated more before bountying. Lmk if you come to a different conclusion!!! |
@anas-sarkez |
At this point I think this is mostly not possible (technically there is probably a solution but it's a dramatic architecture change), there is a version of this that is possible by considering the maximum execution time of effects, but imo we should basically do most of the freeze detection via webworkers |
This issue has been automatically marked as stale because it has had no recent activity. It will be closed if no further activity occurs. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
Emit an error "<trace ... />" took more than 500ms to execute
doInitialPcbComponentRender
/bounty $30
The text was updated successfully, but these errors were encountered: