-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Possible EventEmitter memory leak detected. 11 RoomMember.membership listeners added. #10456
Comments
|
@t3chguy Are you interested in working on this? |
Yup, will sort this tonight
wt., 30 lip 2019, 17:51 użytkownik J. Ryan Stinnett <
[email protected]> napisał:
… @t3chguy <https://github.com/t3chguy> Are you interested in working on
this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10456>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AASK2RHYOTNUMFQAK3W4XJLQCBWPXANCNFSM4IH6KOYQ>
.
|
This is super annoying to wire up, needs to be passed: |
I'm thinking a RoomContext which has all the useful calculated bits from RoomView would be super-useful |
A RoomContext sounds like the perfect answer for this, I think |
How stable are Contexts in React 15.6 though? I've only been using 16.8 recently |
We've had a matrix client context for the history of the project powering a good third of the app, so I'd hope stable enough. We also want to upgrade to React 16 any day now. |
<3 is that 16 or 16.8 (hooks)? |
it'll probably be "whatever is latest" at the time of upgrade, depending on who does it. Ideally we'd keep up with react releases... |
very exciting |
This is due to recent changes from matrix-org/matrix-react-sdk#3255.
It's not a leak in this case, but we are adding lots of listeners since every message now listens to the room for permissions changes, even though the user's permission state should be the same throughout the room.
I would suggest computing this permission info higher up so it happens once per room and passed down as props. This should help us leverage React's update cycle more naturally as well (it should update all components in one go, rather than each message updating separately due to having its own listeners).
The text was updated successfully, but these errors were encountered: