[Varnish] #1576: default pcre_match_limit_recursion and thread_pool_stack dont match - varnishd child process crashes with segfault error 6 in libpcre.so.3.13.1

[Varnish]

#1576: default pcre_match_limit_recursion and thread_pool_stack dont match -
varnishd child process crashes with segfault error 6 in libpcre.so.3.13.1
----------------------+--------------------
 Reporter:  abdi      |       Owner:  slink
     Type:  defect    |      Status:  new
 Priority:  normal    |   Milestone:
Component:  varnishd  |     Version:  4.0.1
 Severity:  normal    |  Resolution:
 Keywords:            |
----------------------+--------------------

Comment (by quintonparker):

 Hi

 I believe I'm experiencing the same issue in varnish 4.0.2 on ubuntu
 precise lts server

 Linux app1.spreeza.net 3.11.0-26-generic #45~precise1-Ubuntu SMP Tue Jul
 15 04:02:35 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

 This is my syslog snippet

 Jan 16 07:48:11 app1 kernel: [11057670.418598] varnishd[11360]: segfault
 at 7f14469bcec0 ip 00007f1445e03a7a sp 00007f14469bce50 error 6 in
 libpcre.so.3.12.1[7f1445df1000+3c000]
 Jan 16 07:48:13 app1 varnishd[47915]: Child (11325) died signal=11 (core
 dumped)
 Jan 16 07:48:13 app1 varnishd[47915]: Child cleanup complete
 Jan 16 07:48:13 app1 varnishd[47915]: child (12116) Started
 Jan 16 07:48:13 app1 varnishd[47915]: Child (12116) said Child starts

 Worth noting that I'm also using devicedetect.vcl

 Increasing thread_pool_stack from 48k to 64k seems to have alleviated the
 problem. Child processes were crashing on an hourly basis but I can now
 report 15 hours of uptime. Not sure if that solved the issue for good :/

-- 
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1576#comment:21>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator