-
Bug
-
Resolution: Fixed
-
P4
-
1.4.0, 5.0u3
-
b59
-
generic, x86
-
linux_redhat_3.0, windows_2000
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2133600 | 5.0u8 | Xueming Shen | P4 | Resolved | Fixed | b01 |
Name: nt126004 Date: 03/14/2002
FULL PRODUCT VERSION :
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)
FULL OPERATING SYSTEM VERSION :
Microsoft Windows 2000 [Version 5.00.2195]
A DESCRIPTION OF THE PROBLEM :
AbstractInterruptibleChannel.blockedOn() invokes a method
via reflection, requiring the allocation of an Object array
for every invocation. This causes excessive garbage
creation in high-activity NIO-based applications because
the blockedOn() method is invoked twice for every call to
select(), read() or write().
This bug can be reproduced always.
(Review ID: 144078)
======================================================================
FULL PRODUCT VERSION :
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)
FULL OPERATING SYSTEM VERSION :
Microsoft Windows 2000 [Version 5.00.2195]
A DESCRIPTION OF THE PROBLEM :
AbstractInterruptibleChannel.blockedOn() invokes a method
via reflection, requiring the allocation of an Object array
for every invocation. This causes excessive garbage
creation in high-activity NIO-based applications because
the blockedOn() method is invoked twice for every call to
select(), read() or write().
This bug can be reproduced always.
(Review ID: 144078)
======================================================================
- backported by
-
JDK-2133600 (ch) AbstractInterruptibleChannel creates excessive garbage
- Resolved
- relates to
-
JDK-6244548 (ch) race in AbstractInterruptibleChannel.blockedOn/initBlockedOn
- Closed