-
Notifications
You must be signed in to change notification settings - Fork 40
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
Crashing Chrome often. Memory leaks? #32
Comments
I have a lotta chrome extensions too |
I think this might have to do with the A-Player downloading all the mp3s prior to playing. This wouldn't be a problem with a few but the main view is a decently sized array of APlayers. If you really want the mp3 playable from the main view I think we'd want to not use the |
I think we should only have a single player like the mobile apps. That would be more performant and correspond with normal UX |
:) Agreed, and that's what this new branch is doing: https://github.com/SoftwareEngineeringDaily/sedaily-front-end/tree/global-player-WIP which is why it was odd since I think Jeff was having problems even after we removed all the player objects. |
Ah! I didn't see the branch. Awesome :D |
@crablar mentioned this happens to him often when developing
Could be due to the nature of live code reloading while developing? Haven't really noticed this as an issue.
The text was updated successfully, but these errors were encountered: