You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Alan M. Carroll (JIRA)" <ji...@apache.org> on 2016/09/06 17:00:28 UTC

[jira] [Updated] (TS-4503) MachineFatal should shutdown without cleanup

     [ https://issues.apache.org/jira/browse/TS-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan M. Carroll updated TS-4503:
--------------------------------
    Assignee: Syeda Persia Aziz  (was: Susan Hinrichs)

> MachineFatal should shutdown without cleanup
> --------------------------------------------
>
>                 Key: TS-4503
>                 URL: https://issues.apache.org/jira/browse/TS-4503
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Susan Hinrichs
>            Assignee: Syeda Persia Aziz
>             Fix For: 7.0.0
>
>
> When MachineFatalClass::raise() is called, it prints a message to the log and then calls exit.  exit causes memory cleanup to be called.  But if we are in such bad state that MachineFatal is called, it is quite likely that memory is messed up.
> We saw a crash where MachineFatal is called in thread 84.  This stack has the real error.  But the stack that got reported was on thread 1 in class destructor logic.  It would have been better if ATS failed immediately and the stack on thread 84 was reported.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)