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 "Quanlong Huang (Jira)" <ji...@apache.org> on 2023/06/26 07:54:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Quanlong Huang updated IMPALA-12102:
------------------------------------
Affects Version/s: Impala 4.1.1
Impala 4.2.0
Impala 4.1.0
Impala 3.4.1
Impala 3.4.0
Impala 3.3.0
Impala 4.0.0
Impala 3.2.0
> 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 3.2.0, Impala 4.0.0, Impala 3.3.0, Impala 3.4.0, Impala 3.4.1, Impala 4.1.0, Impala 4.2.0, Impala 4.1.1, Impala 4.1.2
> Reporter: Zhi Tang
> Assignee: Zhi Tang
> Priority: Major
> Fix For: Impala 4.3.0
>
> 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