[Varnish] #1391: Condition(!VTAILQ_EMPTY(&bo->fetch_obj->store)) not true
Varnish
varnish-bugs at varnish-cache.org
Mon Dec 16 14:31:16 CET 2013
#1391: Condition(!VTAILQ_EMPTY(&bo->fetch_obj->store)) not true
----------------------+----------------------------------------
Reporter: lkarsten | Owner: Poul-Henning Kamp <phk@…>
Type: defect | Status: closed
Priority: normal | Milestone: Varnish 4.0-TP1
Component: varnishd | Version: unknown
Severity: normal | Resolution: fixed
Keywords: |
----------------------+----------------------------------------
Changes (by Poul-Henning Kamp <phk@…>):
* owner: => Poul-Henning Kamp <phk@…>
* status: new => closed
* resolution: => fixed
Comment:
In [b253bf9c52929e13f13c65670dd08871feb1f977]:
{{{
#!CommitTicketReference repository=""
revision="b253bf9c52929e13f13c65670dd08871feb1f977"
When a streaming delivery of a pass object is terminated prematurely,
we cannot just throw the storage away, we have to wait for the
fetch-thread to go away, possibly in response to a new "abandon"
signal.
Spotted first by: scoof
Fixes #1391
}}}
--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1391#comment:1>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator
More information about the varnish-bugs
mailing list