You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/05/04 19:39:00 UTC

[jira] [Commented] (IMPALA-12102) The JniUtil::GetJniExceptionMsg() method has the risk of memory leakage when handling JNI exceptions

    [ https://issues.apache.org/jira/browse/IMPALA-12102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719510#comment-17719510 ] 

ASF subversion and git services commented on IMPALA-12102:
----------------------------------------------------------

Commit e9f5127785ea82786650ee56a50ac4358fbe5466 in impala's branch refs/heads/master from ttttttz
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=e9f512778 ]

IMPALA-12102: Avoid memory leaks in the handling of JNI exceptions

During the processing of JNI Exceptions, some local references
were not released in a timely manner, which may lead to memory
leaks in the JVM.

Testing:
- Manually verified that the memory leak doesn't occur in the
  local development environment.

Change-Id: I4843df07dd0f9d3dc237f91db4ec00721ebbd680
Reviewed-on: http://gerrit.cloudera.org:8080/19810
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>


> The JniUtil::GetJniExceptionMsg() method has the risk of memory leakage when handling JNI exceptions
> ----------------------------------------------------------------------------------------------------
>
>                 Key: IMPALA-12102
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12102
>             Project: IMPALA
>          Issue Type: Bug
>    Affects Versions: Impala 4.1.2
>            Reporter: Zhi Tang
>            Assignee: Zhi Tang
>            Priority: Major
>         Attachments: image-2023-04-26-20-46-55-583.png, image-2023-04-26-20-47-56-620.png
>
>
> When the JniUtil::GetJniExceptionMsg() method handles the JNI exceptions, the reference to the jstring object is not released in time, which may cause a memory leak problem.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org