ERROR ioctl(2) failed, EBADF

[Baymax09]

What happened?

when I used gemini cli，there are errors below：

ERROR ioctl(2) failed, EBADF

.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/node_modules/@lydell/node-pty/unixTerminal.js:243:13        
                                                                                                                           
240:         if (cols <= 0 || rows <= 0 || isNaN(cols) || isNaN(rows) || cols === Infinity || rows === Infinity) {         
241:             throw new Error('resizing must be done using positive cols and rows');                                    
242:         }                                                                                                             
243:         pty.resize(this._fd, cols, rows);                                                                             
244:         this._cols = cols;                                                                                            
245:         this._rows = rows;                                                                                            
246:     };                                                                                                                
                                                                                                                           
-UnixTerminal.resiz                                                                                                        
 e                                                                                                                         

(.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/node_modules/@lydell/node-pty/unixTerminal.
js:243:13)
-_ShellExecutionService.resizePt
y
(.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/chunk-BE42OOYM.js:32026
2:30)
- (.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/interactiveCli-RDMZS6KL.js:6529:31)
- commitHookEffectListMount
(.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:5260:30)
- commitPassiveMountOnFiber
(.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6282:29)
-recursivelyTraversePassiveMountEffec
ts
(.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:
6263:13)
- commitPassiveMountOnFiber
(.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6374:13)
-recursivelyTraversePassiveMountEffec
ts
(.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:
6263:13)
- commitPassiveMountOnFiber
(.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6374:13)
-recursivelyTraversePassiveMountEffec
ts
(.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:
6263:13)
An unexpected critical error occurred:Error: ioctl(2) failed, EBADF
at UnixTerminal.resize
(/home/baymax/.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/node_modules/@lydell/node-pty/unixTerminal.js:
243:13)
at _ShellExecutionService.resizePty
(file:///home/baymax/.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/chunk-BE42OOYM.js:320262:30)
at
file:///home/baymax/.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/interactiveCli-RDMZS6KL.js:6529:3
1
at commitHookEffectListMount
(file:///home/baymax/.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:5260:30)
at commitPassiveMountOnFiber
(file:///home/baymax/.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6282:29)
at recursivelyTraversePassiveMountEffects
(file:///home/baymax/.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6263:13)
at commitPassiveMountOnFiber
(file:///home/baymax/.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6374:13)
at recursivelyTraversePassiveMountEffects
(file:///home/baymax/.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6263:13)
at commitPassiveMountOnFiber
(file:///home/baymax/.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6374:13)
at recursivelyTraversePassiveMountEffects
(file:///home/baymax/.nvm/versions/node/v25.6.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6263:13)

What did you expect to happen?

this error should not happened，pls fix it， thank you

Client information

• CLI Version: 0.44.1
• Git Commit: b9b7416
• Session ID: cdac8908-f9b8-4b6d-8751-b2e76a334ccf
• Operating System: linux v25.6.0
• Sandbox Environment: no sandbox
• Model Version: auto
• Auth Type: oauth-personal
• Memory Usage: 360.5 MB
• Terminal Name: Unknown
• Terminal Background: #000000
• Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

No response

[gemini-cli]

Found possible duplicate issues:

• ERROR ioctl(2) failed, EBADF /home/mich #27538
• ioctl error #27517
• Crash on startup: ioctl(2) failed, EBADF in UnixTerminal.resize #27530
• Gemini cli crash again in this morning #27544
• ioctl error while running gemeni cli #21835
• gemini cli crash again #27506
• 0.44.0-preview.0 - Crash in the middle of processing a prompt node_modules/@google/gemini-cli/node_modules/@lydell/node-pty/unixTermina l.js:243:13 #27366
• from time to time gemini cli crashes #10617
• gemini cli has crashed #27504
• Critical Crash: ioctl(2) failed, EBADF during terminal resize or idle state #10523

If you believe this is not a duplicate, please remove the status/possible-duplicate label.

[raynerj-gdm]

Looks like this was fixed in #27461 which made it into the v0.45.0 nightly release.

You could try upgrading to the latest preview release npm install -g @google/gemini-cli@preview or monitor for when v0.45.0 is released.

[gemini-cli]

Effort Analysis:
The error ioctl(2) failed, EBADF (Bad File Descriptor) occurs in @lydell/node-pty when resize() is invoked on a PTY whose master file descriptor has already been closed. This typically happens during a race condition where a process exits and triggers destroyPtyProcess() in packages/core/src/services/shellExecutionService.ts, but the UI layer (ShellToolMessage.tsx) or an active effect still attempts a resize before the PID is removed from the activePtys map. Although ShellExecutionService.resizePty has logic to suppress EBADF and ESRCH, the stack trace shows the error escaping to the top-level CLI error handler. This suggests either a failure in the error detection logic (e.g., err.message or err.code mismatching in Node v25.6.0) or a re-throw in the React component layer that bypasses the core suppression. Debugging and fixing this requires deep familiarity with PTY lifecycles, cross-platform terminal behavior (Linux/Unix vs. Windows ConPTY), and robust synchronization of asynchronous state across the Core and CLI packages, which maps to the 'Platform-Specific Complexities (PTY/Signals)' category in the guidelines.

[Baymax09]

Looks like this was fixed in #27461 which made it into the v0.45.0 nightly release.

You could try upgrading to the latest preview release npm install -g @google/gemini-cli@preview or monitor for when v0.45.0 is released.

ttttttthanks bro, it does work after trying `npm install -g @google/gemini-cli'