eamodio / vscode-find-related

Finds files related to the current file based on user-defined configuration rules in VS Code
MIT License
30 stars 12 forks source link

fails and maxes out cpu #12

Closed diminutivesloop closed 5 years ago

diminutivesloop commented 5 years ago

Issue Type: Bug

Recently the extension has stopped working for me. When I trigger it I see the selection panel appear but it never shows any results and it eventually maxes-out my CPU. For reference I do have the following custom rulesets defined:

    {
      "name": "angular",
      "rules": [
        {
          "pattern": "(.*)\\.(?:ts|js)$",
          "locators": ["$1.html", "$1.scss", "$1.css"]
        },
        {
          "pattern": "(.*)\\.html$",
          "locators": ["$1.ts", "$1.js", "$1.scss", "$1.css"]
        }
        {
          "pattern": "(.*)\\.(scss|css)$",
          "locators": ["$1.ts", "$1.js", "$1.html"]
        }
      ]
    },
    {
      "name": "spec",
      "rules": [
        {
          "pattern": "(.*)\\.spec(\\..*)$",
          "locators": ["$1$2"]
        },
        {
          "pattern": "(.*)(\\..*)$",
          "locators": ["$1.spec$2"]
        }
      ]
    }

Extension version: 0.8.0 VS Code version: Code 1.29.1 (bc24f98b5f70467bc689abf41cc5550ca637088e, 2018-11-15T19:13:36.375Z) OS version: Windows_NT x64 6.1.7601

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-4930MX CPU @ 3.00GHz (8 x 3192)| |GPU Status|2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled| |Memory (System)|31.94GB (14.24GB free)| |Process Argv|| |Screen Reader|no| |VM|0%|
diminutivesloop commented 5 years ago

After updating to VSCode 1.30.0 this issue no longer manifests.

github-actions[bot] commented 1 year ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.