JDK-4653090 : (ch) AbstractInterruptibleChannel creates excessive garbage
- Type: Bug
- Component: core-libs
- Sub-Component: java.nio
- Affected Version: 1.4.0,5.0u3
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: linux_redhat_3.0,windows_2000
- CPU: generic,x86
- Submitted: 2002-03-14
- Updated: 2005-10-29
- Resolved: 2005-10-29
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| Other | JDK 6 |
|---|---|
| 5.0u8Fixed | 6 b59Fixed  |
Related Reports
|
Relates :
|
Description
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) ======================================================================
Comments
|