[squid-dev] unhandled exception

[Alex Rousskov]

On 02/11/2016 12:39 PM, William Lima wrote:

> What could cause the exception below (src/BodyPipe.cc:281|334)?

A bug. Well, actually two bugs in this case:

* The bug that caused the exception to be thrown.

* The lack of code to handle that exception properly [without killing
Squid]. This is a known problem in many code areas [outside of AsyncJob
kids].

The BodyPipe::expectNoConsumption() code is well documented so you may
be able to tell what that exception means by reading the code.

The BodyPipe::startAutoConsumption() exception should be
self-explanatory: if we are starting to *auto* consume, there should be
no consumer already. Memory corruption aside, that existing/conflicting
consumer is either a regular Consumer code or an earlier auto-consuming
Consumer.

Beyond those immediate reasons, a triage is needed to understand what
exactly went wrong and how to fix it. You may also want to do a bugzilla
search. IIRC, similar problems have been solved before.


HTH,

Alex.