| Previous | Next |
| EBFONT | ENOTRECOVERABLE |
ETOOMANYREFS
This page examines too many references for a Darwin socket splice-style operation. The networking path could not create another reference required by the operation.
Meaning on this platform
Darwin BSD system-call handling: the returned status belongs to Darwin errno and should be decoded with the exact SDK or XNU header used by the target. Darwin extensions and legacy STREAMS names can differ in availability or numbering on other UNIX-like systems. The wording attached to this errno is a clue to the original interface, not proof that a similarly named modern subsystem returned it.
Facts that identify the owner
| Evidence | Question it answers |
|---|---|
| Socket family/type, reference or queued-right count, process limits, peer, and lifecycle trace. | Ties the failed operation to one live API object instead of a translated message. |
| Darwin errno value and the SDK/XNU header version used to decode it. | Shows whether the error arose in the caller ABI, wrapper, or provider. |
| First syscall/ioctl return plus process, thread, and object generation. | Preserves the first boundary before errno can be overwritten. |
| Known-good object of the same class on the same macOS build. | Provides a same-platform known-good comparison. |
Verification sequence
- Close one controlled duplicate/reference and repeat once. Repeat the original operation after the control so the result remains relevant to the original failure.
- Capture errno immediately and compare the paired return value. Keep the binary, header ABI, and provider fixed.
- Repeat with one controlled object while keeping identity and sandbox unchanged. Record whether the control reaches the same syscall or runtime boundary as the failing run.
Cross-platform caution
| Tempting assumption | Safer interpretation |
|---|---|
| The English phrase is assumed to be portable | ETOOMANYREFS belongs to Darwin BSD system-call handling; verify the target headers and returning API before applying another platform's errno table |
| A retry succeeded and erased the original evidence | The retry can replace the original errno with a different state; preserve the first call, numeric value, and object generation beforehand |
A narrow remedy
Targeted correction. Release leaked socket references and bound concurrency; do not treat it as a generic open-file limit without evidence.
Regression proof. Reference count returns after close and the operation remains stable at expected concurrency.
Technical references
- Apple XNU: errno.H — defines the status namespace used.
- Apple: intro(2) system-call errors — documents the API or lifecycle boundary behind this errno.
- Apple OSS: XNU source — provides ABI, implementation, or protocol context.
- The Open Group: errno.H — supports the portability and verification limits.
Looking for a different code? Search another status or error code.