Reply to thread

Message

<blockquote data-quote="RoChess" data-source="post: 1094708" data-attributes="member: 18896">The one comminality I can see between the majority of users who actually experience it is that they run a well-above average configuration. Shouldn't make a difference, but it seems to make things break easy. For me the only bug worth pursuing is a reproducable one, and that just has not been made possible yet for this one. It is easy to sort of force reproduction, and that is to unplug the power to your computer or harddisk right when MP-TVSeries is doing updates to the SQLite index.&nbsp;Maybe the users have a large series database, that takes a long time to verify and they have set their collection rescan time to sharp, so it goes into a constant SQLite update loop in the background. I've gone through the trouble to manually go into my MP-TVSeries collection and mark each 'Ended' show to be checked for &quot;ignore on scan&quot;. But I've changed so many other things, so no idea if that is why the only time my MP-TVSeries database went correct is because I had concurrent RDP open and editing MP-TVSeries dbase and somebody else without me knowing held down power button on HTPC thinking it was &quot;frozen&quot;. In some cases that was with multiple on/offs a week of entire HTPC, or months of 24/7 usage via MP-TVSeries playlists, over a timespan of at least the last 2 years. Of course I don't use standby/resume, for me the screen goes black, and the CPU idles, so maybe the problem lies in there, not enough confirmations if that is the comminality when corruption occurs.&nbsp;I did had corruption myself once a week from older LastMediaAdded plugin, which was harmless, but annoying and what inspired me to write the auto-backup/restore script, which was also a good idea for getting backups anyway <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="RoChess, post: 1094708, member: 18896"] The one comminality I can see between the majority of users who actually experience it is that they run a well-above average configuration. Shouldn't make a difference, but it seems to make things break easy. For me the only bug worth pursuing is a reproducable one, and that just has not been made possible yet for this one. It is easy to sort of force reproduction, and that is to unplug the power to your computer or harddisk right when MP-TVSeries is doing updates to the SQLite index. Maybe the users have a large series database, that takes a long time to verify and they have set their collection rescan time to sharp, so it goes into a constant SQLite update loop in the background. I've gone through the trouble to manually go into my MP-TVSeries collection and mark each 'Ended' show to be checked for "ignore on scan". But I've changed so many other things, so no idea if that is why the only time my MP-TVSeries database went correct is because I had concurrent RDP open and editing MP-TVSeries dbase and somebody else without me knowing held down power button on HTPC thinking it was "frozen". In some cases that was with multiple on/offs a week of entire HTPC, or months of 24/7 usage via MP-TVSeries playlists, over a timespan of at least the last 2 years. Of course I don't use standby/resume, for me the screen goes black, and the CPU idles, so maybe the problem lies in there, not enough confirmations if that is the comminality when corruption occurs. I did had corruption myself once a week from older LastMediaAdded plugin, which was harmless, but annoying and what inspired me to write the auto-backup/restore script, which was also a good idea for getting backups anyway :) [/QUOTE]

Verification