Re: What does the error "Process <URL> not running" mean?

[Stefan Monnier]

Eli Zaretskii [2022-02-07 22:10:09] wrote:
>> I've tried it (with just 5 of your urls) on GNU/Linux and see the same.
>> The network processes seem to stay in open status for quite some time
>> even though I also killed the buffer in the callback function.  It's now
>> about 5 minutes since my test and still 4 of initially 8 or 9 network
>> processes are listed as open in `list-processes'.
>> 
>> I have no idea if that's intended or not.
>
> Isn't that the timeout till the other side closes the connection?

So the URL library (under w32) should try and eagerly cull its set of
open connections to bound the number of open connections it keeps well
below the 32 limit.


        Stefan