-
Enhancement
-
Resolution: Fixed
-
P4
-
21
-
b07
-
os_x
-
Fix failed
This will track an improvement of JDK-8291060 "OPEN_MAX is no longer the max limit on macOS >= 10.6 for RLIMIT_NOFILE" taking into the account what we learned from JDK-8299258 "Launching ksh (shell) from within Java through ProcessBuilder causes ksh process to crash with EXC_BAD_ACCESS (SIGSEGV)"
The reason I would like to see this properly fixed, is that I would like to see parity of macOS and Linux when it comes to process/file count as it might be important to the os behavior under MACH5 and explain the issues we see on macOS compared to other platforms. This is just one tiny piece in a big puzzle and I would like to know that it's in the right spot.
The reason I would like to see this properly fixed, is that I would like to see parity of macOS and Linux when it comes to process/file count as it might be important to the os behavior under MACH5 and explain the issues we see on macOS compared to other platforms. This is just one tiny piece in a big puzzle and I would like to know that it's in the right spot.
- is cloned by
-
JDK-8324577 [REDO] - [IMPROVE] OPEN_MAX is no longer the max limit on macOS >= 10.6 for RLIMIT_NOFILE
- Resolved
- relates to
-
JDK-8324578 [BACKOUT] [IMPROVE] OPEN_MAX is no longer the max limit on macOS >= 10.6 for RLIMIT_NOFILE
- Closed
-
JDK-8324668 JDWP process management needs more efficient file descriptor handling
- Resolved
-
JDK-8299258 Launching ksh (shell) from within Java through ProcessBuilder causes ksh process to crash with EXC_BAD_ACCESS (SIGSEGV)
- Closed
-
JDK-8291060 OPEN_MAX is no longer the max limit on macOS >= 10.6 for RLIMIT_NOFILE
- Closed
(2 links to)