eclipse-theia/theia

Issue : Unhandled Promise Rejection & Orphaned Disk Space Leak in rimrafMove on File Deletion 1. Header Information Title: [Bug] [filesystem] Unhandled Promise Rejection and orphaned temporary files in DiskFileSystemProvider.rimrafMove Affected Package: @theia/filesystem Affected File: packages/filesystem/src/node/disk-file-system-provider.ts Affected Lines: Lines 534–550 Severity: Medium-High (Process Stability / Resource Leak) 2. Problem Description When recursively deleting directories, DiskFileSystemProvider.rimrafMove moves the directory to os.tmpdir() and then initiates asynchronous deletion via this.rimrafUnlink(pathInTemp) without awaiting or attaching a .catch() rejection handler. If rimrafUnlink encounters permission errors (EACCES/EPERM) or locked files during deletion: An Unhandled Promise Rejection occurs, which in modern Node.js environments can terminate the process or trigger critical alert thresholds. The renamed files remain permanently abandoned inside os.tmpdi

Issue : Function Coercion Disabling Priority Registration & Fatal Process Crash on File Read in Mini Browser 1. Header Information Title: [Bug] [mini-browser] Relational comparison of handler priority functions breaks priority ordering & uncaught throw in fs.readFile callback crashes backend process Affected Package: @theia/mini-browser Affected File: packages/mini-browser/src/node/mini-browser-endpoint.ts Affected Lines: Lines 91–100, 244–253, and 282–291 Severity: High (Extensibility Mechanism Failure / Backend Crash) 2. Problem Description In MiniBrowserEndpoint.onStart(), handler priority comparison compares the function references (handler.priority > existingHandler.priority) rather than calling the methods (handler.priority() > existingHandler.priority()). This causes the condition to evaluate to false always, completely preventing custom extensions from overriding default file preview handlers. In ImageHandler.respond and PdfHandler.respond, errors encountered when rea

Issue : Broken User Cancellation on Windows & Main-Thread Freezing in AI Terminal 1. Header Information Title: [Bug] [ai-terminal] Command cancellation on Windows fails to report canceled state and blocks Node.js event loop with execSync Affected Package: @theia/ai-terminal Affected File: packages/ai-terminal/src/node/shell-execution-server-impl.ts Affected Lines: Lines 85–113 and Lines 155–184 Severity: High (Cross-Platform Execution Defect / UI Responsiveness) 2. Problem Description The ShellExecutionServerImpl provides shell command execution for autonomous AI tools and chat agents. When a user or agent cancels an in-flight command via cancel(executionId): On Windows, the execution server fails to report canceled: true and instead returns a generic command error with exit code. Terminating child process trees on Windows uses execSync (taskkill /pid ... /T /F), synchronously blocking the entire Theia Node.js backend server. 3. Root Cause Analysis Look at lines 85–113 in p

Issue : Permanent Hanging Promise & RPC Memory Leak in SCM Extension Host 1. Header Information Title: [Bug] [plugin-ext] Permanent Promise deadlock and RPC protocol memory leak in ScmExt due to invalid new Promise() executor Affected Package: @theia/plugin-ext Affected File: packages/plugin-ext/src/plugin/scm.ts Affected Lines: Lines 451–459 and Lines 1018–1027 Severity: Critical (Deadlock / Memory Leak / Broken Extension Host Protocol) 2. Problem Description In the Source Control Management (SCM) extension implementation (ScmExtImpl), two critical methods responsible for executing SCM commands and providing quick diff original resources instantiate promises using new Promise(() => ...) without declaring or invoking resolve or reject. Per the ECMAScript 2015+ specification (§27.2.3.1), the return value of an executor passed to new Promise is completely ignored. Because neither resolve nor reject is ever called, the returned Promise remains in the <pending> state forever. 3. R

Feature Description: Now that plugins run in browser-only (#17966), @theia/plugin-metrics tries to send its metrics to the backend, which doesn't exist there. The browser-only example logs a Request 'setMetrics' on service '/services/plugin-ext/metrics' is unavailable: no backend in frontend-only mode error several times on every load. @theia/plugin-metrics should get a frontendOnly module that binds a no-op PluginMetrics, same as #17966 did for VSXEnvironment in @theia/vsx-registry.