-
Bug
-
Resolution: Fixed
-
P3
-
1.3.1_19
-
b01
-
generic
-
generic
(A further problem demonstrated with the testcase in 6447127.)
CJavaDispatch objects keep a reference count, but do
not guard updates from being accessed in multiple
threads concurrently.
Losing track of CJavaDispatch objects creates memory
leaks as Java global references (to JavaObjectInterface
java objects) are kept alive.
Using Critical Sections as already used in other parts
of the class is preferable.
CJavaDispatch objects keep a reference count, but do
not guard updates from being accessed in multiple
threads concurrently.
Losing track of CJavaDispatch objects creates memory
leaks as Java global references (to JavaObjectInterface
java objects) are kept alive.
Using Critical Sections as already used in other parts
of the class is preferable.
- relates to
-
JDK-6447127 Beans using JPanel show memory leak when used with 1.3.1 ActiveX bridge
- Resolved