There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
We are seeing a bug with the Player Framework v2.0 (for Windows Store) where seeking becomes unresponsive until the application is restarted. We are able to reproduce it by quickly calling player.SeekAsync() twice. It seems that calling it a second time
(before the first fully completes) puts the framework into a state where it will never seek again. The same behavior is seen when setting player.Position() instead of SeekAsync. We are able to issue other types of commands like play / pause, change the source
url ect but it will not ever seek again.
Putting a mutex around await player.SeekAsync() helped the problem but it seems like SeekAsync() returns before the seek is truly finished. Is this a bug in the Player Framework or is there some work around we can do in our app?