We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 1464 - memleak in Android_JNI_ExceptionOccurred
Summary: memleak in Android_JNI_ExceptionOccurred
Status: RESOLVED INVALID
Alias: None
Product: SDL
Classification: Unclassified
Component: *don't know* (show other bugs)
Version: HG 2.0
Hardware: All Android (All)
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-07 14:06 UTC by Martin Gerhardy
Modified: 2012-04-07 14:11 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Gerhardy 2012-04-07 14:06:10 UTC 
According to http://publib.boulder.ibm.com/infocenter/javasdk/v5r0/index.jsp?topic=%2Fcom.ibm.java.doc.diagnostics.50%2Fdiag%2Funderstanding%2Fjni_refs.html the jclass references must be deleted, too

        mEnv->DeleteLocalRef(classClass);
        mEnv->DeleteLocalRef(exceptionClass);
        mEnv->DeleteLocalRef(exception);
        mEnv->DeleteLocalRef(exceptionName);
Comment 1 Martin Gerhardy 2012-04-07 14:11:29 UTC 
forget it - Android_JNI_ExceptionOccurred is always secured by LocalReferenceHolder::init calls