Hi Jiaz,
Thank you very much for your quick answer.
I'm not a software programmer, but I understand from what you're saying that Java's memory management is probably overburdened when a massive load of archives must be processed in one session. I'll remember to write down the figures in the About Dialog window and send them to the JD community whenever I encounter problems like this with JDownloader (if JD is still responsive under such circumstances). Thanks for your advice on how to handle this kind of situation and about setting op JD to remove finished links/archives automatically. I'm going to use that option.
I hope you can find time to rewrite the parts in JD that are responsible for this memory problem.
Do you think it helps to free up memory space if I instruct JD to remove the finished (extracted) archives and links during the active session?
rockwater