Show Posts
1
Bug Reports / Persistence Failure - Application State and Song Properties
« on: March 29, 2017, 02:13:58 PM »
Summary:
In certain situations, song properties such as play count information fail to be preserved, along with other application state information such as the Playing Tracks list (at a minimum; the full extent of this bug is not known).
This is an issue whenever MusicBee is forcibly exited, either due to a crash*, Windows shutting down**, or deliberate termination of the program via the Task Manager. Closing MusicBee from within the application itself will not cause this bug.
To reproduce:
1. Start MusicBee.
2. Select a song and take note of its current play count.
3. Play the song so that its play count increments by one, or manually update the play count to a new value.
4. Open the Windows Task Manager and terminate MusicBee forcibly. (It is necessary to do so via the Processes tab, as terminating through the Application tab first sends the WM_CLOSE message, which is equivalent to simply clicking File > Exit in MusicBee itself.)
5. Open MusicBee again and note that the song's play count will have reverted to the value observed in step two. Similarly, any updates to the Playing Tracks list (songs added or removed) will have reverted to the state it was in at the time of step two.
Some pieces of information seem not to be affected by this bug—changes to tags (as opposed to properties) such as artist name will persist, and a song dragged from the inbox to the main library will not revert to the inbox. Editing both tags and properties for a song and then reproducing the bug will result in tags being preserved, but not properties.
(I assume that MusicBee saves only file-based metadata immediately upon updating it, and information stored within MusicBee's database is saved just once, when the application quits—but that's speculation, and you'd definitely know better.)
Running Environment:
I am currently running the latest 3.0 release of MusicBee in portable mode on a Windows 7 machine. This bug has been observed in prior versions of the program under the same setup.
-----------------------
*I can't recall MusicBee ever crashing suddenly on me due to a fault in the program, but it has happened on occasion that an unexpected disconnection of the portable media that the program resides on caused MusicBee to crash. An unreliable USB connection can cause this to happen fairly frequently.
**I'm not 100% certain about this one—it may only be certain cases where Windows doesn't shut down correctly or applications are force-closed during shutdown.
In certain situations, song properties such as play count information fail to be preserved, along with other application state information such as the Playing Tracks list (at a minimum; the full extent of this bug is not known).
This is an issue whenever MusicBee is forcibly exited, either due to a crash*, Windows shutting down**, or deliberate termination of the program via the Task Manager. Closing MusicBee from within the application itself will not cause this bug.
To reproduce:
1. Start MusicBee.
2. Select a song and take note of its current play count.
3. Play the song so that its play count increments by one, or manually update the play count to a new value.
4. Open the Windows Task Manager and terminate MusicBee forcibly. (It is necessary to do so via the Processes tab, as terminating through the Application tab first sends the WM_CLOSE message, which is equivalent to simply clicking File > Exit in MusicBee itself.)
5. Open MusicBee again and note that the song's play count will have reverted to the value observed in step two. Similarly, any updates to the Playing Tracks list (songs added or removed) will have reverted to the state it was in at the time of step two.
Some pieces of information seem not to be affected by this bug—changes to tags (as opposed to properties) such as artist name will persist, and a song dragged from the inbox to the main library will not revert to the inbox. Editing both tags and properties for a song and then reproducing the bug will result in tags being preserved, but not properties.
(I assume that MusicBee saves only file-based metadata immediately upon updating it, and information stored within MusicBee's database is saved just once, when the application quits—but that's speculation, and you'd definitely know better.)
Running Environment:
I am currently running the latest 3.0 release of MusicBee in portable mode on a Windows 7 machine. This bug has been observed in prior versions of the program under the same setup.
-----------------------
*I can't recall MusicBee ever crashing suddenly on me due to a fault in the program, but it has happened on occasion that an unexpected disconnection of the portable media that the program resides on caused MusicBee to crash. An unreliable USB connection can cause this to happen fairly frequently.
**I'm not 100% certain about this one—it may only be certain cases where Windows doesn't shut down correctly or applications are force-closed during shutdown.