Crash gemini cli.

[TuanAnhMS]

What happened?

ERROR ioctl(2) failed, EBADF

/home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/node_modules/@lydell/node-pty/unixTerminal.j
s: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.resi
ze (/home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/node_modules/@lydell/node-
pty/unixTerminal.js:243:13)
-_ShellExecutionService.res
izePty (file:///home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/bundle/chu
nk-BE42OOYM.js:320262:30)

(file:///home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/bundle/interactiveCli-RDMZS6KL.js:6
529:31)
-commitHookEffectListMo
unt (file:///home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/bundle/chunk-V
UERI7WB.js:5260:30)
-commitPassiveMountOnFi
ber (file:///home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/bundle/chunk-V
UERI7WB.js:6282:29)
-recursivelyTraversePassiveMoun
tEffects (file:///home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/bundle
/chunk-VUERI7WB.js:6263:13)
-commitPassiveMountOnFi
ber (file:///home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/bundle/chunk-V
UERI7WB.js:6374:13)
-recursivelyTraversePassiveMoun
tEffects (file:///home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/bundle
/chunk-VUERI7WB.js:6263:13)
-commitPassiveMountOnFi
ber (file:///home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/bundle/chunk-V
UERI7WB.js:6374:13)
-recursivelyTraversePassiveMoun
tEffects (file:///home/oneadmin/.nvm/versions/node/v24.15.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/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/node_modules/@lydell/node-pty/unixTerminal.js:243:13)
at _ShellExecutionService.resizePty (file:///home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/bundle/chunk-BE42OOYM.js:320262:30)
at file:///home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/bundle/interactiveCli-RDMZS6KL.js:6529:31
at commitHookEffectListMount (file:///home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:5260:30)
at commitPassiveMountOnFiber (file:///home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6282:29)
at recursivelyTraversePassiveMountEffects (file:///home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6263:13)
at commitPassiveMountOnFiber (file:///home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6374:13)
at recursivelyTraversePassiveMountEffects (file:///home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6263:13)
at commitPassiveMountOnFiber (file:///home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6374:13)
at recursivelyTraversePassiveMountEffects (file:///home/oneadmin/.nvm/versions/node/v24.15.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6263:13)

What did you expect to happen?

Just run my server and crash dead. always happen.

Client information

• CLI Version: 0.44.1
• Git Commit: b9b7416
• Session ID: 5b162933-936c-443c-b2bd-8b5add37a6aa
• Operating System: linux v24.15.0
• Sandbox Environment: no sandbox
• Model Version: auto
• Auth Type: oauth-personal
• Memory Usage: 291.5 MB
• Terminal Name: xterm.js(6.1.0-beta.213)
• Terminal Background: #252526
• Kitty Keyboard Protocol: Supported
• IDE Client: VS Code

Login information

Google AI Pro.

Anything else we need to know?

old seastar platform may affect network and system call.

[gemini-cli]

Found possible duplicate issues:

• Crash on startup: ioctl(2) failed, EBADF in UnixTerminal.resize #27530
• ERROR ioctl(2) failed, EBADF /home/mich #27538
• ioctl error #27517
• Gemini cli crash again in this morning #27544
• ERROR ioctl(2) failed, EBADF #27546
• gemini cli crash again #27506
• gemini cli has crashed #27504
• from time to time gemini cli crashes #10617
• 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
• ioctl error while running gemeni cli #21835

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

[gemini-cli]

This is a critical crash caused by a race condition in node-pty's resize operation when the underlying shell process exits, resulting in an EBADF (Bad File Descriptor) error.

This issue reports a terminal resizing crash. Please provide more specific steps to reproduce the issue and details about your terminal environment.

Effort Analysis:
The crash occurs in node-pty/unixTerminal.js during an ioctl system call when ShellExecutionService.resizePty in packages/core/src/services/shellExecutionService.ts is called on a terminal that has just exited. This is a classic race condition between the React-driven UI (specifically ShellToolMessage.tsx and BackgroundTaskDisplay.tsx which call resizePty in useEffect) and the asynchronous lifecycle of the spawned shell process. Resolving this requires robust, platform-specific error handling and synchronization across packages/core and packages/cli (including global exception handlers in packages/cli/index.ts) to safely suppress non-critical PTY errors. Given that it involves low-level PTY/Signals behavior and platform-specific complexities (Unix ioctl), it is categorized as effort/large according to the triage guidelines.

[galdawave]

Hi, we believe that this was fixed by #27496 which should be in the latest, stable. Will close this out, if this is still occurring please tag me and i'll reopen.