Github user shinrich commented on the issue:
https://github.com/apache/trafficserver/pull/694
In our most recent fire drill, the core was very useful. The particular
problem only happens under very heavy load. By poking around the core, we got
some idea of the underlying cause and were able to add additional checks to
attempt to catch the problem next time around.
The problem was that the reported stack was showing secondary errors from
the memory cleanup. So we were looking in the wrong area for several days
until we got access to the machine and core. Then staring at the core for a
while until it occurred to me to do "info thread" and find the real problem.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
