-
Notifications
You must be signed in to change notification settings - Fork 61
Description
Bug Report: Console window flashes briefly when git-ai.exe runs
Summary
The Atlascode extension spawns git-ai.exe processes that briefly display a visible console window before closing. This causes an annoying black window flash on the user's screen at regular intervals.
Environment
- OS: Windows 11 (Build 26100)
- VS Code: 1.107.1
- Atlascode Extension Version: 0.13.22 (rovodev)
- Extension Path:
%APPDATA%\Code\User\workspaceStorage\<id>\atlassian.atlascode\atlascode-rovodev-bin\0.13.22\
Steps to Reproduce
- Install the Atlascode extension in VS Code
- Connect to an Atlassian site (e.g., Jira/Bitbucket)
- Open a workspace with a Git repository
- Wait or work normally in VS Code
- Observe intermittent black console window flashing on screen
Expected Behavior
Background processes should run invisibly without displaying any console window.
Actual Behavior
A black console window briefly appears and disappears. The window flashes too quickly to read but is visually disruptive.
Technical Details
Using Process Monitor (Sysinternals), I captured the following process being spawned:
Process: git-ai.exe
Command Line: git-ai.exe stats-delta --json
Parent Process: Code.exe (VS Code)
Working Directory: C:\<project_path>
The git-ai.exe binary appears to be a PyInstaller-bundled Python application. When executed, it creates a console window because it was likely built without the --noconsole flag, or the parent process (VS Code/Atlascode) is not using the CREATE_NO_WINDOW process creation flag.
Additionally, atlassian_cli_rovodev.exe may exhibit similar behavior:
atlassian_cli_rovodev.exe serve <port> --xid rovodev-ide-vscode --site-url <site>
Workaround
Disabling the Atlascode extension stops the issue, but this removes all extension functionality.
Additional Notes
- The issue is intermittent and seems to occur when the extension polls for git status or repository changes
- The console window appears for approximately 50-200ms, making it difficult to capture without process monitoring tools
- This is a Windows-specific issue due to how console applications are handled
Attachments
Process Monitor logs available upon request.