[djmakinera]

Possible improve the speed of the addition of a single or more packages to download?
Ps. The current jdownloader installation on a fast SSD
500K-1M links | Current setting -Xmx7GB
The duration of the addition of one or more package ~1 minutes ~1,5 minutes

[Jiaz]

Speed highly depends on number of links in package.

[djmakinera]

Speed highly depends on number of links in package.

Not always:

TEST

1000 links (1 package) = FAST ADD
7000+ links (1 package) = SLOW ADD
Links (6 + 11 + 18 + 14 + 12) (5 package) = SLOW ADD

[Jiaz]

You talked about adding package and NOT crawling!
Crawling highly depends on the plugin and limits. If this is about VK plugin then we can stop right here!

[djmakinera]

Add packages from [TAB Linkgrabber] to [TAB Download], very clearly I expressed itself.

[Jiaz]

And how many Links/Packages are within your Linkgrabber/DownloadList?
If there are many then I already linked the correct ticket

[djmakinera]

Above 200k - 1000k (LinkGrabber list)
The problem only affect "Linkgrabber list" (does not apply to "Download list")

[Jiaz]

Linkgrabber List has to maintain a duplicate map. so very long list = more time required.
That's exactly what the linked ticket is about

[djmakinera]

This problem is always present, even after the new installation, and even if it contains only one link and one package (in Linkgrabber)
VERRRRYYYY SMALL LIST!!!

It occurs only in the case of a domain Vk!

[Jiaz]

The stacktrace shows that the zip file is empty and not correct written. Either filesystem error or you killed JDownloader during shutdown. And again this has NOTHING to do with the thread topic!

[djmakinera]

1. Either filesystem error
2. killed JDownloader during shutdown

Not true !
Every Run or restart JD2 is the same error.

I checked it on various system configurations
1. Acer (Laptop) XP/Vista
2. and PC Desktop Win 7

My friend is also checked and said that for him the same error.

The error occurs only if the domain VK and a ONLY new version/build of JD2


In all the old versions (test many different installation), for example. 2013, 2014 (No error!!!)

[djmakinera]

1. Either filesystem error
2. killed JDownloader during shutdown

I tested domain

zippyshare.com, and various other domain

a) I killed the process = No error !!!
b) cutting off Power Supply (!) = No error !!!

I tested domain

vk.com

(only one 1 link)
a)Correct Exit or Restart = ALWAYS Error
b)Without power off = ALWAYS Error


So what's going on here? Where there is an Internal Error in the new version JD2?

[Jiaz]

Please provide a single VK link for testing.
And PLEASE post in the correct thread! This is the wrong thread!

[Jiaz]

This error
Empty/Invalid Zip:C:\JDownloader2\cfg\linkcollector1416.zip|Size:0
Signals that the Zip file is empty.
When there are issues during saving the file will be deleted and there are traces in logfile.

[djmakinera]

I found an old topic of August 2016, so you could move:
https://board.jdownloader.org/showpo...3&postcount=38

Restart or Run
repeating a 1000 times restart or run
generate 1000 errors in the log

1 Run or Restart = 1 Error Found
1000 Run or Restart = 1000 Error Found
only the number of erroneous archive change (each time a different number)

[Jiaz]

Works perfectly fine for me.
I can offer you a teamviewer session about this. Just send me ID and PW to support@jdownloader.org

[djmakinera]

Jiaz - Now I know what causes this error.
The startup parameters causing this error: Empty/Invalid Zip

"C:\Program Files\Java\jre1.8.0_112\bin\javaw.exe" -Xdiag -Xms2G -Xmx7G -jar C:\Jdownloader2\JDownloader.jar

Please correct the startup parameters that do not cause this problem because without parameters, not enough memory allocated (Especially for a large list of links and stability GUI)

[Jiaz]

The zip file is created during saving and not during loading
Nothing to fix in JDownloader. It simply fails to save the list because it is out of memory!

[Jiaz]

I will reduce memory usage during saving the list. Wait for next core update

[Jiaz]

Reduced memory usage during linklist saving, please check again with next core update