[
https://issues.apache.org/jira/browse/TS-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312966#comment-15312966
]
ASF GitHub Bot commented on TS-4503:
------------------------------------
GitHub user shinrich opened a pull request:
https://github.com/apache/trafficserver/pull/694
TS-4503: Cause MachineFatal to terminate process without attempting m…
…emory cleanup.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shinrich/trafficserver ts-4503
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/694.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #694
----
commit 465abad2f55fcac2f98af46ce3800ed8be43f36a
Author: Susan Hinrichs <[email protected]>
Date: 2016-06-02T20:04:37Z
TS-4503: Cause MachineFatal to terminate process without attempting memory
cleanup.
----
> 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: Susan Hinrichs
> 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)
