Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 48AA61868F for ; Thu, 30 Jul 2015 12:11:04 +0000 (UTC) Received: (qmail 13075 invoked by uid 500); 30 Jul 2015 12:11:03 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 13018 invoked by uid 500); 30 Jul 2015 12:11:03 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 13007 invoked by uid 99); 30 Jul 2015 12:11:03 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jul 2015 12:11:03 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 87A6CE6B7E; Thu, 30 Jul 2015 12:11:03 +0000 (UTC) From: kansal To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: Coverity Issue: Resource Leak fixed Content-Type: text/plain Message-Id: <20150730121103.87A6CE6B7E@git1-us-west.apache.org> Date: Thu, 30 Jul 2015 12:11:03 +0000 (UTC) Github user kansal commented on the pull request: https://github.com/apache/cloudstack/pull/643#issuecomment-126301540 @DaanHoogland It was the issue that was reported by our internal coverity. The issue reported is: "noescape: Resource 'in' is not closed or saved in readObject. CID 17897: Resource leak (RESOURCE_LEAK). leaked_resource: Variable in going out of scope leaks the resource it refers to." --- 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 infrastructure@apache.org or file a JIRA ticket with INFRA. ---