-
Notifications
You must be signed in to change notification settings - Fork 21
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
I get indicates a memory leak in my application warning when implement React-netflix-player. #28
Comments
Hey @huy232 May you try with this new version 1.1.5? If the problem persist, send me your react version please. |
problem still persists with newest react version (v17). Possible solution is to do some cleanup in the useEffect hooks (for example reset all the states to default values) |
Hello @Lucasmg37 , I'm really sorry for my really really late reply, I've been busy and didn't see the notification up until now. So after a year, I returned to this player because I like it and want to know whether I still have this problem or not. But turn out I still have this problem. My React version is "react": "^17.0.2" To reproduce the situation:
I'm using the So when I go back to the information page or change the episode, it immediately fires a warning that I'm having a memory leak. Besides, after watching an episode for some period of time, let's say about 3-5 minutes, another warning that said there were I used some other players for my project and it still works fine, but when I switch to this, I have those problems, up until now. Hope you can read this. |
Have you found an alternative to this ? |
Hello, I have this warning only whenever I try to implement
<ReactNetflixPlayer src={myMp4FileState}/>
into my component, if I disable the React-netflix-player and switch to a standard HTML tag like:
the warning will disappear and everything is fine again, no more warning fire out, I've tested it a few times by disabling and enabling the React-netflix-player, so I think it's from the React-netflix-player, hope you can have a look, thanks.
For more specific, it's said:
The text was updated successfully, but these errors were encountered: