View Issue Details

IDProjectCategoryView StatusLast Update
0005585MMW v4Otherpublic2009-05-15 10:15
ReporterLudek Assigned To 
PriorityimmediateSeverityminorReproducibilityrandom
Status closedResolutionfixed 
Product Version3.0 
Target Version3.1Fixed in Version3.1 
Summary0005585: Podcast episode downloads may be incomplete (due to network interruption)
DescriptionAs reported here:
http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=38691

When network connection is interrupted then MM downloads incomplete episode. MM should report an error or at least doesn't download incomplete episodes.
Additional Informationhttp://www.mediamonkey.com/forum/viewtopic.php?f=6&t=38691
TagsNo tags attached.
Fixed in build1245

Relationships

related to 0000051 closedLudek Errors interrupt Caching/Normalization/Conversion/Synchronization Operations 
parent of 0005703 closedLudek Automatic podcasts update shows error log (regression) 
related to 0001293 closedLudek Download Manager 

Activities

Ludek

2009-05-06 14:20

developer   ~0017699

Fixed in build 1244.

rusty

2009-05-07 21:09

administrator   ~0017733

Tested 1244 as follows:
-Clicked Podcast node > Update all
-While Podcasts were updating, blocked internet access for several seconds via the firewall
-->Update processes just froze and never go away. No errors ever result because the process seems to be 'stuck'. Even right-clicking 'Terminate' has no effect!

I'm not sure if this is a new bug, but it's definitely preventing appropriate errors from showing up.

Ludek

2009-05-10 22:26

developer   ~0017789

Last edited: 2009-05-10 22:31

Rusty, which firewall you use?

I've tested this with PeerGuardian2 and when I block HTTP the progress bar stops (pauses the download), but immediately after allowing HTTP the download progress continues without an error.

If I test it by disabling internet connection then there is the expected error "Incomplete download" shown in the manner of issue 0000051.

Note that if you run the "Update all podcasts" action then no errors are reported, because the same action can be performed also automatically for podcasts and error reporting is not indented here. So now the error is reported only if you run "Update podcast" action. But now (if 0000051 is implemented) we could add the error reporting also to the "Update all podcasts" action, because popped-up errors don't interrupt the whole process now.

rusty

2009-05-11 12:08

administrator   ~0017792

I tested with Zone Alarm and enabled the 'Internet Lock' to test this out. Also note that I was using the 'Update All' function to trigger the updates.

btw, I would definitely expect that podcast error logging would work in all cases, including for 'update all'. Once you make the change, I'll retest.

Ludek

2009-05-11 13:32

developer   ~0017793

Last edited: 2009-05-11 20:03

ok, 'Update all podcasts' now logs the errors same way as in case of individual podcast updating and the error log is shown at the end of of the 'update all podcast' process.

Fixed in build 1245.

Re: the Zone Alarm issue, I have installed Zone Alarm version 8.0.298.000 on Win XP SP2, MM build 1244 and I have no such issue, if I engaged internet lock then download progress pauses and immediatelly after I unticked the "Engage Internet Lock" then the download progress continues without an error.
Try to re-test in build 1245.

rusty

2009-05-15 10:14

administrator   ~0017869

Retested in 1246 and:

Using the ZA internet lock, or by disconnecting ethernet, MM correctly triggered the error dialog.

However, if ZA 'Stop all internet activity' was enabled, then the thread froze, and MM could not be closed except via the task manager. (other network-based apps continued functioning correctly once internet traffic was re-enabled.

rusty

2009-05-15 10:15

administrator   ~0017870

Scratch that--it's working correctly in 1246 in both cases. In the 'buggy' situation, it just took a little longer for the error dialog to appear.