RFR: 8320691: Timeout handler on Windows takes 2 hours to complete [v2]

[Alan Bateman]

On Fri, 24 Nov 2023 09:40:16 GMT, Daniel Jeliński <djelinski at openjdk.org> wrote:

>>> Notice the absence of "params" part in that key. I wonder if that is playing a role here and whether we should fix this key.
>> 
>> Actually ignore that part. I had a look at the internal logs that you referenced. It appears that this form of specifying the timeout (through the use of `params` key) seems to work too. The reason why it took 2 hours is because it ran that command against 2 separate processes and each one timed out after one hour:
>> 
>> 
>> [2023-11-23 21:45:40] [cdb.exe, -c, ".dump, /f, core.12345;qd", -p, 12345] timeout=3600000
>> ...
>> 0:001> WARNING: tool timed out: killed process after 3600000 ms
>> ----------------------------------------
>> [2023-11-23 22:45:40] exit code: -2 time: 3600006 ms
>> ----------------------------------------
>> 
>> 
>> ----------------------------------------
>> [2023-11-23 22:47:36] [cdb.exe, -c, ".dump, /f, core.6789;qd", -p, 6789] timeout=3600000
>> ----------------------------------------
>> 
>> ...
>> 0:063> WARNING: tool timed out: killed process after 3600000 ms
>> ----------------------------------------
>> [2023-11-23 23:47:36] exit code: -2 time: 3599996 ms
>> ----------------------------------------
>> 
>> 
>> Edit: ... and you did mention about this in the description of the JBS issue. I just overlooked it :)
>
> good point, 10 minutes should be more than enough. I'll update.

Out of curiosity, do we know why it takes more than an hour? Is it attempting to connect to the Microsoft symbol server?

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/16806#discussion_r1404194681