I apologize for the vague nature of this problem report but I can't be any more specific. Here's my environment:
Windows 7 64-bit, VDH 7.3.6a1, CoApp 1.2.4, license verified, Firefox 62.0 64-bit, VLC 3.0.4 Vetinari
This has happened to me a few times today & the pattern is always the same. I think part of the way to recreate this problem requires a relatively slow Internet connection. Mine is about 530KB, what Windows Resource Monitor reports as 550,000 bytes per second.
Here's how the pattern has gone. I'll launch several simultaneous downloads, say 6, using the CoApp. Sorry, these are from a pay site so I can't share URLs. Each one will be an MP4 file in the 1G-2G range. VDH will report, after all 6 downloads are safely in progress, that times to complete will be in the range of 2-8 hours, sometimes longer. Things will run fine for a couple of hours until one of the downloads completes. During that time, I will periodically drop down the VDH menu to check how things are going & each download will have progressed some. I will also go to the directory using Windows Explorer (File Manager) into which I'm doing these downloads & refresh the display. The file sizes will show increases on all the files.
But when a download completes, my entire system comes to its knees. When I'm downloading only a single file, I usually notice my whole system becomes unresponsive for 3 or 4 seconds, then the VDH notification pops up & things go back to normal. But in this case, the VDH notification pops up & things do not go back to normal. Task Manager gives me the "task is not reesponding" message. You know things are bad when even Task Manager refuses to take focus. I have the Task Manager window positioned so that I can see all the Firefox threads as well as the CoApp thread. The CoApp, which until then will have been showing a memory usage in the 1G range, suddenly is showing 3G & grows. I've seen it go over 4G. I have 8G of real RAM. The Task Manager, when it shows anything at all, says my memory usage is over 90%. But with Task Manager flipping in & out of unresponsive state, that display comes & goes.
Meanwhile, Firefox windows become extremely sluggish. The disk activity light on the computer case is on solid, not flickering. Firefox windows respond eventually, but in times measured in minutes. It's all I can do to get logged off the pay site & close the browser windows. Things aren't helped at all by the fact that Task Manager, even though it's in the "not responding" state & refuses to take focus, still sits on top of all open windows obscuring whatever is behind it. I can't get any window to display on top of Task Manager. Eventually I get all Firefox windows to close & the system sits there with the disk activity light still on solid, not flickering. After waiting a couple of minutes, Firfox generates a crash report. Fortunately, the button that says "Quit Firefox" is visible peeking around from behind the Task Manager window so I can click it to get Firefox to send its crash report to Mozilla & close. When the crash report finally gets sent, all the Firefox threads disappear from the Task Manager display, taking the CoApp with them, Task Manager finally starts responding again, & I get my system back to running normally.
Until everything happens again. I do want to download those files, which I am managing to do one at a time. For the time being, it seems like I am stuck downloading only 1 file at a time. I know I can set VDH to download only 1 file at a time & let its queueing take care of things. But this is not supposed to be necessary. I have had lots of downloads running concurrently in the past & never had this problem.
I am speculating that there is a memory leak in the CoApp. I think the fact that the entire system becomes unresponsive while the CoApp is finalizing a download, even when it's the only download I'm doing, is also a clue to . . . something.
I wish I could be more specific. If there is something I can do to take some diagnostics for you, let me know. They would have to be things that get launched early because when this starts happening, there isn't much chance I'll be able to launch a diagnostic since my system is essentially unusable until I can clear the condition.
It also occurs to me that the CoApp is holding things in RAM until it's time to write them to disk. Unfortunately, when you've got a bunch of large downloads all running at the same time, this can make the CoApp's memory demand grow prohibitively large. I suggest this design needs some rethinking. Perhaps you can hold less transient stuff in RAM & write more of it to disk every so often instead. I know, I'm guessing & maybe that's not how things actually work. But I'm trying to think of reasons for the CoApp to need such a large memory footprint. I think that footprint is the root cause of the problem. At the least, I'm hoping to maybe trigger some ideas, ones I wouldn't know enough to come up with myself.