JDK-6936168 : Recent fix for unmapping stack guard pages doesn't close /proc/self/maps
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: hs18
- Priority: P2
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2010-03-18
- Updated: 2012-10-08
- Resolved: 2010-04-06
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.
| JDK 6 | JDK 7 | Other |
|---|---|---|
| 6-poolResolved | 7Fixed  |
hs18Fixed |
Related Reports
|
Duplicate :
|
Description
On 03/18/2010 09:10 AM, Andreas Kohn wrote: With this change I seem to hit the limit on the number of open files. Looking through it, shouldn't get_stack_bounds() close the FILE* it opened? For example an eclipse process shows this: /proc/20662/fd>ls -al |grep -c /proc/20662/maps 1917
Comments
|