JDownloader Community - Appwork GmbH
 

Reply
 
Thread Tools Display Modes
  #1  
Old 04.07.2022, 01:56
armin.beispiel armin.beispiel is offline
Vacuum Cleaner
 
Join Date: Nov 2015
Posts: 19
Default Downloads stopped one file too early

When I choose "Stop after this download" from the context menu of a file, that file itself isn't downloaded, only the one before it, although it should be downloaded and then JD should stop.

If it helps, I'm currently downloading with Rapidgator and I believe a reconnect is necessary after each file.

Last edited by armin.beispiel; 04.07.2022 at 02:03.
Reply With Quote
  #2  
Old 04.07.2022, 09:17
Jiaz's Avatar
Jiaz Jiaz is offline
JD Manager
 
Join Date: Mar 2009
Location: Germany
Posts: 76,793
Default

@armin.beispiel: did you set *stop after this download* on the file that requested the reconnect?
File A, File B(Stopmark)
File A -> Reconnect
File A finished -> File B -> Reconnect- >Stop?
I'm asking because the *Stop after this download* does not mean *stop when this file is downloaded* but *stop when you tried at least once to download the file*, else a broken file (eg waiting, and waiting and waiting) would just make your JDownloader continue to download despite the stopmark being reached.
__________________
JD-Dev & Server-Admin
Reply With Quote
  #3  
Old 04.07.2022, 09:21
Jiaz's Avatar
Jiaz Jiaz is offline
JD Manager
 
Join Date: Mar 2009
Location: Germany
Posts: 76,793
Default

__________________
JD-Dev & Server-Admin
Reply With Quote
  #4  
Old 04.07.2022, 21:41
armin.beispiel armin.beispiel is offline
Vacuum Cleaner
 
Join Date: Nov 2015
Posts: 19
Default

Quote:
Originally Posted by Jiaz View Post
did you set *stop after this download* on the file that requested the reconnect?
It seems, reconnects only happen sporadically, not before every file. So, I don't know whether the file with the stopmark that wasn't downloaded was the one that requested a reconnect. It's also not trivial to find out because the hoster is slow and the files are big (= short, rare time windows for checking).

But it seems you found something to improve that'll likely be the cause.
Reply With Quote
  #5  
Old 05.07.2022, 10:43
Jiaz's Avatar
Jiaz Jiaz is offline
JD Manager
 
Join Date: Mar 2009
Location: Germany
Posts: 76,793
Default

Quote:
Originally Posted by armin.beispiel View Post
But it seems you found something to improve that'll likely be the cause.
At least for the *reconnect scenario*, yes, that I can improve, maybe that will solve your problem
__________________
JD-Dev & Server-Admin
Reply With Quote
  #6  
Old 05.07.2022, 11:42
Jiaz's Avatar
Jiaz Jiaz is offline
JD Manager
 
Join Date: Mar 2009
Location: Germany
Posts: 76,793
Default

A fix for this scenario is more complex than I though. A download that requires reconnect currently counts as *at least tried once* and thus stop mark is reached. When I change this logic, then a single download waiting for reconnect will cause other links to be started. imagine not having setup a working reconnect, then JDownloader would just continue downloading all the rest.
I've tried a simple solution where JDownloader does allow 1 mins for reconnect to happen and continue. Please check again with next core update. Within that time window new/next downloads may get startet
__________________
JD-Dev & Server-Admin

Last edited by Jiaz; 05.07.2022 at 11:47.
Reply With Quote
  #7  
Old 05.07.2022, 20:20
armin.beispiel armin.beispiel is offline
Vacuum Cleaner
 
Join Date: Nov 2015
Posts: 19
Default

Couldn't the logic be changed to always handle the stopmark on the next file. So, it is checked as soon as a file starts "Is file after file with stopmark?" If yes, don't continue with the file.

If actions like deactivating files are performed, the internal file-after-stopmark mark would need to be re-evaluated. Maybe your new timeout code (a bit longer?) could function as a fallback, in case of a bug where JD wouldn't stop.
Reply With Quote
  #8  
Old 06.07.2022, 10:12
Jiaz's Avatar
Jiaz Jiaz is offline
JD Manager
 
Join Date: Mar 2009
Location: Germany
Posts: 76,793
Default

@armin.beispiel: changing the behavior is never a good idea please wait for next core update and see if it helps in your situation
__________________
JD-Dev & Server-Admin
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT +2. The time now is 01:01.
Provided By AppWork GmbH | Privacy | Imprint
Parts of the Design are used from Kirsch designed by Andrew & Austin
Powered by vBulletin® Version 3.8.10 Beta 1
Copyright ©2000 - 2022, Jelsoft Enterprises Ltd.