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

Fix for Critical Issue #2: Spawning 100% CPU Processes that Never Exit #3

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Commits on Jun 6, 2019

  1. Fix for critical bug jrieken#2: Spawning many node.exe processes whic…

    …h use 100% of a CPU core each and never terminate, even days later.
    
    Added options (which can change hard-coded or expose as user settings ideally) for reducing CPU priority
    Note: After pull, run npm install to install new dependencies added to package.json
    Git ignored package-lock.json
    Changed extension category to new "Programming Languages" instead of "Programming" to fix warning for that
    TODO: Expose settings under //Settings: section in search.js as extension settings to control timeout, CPU priority, etc.
    TODO: Requires further testing to ensure doesn't break spawning the node.exe for nak file search proccess and that always exits even if Ctrl-Click / Go to Definition for If or Var keywords in large projects with many node modules, for example.
    PowerWeb5 committed Jun 6, 2019
    Configuration menu
    Copy the full SHA
    a33c797 View commit details
    Browse the repository at this point in the history
  2. Updated version, bumped to 1.0.0 since is fairly stable and unlikely …

    …to change much further soon.
    
    Mentioned TypeScript in extension/package description as well.
    PowerWeb5 committed Jun 6, 2019
    Configuration menu
    Copy the full SHA
    1aca2b3 View commit details
    Browse the repository at this point in the history