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
You can setMaxlisteners directly onto the store object yourself to prevent the error bubbling:
MyStore.setMaxlisteners(0);
but I'm not sure why we keep the default max listeners on stores, I guess it's quite useful to catch memory leaks from components not being unmounted or being unmounted incorrectly
I should have pointed out that I already fixed it the way that @tomatau described it.
But now I'm second-guessing the way I've structured my components, instead of having every GridItem listen to a Store, I should probably have the GridView listen to it and propagate the changes to the items via a property?
Anyhow, I can whip up a PR for the Store if you want.
Hi,
I was having an issue where node was complaining about a potential memory leak because too many listeners were being added for the same event.
I saw that this was fixed in Biff (FormidableLabs@04edf8a) but not in this repo.
Is there a particular reason for that? Could we apply the same fix here?
The text was updated successfully, but these errors were encountered: