Polarion is our application and it uses SvnKit (http://svnkit.com/) as a
connector to SVN. We use SVNKit version 1.8.12.
Dump from our application also shows that the threads are waiting for data
from network. Could it be an issue in Windows itself? Anyway, we have seen
this behavior both in Windows and Linux environment and never seen it with
Subversion 1.8 and earlier, so we suspect it's a regression in Subversion.
From: Ivan Zhakov [mailto:ivan_at_visualsvn.com]
Sent: Tuesday, May 31, 2016 2:10 PM
To: Radek Krotil
Subject: Re: Deadlock-like behaviour of svnserve in multi-threaded mode (-T)
On 31 May 2016 at 14:43, Radek Krotil <radek.krotil_at_polarion.com> wrote:
> Hi Ivan.
> I managed to get the debug symbols for the Subversion binaries, we've
> been using. It can be downloaded at
As far I see all 22 workers threads are waiting for data from network:
ntdll.dll!NtWaitForSingleObject () Unknown
mswsock.dll!SockWaitForSingleObject () Unknown
mswsock.dll!WSPRecv () Unknown
ws2_32.dll!WSARecv () Unknown
svnserve.exe!sock_read_cb(void * baton, char * buffer, unsigned
__int64 * len) Line 120 C
svnserve.exe!readbuf_fill(svn_ra_svn_conn_st * conn, apr_pool_t *
pool) Line 391 C
svnserve.exe!svn_ra_svn__read_tuple(svn_ra_svn_conn_st * conn,
apr_pool_t * pool, const char * fmt, ...) Line 1379 C
svnserve.exe!serve_interruptable(int * terminate_p, connection_t *
connection, int(*)(connection_t *) is_busy, apr_pool_t * pool) Line
svnserve.exe!serve_thread(apr_thread_t * tid, void * data) Line 598 C
It also seems that you're using some third-party (Polarion) svn:// client
for Subversion. Is it true?
Received on 2016-05-31 16:19:16 CEST