Gemini cli crash again in this morning

[mizukazu147]

What happened?

Gemini CLI still crashes with the following log.

ERROR ioctl(2) failed, EBADF

/home/kazuhito/.nvm/versions/node/v22.17.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.resize (/home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/node_modules/@lydell/node-pty/unixTerminal.js:243:13)
• _ShellExecutionService.resizePty (file:///home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/bundle/chunk-BE42OOYM.js:320262:30)
• (file:///home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/bundle/interactiveCli-RDMZS6KL.js:6529:31)
• commitHookEffectListMount (file:///home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:5260:30)
• commitPassiveMountOnFiber (file:///home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6282:29)
• recursivelyTraversePassiveMountEffects (file:///home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6263:13)
• commitPassiveMountOnFiber (file:///home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6374:13)
• recursivelyTraversePassiveMountEffects (file:///home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6263:13)
• commitPassiveMountOnFiber (file:///home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6374:13)
• recursivelyTraversePassiveMountEffects (file:///home/kazuhito/.nvm/versions/node/v22.17.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/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/node_modules/@lydell/node-pty/unixTerminal.js:243:13)
at _ShellExecutionService.resizePty (file:///home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/bundle/chunk-BE42OOYM.js:320262:30)
at file:///home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/bundle/interactiveCli-RDMZS6KL.js:6529:31
at commitHookEffectListMount (file:///home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:5260:30)
at commitPassiveMountOnFiber (file:///home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6282:29)
at recursivelyTraversePassiveMountEffects (file:///home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6263:13)
at commitPassiveMountOnFiber (file:///home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6374:13)
at recursivelyTraversePassiveMountEffects (file:///home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6263:13)
at commitPassiveMountOnFiber (file:///home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6374:13)
at recursivelyTraversePassiveMountEffects (file:///home/kazuhito/.nvm/versions/node/v22.17.0/lib/node_modules/@google/gemini-cli/bundle/chunk-VUERI7WB.js:6263:13)

What did you expect to happen?

I had expected the issue to be resolved today following my previous bug report, but it still hasn’t been resolved at all.

Client information

• CLI Version: 0.44.1
• Git Commit: b9b7416
• Session ID: c242da1e-b984-48ac-a99e-098e139918c5
• Operating System: linux v22.17.0
• Sandbox Environment: no sandbox
• Model Version: gemini-3-flash-preview
• Auth Type: oauth-personal
• Memory Usage: 267.9 MB
• Terminal Name: Unknown
• Terminal Background: #282c34
• Kitty Keyboard Protocol: Unsupported

Login information

Google account

Anything else we need to know?

When I asked gemini cli to recall my previous work, it crashed.

[gemini-cli]

Found possible duplicate issues:

• gemini cli crash again #27506
• Crash on startup: ioctl(2) failed, EBADF in UnixTerminal.resize #27530
• ERROR ioctl(2) failed, EBADF /home/mich #27538
• gemini cli has crashed #27504
• ioctl error #27517
• 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
• Critical Crash: ioctl(2) failed, EBADF during terminal resize or idle state #10523
• fatal error again!!!! #27516

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

[mizukazu147]

I reported a bug yesterday, but the issue has still not been resolved at all, and the exact same problem is occurring.

[gemini-cli]

Effort Analysis:
The crash Error: ioctl(2) failed, EBADF originates from node-pty's native UnixTerminal.resize call in unixTerminal.js:243, triggered by ShellExecutionService.resizePty in packages/core/src/services/shellExecutionService.ts. This occurs when the UI attempts to resize a pseudo-terminal whose file descriptor has already been closed (Bad File Descriptor) by the OS after the child process exited. While ShellExecutionService.resizePty contains a try-catch intended to swallow EBADF errors, the crash persists because of inconsistent rethrowing in calling components like ShellToolMessage.tsx (which rethrows any error message not matching a specific string) and the lack of defensive handling in BackgroundTaskDisplay.tsx. Diagnosing and fixing this requires complex state synchronization between the asynchronous process termination events and the synchronous Ink layout engine. Per the guidelines, issues involving node-pty, platform-specific shell behaviors (Linux ioctl), and intermittent race conditions that have survived previous fix attempts are categorized as effort/large due to high reproduction and verification overhead.

[tuapuikia]

what is your locale setting and language used?

[mizukazu147]

I restarted the Gemini CLI and asked why it had crashed. Gemini provided an explanation that matched that description, suggested a solution, and implemented it for me. The problem may now be resolved. I’ll keep an eye on it.