United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: 6592428 D3D: memory leak on exit because of pSyncQuery
6592428 : D3D: memory leak on exit because of pSyncQuery

Details
Type:
Bug
Submit Date:
2007-08-13
Status:
Closed
Updated Date:
2010-10-14
Project Name:
JDK
Resolved Date:
2007-08-21
Component:
client-libs
OS:
windows_xp
Sub-Component:
2d
CPU:
x86
Priority:
P3
Resolution:
Fixed
Affected Versions:
6u4
Fixed Versions:
6u10

Related Reports
Relates:

Sub Tasks

Description
When application exits the d3d pipeline is not released correctly, which
causes a large memory leak.

                                    

Comments
SUGGESTED FIX

http://sa.sfbay.sun.com/projects/java2d_data/6u4/6592428.0
                                     
2007-08-14
EVALUATION

There are two methods in the D3DContext class for resource disposal:
 - to release default-pool resources only (ReleaseDefPoolResources()) 
 - to release all resources (ReleaseContextResources()), inlcuding those in default pool

ReleaseContextResources is supposed to release all resources including
all default pool ones, but one resource (pSyncQuery) was missed, which
resulted in d3d devices not being released, causing a leak.

The fix is to call ReleaseDefPoolResources() from ReleaseContextResources()
to make sure all default pool resources are released.
                                     
2007-08-13



Hardware and Software, Engineered to Work Together