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
With the 1.x version and the solution the README for 2, a child component can affect an autorun on a parent, which in my case caused a ton of subscriptions to get called, spiking CPU usage to 80%+ on an AWS general purpose medium instance with two people typing on a controlled component. I fixed this by first upgrading to 2.0, then taking the README solution for tracker and wrapping a nonreactive call around the call to onData.
With the 1.x version and the solution the README for 2, a child component can affect an autorun on a parent, which in my case caused a ton of subscriptions to get called, spiking CPU usage to 80%+ on an AWS general purpose medium instance with two people typing on a controlled component. I fixed this by first upgrading to 2.0, then taking the README solution for tracker and wrapping a nonreactive call around the call to onData.
The text was updated successfully, but these errors were encountered: