842020 - tstclnt -O (sync verify) deadlock on Windows (at least XP + Server 2003)

Status: RESOLVED INVALID

(NSS :: Tools, defect)

Description

[Kai Engert [:KaiE:]]

As part of the work for bug 360420 (patch 3 of 4), I've added new tests that verify the arrival of stapled certificate status information as part of the handshake.

In order to make life simple, I had chosen to make use of the existing, synchronous verification feature offered by tstclnt, using -O

While it appears to work fine on most platforms, we experience a deadlock on Windows, I've seen it on both Windows XP and Windows Server 2003 - using the preferred WIN95 build configuration.


The deadlock is unrelated to the new OCSP stapling code.

Using a build from before adding that code, I can reproduce the deadlock using:
  tstclnt -V tls1.0: -O -h mozilla.org -p 443 -d dbdir

Comment 1

[Kai Engert [:KaiE:]]

The deadlock happens at process exit. In the Windows debugger, I see three active threads:

The main thread is waiting in PR_Cleanup, line 364, _pr_userActive is 2, therefore waiting for the _pr_primordialExitCVar without timeout.

A second thread is blocked inside tstclnt's thread_main function, waiting inside PR_Read.

(The third thread is named Win64 Thread, no debug symbols, call stack consists of kernel calls, only.)

Comment 2

[Kai Engert [:KaiE:]]

Luckily there seems to be a very obvious reason for this problem. I'm not piping any input data to standard input (as all the other tstclnt invocations do), that's why it blocks forever... It's independent of the -O option.

Comment 3

[Kai Engert [:KaiE:]]

invalid