[
https://issues.apache.org/jira/browse/SVN-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16881270#comment-16881270
]
Alexander Veit commented on SVN-4817:
-
Further analyze showed that this bug is related to the {{--threads}} option in
{{svnserve}}.
When {{svnserve}} is started without {{--threads}} set, the segfault disappears.
> svnserve: frequent segfaults in libapr
> --
>
> Key: SVN-4817
> URL: https://issues.apache.org/jira/browse/SVN-4817
> Project: Subversion
> Issue Type: Bug
> Components: svnserve
>Affects Versions: 1.12.x
> Environment: OS:
> Linux 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1 (2019-04-12) x86_64 GNU/Linux
> Distributor ID: Debian
> Description:Debian GNU/Linux 9.9 (stretch)
> Release:9.9
> Codename: stretch
> svnserve, version 1.12.0 (r1857323)
>compiled May 17 2019, 12:46:50 on x86_64-unknown-linux-gnu
> The following repository back-end (FS) modules are available:
> * fs_fs : Module for working with a plain file (FSFS) repository.
> * fs_x : Module for working with an experimental (FSX) repository.
> * fs_base : Module for working with a Berkeley DB repository.
>Reporter: Alexander Veit
>Priority: Critical
>
> We have various Jenkins jobs that nondeterministically fail during Subversion
> operations. The kernel ring buffer shows svnserve segfaulting when this
> happens.
> The Subversion binary is linked with the libraries provided with Debian
> Stretch.
> libapr1/stable,now 1.5.2-5 amd64 [installed]
> libapr1-dev/stable,now 1.5.2-5 amd64 [installed]
> libaprutil1/stable,now 1.5.4-3 amd64 [installed]
> libaprutil1-dev/stable,now 1.5.4-3 amd64 [installed]
> This error also occurred with a previous Subversion version.
> {noformat}
> ...
> 2019-05-20T06:50:30,516658+0200 svnserve[27597]: segfault at 8 ip
> 560d6c4d13ea sp 7fd4d2ef3e50 error 4 in svnserve[560d6c4c3000+15000]
> 2019-05-20T06:50:30,686601+0200 svnserve[27701]: segfault at 14 ip
> 7fa5d93bf822 sp 7fa59bd19c90 error 4 in
> libapr-1.so.0.5.2[7fa5d93a3000+32000]
> 2019-05-20T06:58:56,623191+0200 svnserve[6754]: segfault at 0 ip
> 7f45cafc6edd sp 7f459effccb0 error 4 in
> libapr-1.so.0.5.2[7f45cafaa000+32000]
> 2019-05-20T07:05:30,620531+0200 svnserve[15425]: segfault at 0 ip
> 7fd59013aedd sp 7fd57156ccb0 error 4 in
> libapr-1.so.0.5.2[7fd59011e000+32000]
> 2019-05-20T07:26:30,485982+0200 svnserve[11182]: segfault at 0 ip
> 7f1ddc86aedd sp 7f1d5fffecb0 error 4 in
> libapr-1.so.0.5.2[7f1ddc84e000+32000]
> 2019-05-20T08:29:30,118881+0200 svnserve[31762]: segfault at 14 ip
> 7f4f517a2822 sp 7f4f0dffac90 error 4 in
> libapr-1.so.0.5.2[7f4f51786000+32000]
> 2019-05-20T08:29:30,688443+0200 svnserve[32187]: segfault at 14 ip
> 7f2795f84822 sp 7f279233dc90 error 4 in
> libapr-1.so.0.5.2[7f2795f68000+32000]
> 2019-05-20T08:47:30,951617+0200 svnserve[27102]: segfault at 3c ip
> 7f25a5847d9a sp 7f2579328de0 error 4 in
> libapr-1.so.0.5.2[7f25a5825000+32000]
> 2019-05-20T08:54:30,986006+0200 svnserve[4841]: segfault at 18 ip
> 7fc9ee2337a1 sp 7fc99bffec90 error 4 in
> libapr-1.so.0.5.2[7fc9ee217000+32000]
> 2019-05-20T09:10:56,631800+0200 svnserve[27994]: segfault at 0 ip
> 7f7431d9fedd sp 7f7404800cb0 error 4 in
> libapr-1.so.0.5.2[7f7431d83000+32000]
> 2019-05-20T09:19:30,828900+0200 svnserve[8397]: segfault at 0 ip
> 7f79c3c0aedd sp 7f798d7f9cb0 error 4 in
> libapr-1.so.0.5.2[7f79c3bee000+32000]
> 2019-05-20T09:28:30,379310+0200 svnserve[20890]: segfault at 0 ip
> 7f2d9ca29edd sp 7f2d61d15cb0 error 4 in
> libapr-1.so.0.5.2[7f2d9ca0d000+32000]
> 2019-05-20T09:40:30,294511+0200 svnserve[5491]: segfault at 14 ip
> 7f5cac6bf822 sp 7f5c5fffec90 error 4 in
> libapr-1.so.0.5.2[7f5cac6a3000+32000]
> 2019-05-20T09:41:29,829458+0200 svnserve[6334]: segfault at 18 ip
> 7fba8d1cd7a1 sp 7fba3a7fbc90 error 4 in
> libapr-1.so.0.5.2[7fba8d1b1000+32000]
> 2019-05-20T09:50:29,728226+0200 svnserve[20593]: segfault at 14 ip
> 7efe463e7822 sp 7efe1e04bc90 error 4 in
> libapr-1.so.0.5.2[7efe463cb000+32000]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
