You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not an issue as such, just checking an assumption...
Because events are handled in Javascript and therefore subject to the node event loop and GC, we assume there is always a possible delay between event happening and Javascript handler executing, either because of a badly behaved script (eg. a Javascript timer that does significant work on each tick), or unexpected full GC in v8 itself.
Is this something the team has considered/experienced, and do you have any thoughts on it? It would obviously cause issues for any safety related functions that need to respond in a deterministic timeframe to an event.
Thanks
The text was updated successfully, but these errors were encountered:
This is not an issue as such, just checking an assumption...
Because events are handled in Javascript and therefore subject to the node event loop and GC, we assume there is always a possible delay between event happening and Javascript handler executing, either because of a badly behaved script (eg. a Javascript timer that does significant work on each tick), or unexpected full GC in v8 itself.
Is this something the team has considered/experienced, and do you have any thoughts on it? It would obviously cause issues for any safety related functions that need to respond in a deterministic timeframe to an event.
Thanks
The text was updated successfully, but these errors were encountered: