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
The app uses about twice or three times as much memory after playing multiple video's in succession without closing the app.
After some research, there are multiple things we can do:
Unsubscribe from event handlers
Dispose the Media as per the LibVLCSharp.UWP sample
Stop using MVVM Light as it is no longer maintained and has leaks as well.
It might also have something to do with this issue.
The text was updated successfully, but these errors were encountered:
Related issue is #40.
VideoPlayerPageViewModel:
- chg: Instead of lambda's, event handlers are now used for all events,
including timers. The fileNameOverlayTimer has been moved to the top and
made readonly, so it is only initialized once. Also, some comments have
been split over multiple lines.
- fix: The fileNameOverlayTimer is now only once instead of every 5 seconds.
Views/VideoPlayerPage.xaml.cs:
- chg: Unsubscribe from events using event handlers instead of lambda's.
Some comments have been split over multiple lines.
Related issue is #40.
App.xaml.cs:
- add: Global UI dispatcher property, so every class can access the UI conventiently.
VideoPlayerPageViewModel.cs:
- rem: Unneeded using system.diagnostics.
VideoPlayerPage.xaml.cs:
- chg: Dispose the media after playing it by wrapping it in a using. This follows the
official LibVLCSharp UWP sample. Replaced lengthy dispatcher calls with App.Current.
The app uses about twice or three times as much memory after playing multiple video's in succession without closing the app.
After some research, there are multiple things we can do:
It might also have something to do with this issue.
The text was updated successfully, but these errors were encountered: