View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0019379 | MMW 5 | Playback | public | 2022-09-15 22:06 | 2022-09-16 00:22 |
| Reporter | rusty | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | sometimes |
| Status | feedback | Resolution | open | ||
| Product Version | 5.2 | ||||
| Target Version | 5.2 | ||||
| Summary | 0019379: Playback issues on resume from sleep on systems using 'Modern standby' | ||||
| Description | On systems that use S0 (=Modern Standby) to sleep (rather than S3, which has been used traditionally), MediaMonkey occasionally experiences playback problems on resume including: - the seekbar not displaying or not displaying in the correct position (occurs 1/5 times) - playback starts by itself (1/10 times) This occurs because as soon as the machine starts going to sleep, Windows stops MM threads, ignoring MM requests to briefly postpone sleep (by SetThreadExecutionState and/or PowerSetRequest) to save MM's state (playback, etc.). Because state isn't fully saved, issues can occur on resume (on waking up these threads continue to try to save state and prepare for sleep, even though the system is already waking from sleep). This can be replicated as follows: 1 Launch MM 2 initiate playback and press PAUSE 3 Close laptop to trigger Sleep mode 4 Open laptop --> Screensaver displays 5 Click mouse (on a portion of the screen where MediaMonkey isn't displayed) --> Apps display, but after a few seconds the MM seekbar indicator may disappear! 6 Repeat steps 3-5 4x --> MM may start playing by itself for a couple of seconds Because the playback problem rarely occurs and because the effect on the user is minimal, we can target a fix with low priority. | ||||
| Additional Information | This bug was originally reported at 0019063. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
