Skip to content

Liveshare logs are massive and took a long time to generate #3516

@connor4312

Description

@connor4312

Describe what happened: Exporting logs took about 15 minutes and created a 1.8 GB zip file

What was your system configuration?
Product and Version [VS/VSCode]: VS Code, 1.46.0-insider 2020-05-11T10:00:12.459Z
OS Version[macOS/Windows]: Windows_NT x64 10.0.18363
Live Share Extension Version: v1.0.2106
Target Platform or Language [e.g. Node.js]: N/A

Steps to Reproduce / Scenario:

  1. Start a live share session. I started debugging a "hello world" node.js process with our new debugger Parent/child debug sessions are not preserved #3515
  2. Run the "Export logs" command
  3. The extension host took about 15 minute with very high disk read usage
  4. It eventually produced a 1.8GB zip file--I guess, after seeing CPU usage and i/o drop back down. While VS Code was open, it held onto it (reported by Unlocker) and I could not open the folder. After closing VS Code. Windows reported it as corrupt. 7zip was able to open it, but could not extract the log file (and honestly not sure I have enough disk space to decompress whatever 1.8GB of text represents!)

Please attach logs to this issue:

I can upload the corrupt zip somewhat on request.

Screenshots

The disk i/o was almost all reads:

Looks like a whole lot of filesystem reads, profile: https://memes.peet.io/img/CPU-20200511T174437.212Z.cpuprofile

Windows reports it as corrupt:

7zip gave more info:

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions