Memory leaks in release critical code

Description

The ICU4JNI code version 3.4 has multiple occurrences of JNI calls to
GetPrimitiveArrayCritical and ReleasePrimitiveArrayCritical (see
converter/ConverterInterface.c and normalizer/NormalizationInterface.c).

ICU4JNI frequently uses release mode JNI_COMMIT alone, which is a checkpoint
copy back of data to the java array and is not required to release the primitive
array memory storage. On VMs that copy the data this introduces a significant
memory leak.

According to JNI the mode flag for copying back the data and releasing the
memory is mode 0.

(Note that on VMs that do not copy the data, the modes 0 and JNI_COMMIT are
equally meaningless and therefore this leak goes undetected.)

Activity

Show:
TracBot
July 1, 2018, 12:06 AM
Trac Comment by auditor—1970-01-01T01:21:49.000Z
  • Wed Sep 14 08:18:23 2005 weiv changed notes2: assign: "" to "ram", priority: "" to "critical", target: "UNSCH" to "3.6",

  • Fri Sep 16 08:05:33 2005 grhoten moved from incoming to others

  • Mon Sep 26 12:12:59 2005 ram changed notes2: review: "" to "srl",

  • Tue Jul 18 13:55:05 2006 srl moved from others to fixed

  • Sun Oct 22 07:30:53 2006 grhoten moved from fixed to closed

Fixed

Assignee

TracBot

Reporter

TracBot

Components

Labels

None

Reviewer

None

Priority

blocks-release

Time Needed

None

Fix versions