Download status: Inconsistent information on low storage devices

[WebworkrNet]

Both the open app itself and an associated PUSH message after the start of a download inform about the download status. However, this information is not always consistent, as the following example shows.

The phenomenon occurs in connection with scarce free device memory. There may be a causal relationship.

[WebworkrNet]

Two other examples:

Download list shows that the uploads were aborted with error.

However, the PUSH messages indicate that the download process is still running, although it is currently interrupted.

[WebworkrNet]

Another recent example (without memory warning)

Addendum:
In this case the problem could be homemade. I may have deleted the temporary file in the download in the meantime to free up limited storage space for another download. At the same time, I didn't want to interrupt the ongoing download process, see #310 FR "Pause downloads". If the process happened like this, then at the end it may not be checked whether the video file is complete.

[WebworkrNet]

I'm not sure whether this problem is really due to the lack of memory. #452 occurs without a memory warning, but is otherwise inconsistent.