Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Amazon Q Causes Visual Studio Code to Crash When Joining Microsoft Live Share on macOS #6485

Open
scanianick opened this issue Feb 3, 2025 · 3 comments
Labels
bug We can reproduce the issue and confirmed it is a bug.

Comments

@scanianick
Copy link

Problem

When joining a Microsoft Live Share session, Visual Studio Code crashes if Amazon Q is enabled. The current workaround is to disable Amazon Q.

I have confirmed this issue with a colleague running the same versions of VS Code, Live Share, and Amazon Q, but it works fine for another colleague using macOS Darwin arm64 24.1.0 with identical software versions. Based on my experience, this issue has persisted across multiple macOS and Amazon Q versions.

Steps to reproduce the issue

Expected behavior

System details (run AWS: About and/or Amazon Q: About)

OS: Darwin arm64 24.2.0
Visual Studio Code extension host: 1.96.4
AWS Toolkit: 3.44.0
node: 20.18.1
electron: 32.2.6

OS: Darwin arm64 24.2.0
Visual Studio Code extension host: 1.96.4
Amazon Q: 1.45.0
node: 20.18.1
electron: 32.2.6

Microsoft Live Share version (ms-vsliveshare.vsliveshare):
1.0.5948

@scanianick scanianick added the bug We can reproduce the issue and confirmed it is a bug. label Feb 3, 2025
@jpinkney-aws
Copy link
Contributor

Hi, are there any VSCode relevant logs that you can share with us to help diagnose the issue? Is the problem that the extension host is crashing? Or Live Share won't work at all?

@scanianick
Copy link
Author

So basically, it works for a short time but usually crashes within a minute, displaying this popup.

Image

Since the window crash it is hard to get the logs within Visual Studio Code for Amazon Q extension. But I check the main log.

tail -f main.log
2025-02-03 15:34:01.132 [info] Extension host with pid 53690 exited with code: 0, signal: unknown.
2025-02-03 15:35:39.164 [info] Extension host with pid 38709 exited with code: 0, signal: unknown.
2025-02-03 15:36:31.873 [error] CodeWindow: renderer process gone (reason: crashed, code: 5)
2025-02-03 15:36:32.159 [info] Extension host with pid 57434 exited with code: 0, signal: unknown.
2025-02-03 15:36:47.576 [info] Extension host with pid 38710 exited with code: 0, signal: unknown.
2025-02-03 15:37:18.125 [info] Extension host with pid 59612 exited with code: 0, signal: unknown.
2025-02-03 15:37:27.111 [info] Extension host with pid 61796 exited with code: 0, signal: unknown.
2025-02-03 15:37:34.992 [info] Extension host with pid 62035 exited with code: 0, signal: unknown.
2025-02-03 15:38:08.846 [error] CodeWindow: renderer process gone (reason: crashed, code: 5)
2025-02-03 15:38:09.135 [info] Extension host with pid 62226 exited with code: 0, signal: unknown.

@scanianick
Copy link
Author

Let me know if you have any other relevant log to look for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug We can reproduce the issue and confirmed it is a bug.
Projects
None yet
Development

No branches or pull requests

2 participants