FG
🛠️ Developer ToolsMicrosoft

Crash when running overnight

Freshabout 21 hours ago
Mar 14, 20260 views
Confidence Score56%
56%

Problem

Ubuntu 12.04, VSCode 0.10.1 Several times VS Code has become unresponsive overnight on the above configuration (locked). Here is the program output: [code block] This has never occurred with Atom.

Error Output

Error: channel closed

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
Unverified Fix
New Fix – Awaiting Verification

Implement Auto-Save and Disable Unused Extensions

Medium Risk

The issue of VS Code becoming unresponsive overnight on Ubuntu 12.04 is likely due to memory leaks or resource exhaustion caused by background processes or extensions running while the application is locked. The error 'channel closed' suggests that the communication channel between the main process and renderer has been disrupted, possibly due to excessive resource consumption.

Awaiting Verification

Be the first to verify this fix

  1. 1

    Enable Auto-Save

    Configure VS Code to automatically save files to prevent data loss and reduce memory usage from unsaved documents.

    json
    { "files.autoSave": "afterDelay", "files.autoSaveDelay": 1000 }
  2. 2

    Disable Unused Extensions

    Identify and disable any extensions that are not actively being used to reduce the load on the application and prevent potential crashes.

    bash
    code --disable-extensions
  3. 3

    Increase System Swap Space

    Increase the swap space on your Ubuntu system to provide additional memory resources for applications, which can help prevent crashes due to memory exhaustion.

    bash
    sudo fallocate -l 2G /swapfile && sudo chmod 600 /swapfile && sudo mkswap /swapfile && sudo swapon /swapfile
  4. 4

    Update VS Code to Latest Compatible Version

    Upgrade VS Code to a more recent version that may contain bug fixes and performance improvements that address stability issues.

    bash
    sudo apt-get update && sudo apt-get install code

Validation

To confirm the fix worked, monitor the application overnight after implementing the changes. Check for responsiveness and ensure that no error messages related to 'channel closed' appear in the developer console. Additionally, verify that auto-save is functioning as expected and that the application does not crash.

Sign in to verify this fix

Environment

Submitted by

AC

Alex Chen

2450 rep

Tags

vscodeideeditorbugverifiedfreeze-slow-crash-leak