Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Atom becomes unresponsive after opening several JS files #1266

Open
kaiyoma opened this issue May 12, 2019 · 1 comment
Open

Atom becomes unresponsive after opening several JS files #1266

kaiyoma opened this issue May 12, 2019 · 1 comment

Comments

@kaiyoma
Copy link

kaiyoma commented May 12, 2019

Issue Type

Bug

Issue Description

If I open a bunch (between 10 and 20) JS files all at once in Atom, the program becomes unresponsive and after a few moments asks me if I want to force close or wait. Waiting for the program to become responsive never seems to work and Atom has to be killed.

This problem seems to be related to the linter-eslint package. If I disable only linter-eslint and try again, everything works as expected. If I re-enable the package and try again, Atom becomes unresponsive. Also, if I try opening a bunch of non-JS files (with all packages enabled), everything works fine.

Bug Checklist

Atom version: 1.36.1
linter-eslint version: 8.5.5
ESLint version: 5.16.0
Hours since last Atom restart: 0.1
Platform: win32
Using local project ESLint from: ...\node_modules\eslint
Current file's scopes: [
  "source.json",
  "meta.structure.dictionary.json",
  "meta.structure.dictionary.value.json",
  "meta.structure.dictionary.json",
  "meta.structure.dictionary.key.json",
  "string.quoted.double.json",
  "punctuation.definition.string.end.json"
]
linter-eslint configuration: {
  "scopes": [
    "source.js",
    "source.jsx",
    "source.js.jsx",
    "source.flow",
    "source.babel",
    "source.js-semantic"
  ],
  "lintHtmlFiles": false,
  "autofix": {
    "fixOnSave": false,
    "ignoreFixableRulesWhileTyping": false,
    "rulesToDisableWhileFixing": []
  },
  "global": {
    "useGlobalEslint": false,
    "eslintrcPath": "",
    "globalNodePath": ""
  },
  "disabling": {
    "disableWhenNoEslintConfig": true,
    "rulesToSilenceWhileTyping": []
  },
  "advanced": {
    "disableEslintIgnore": false,
    "disableFSCache": false,
    "showRuleIdInMessage": true,
    "eslintRulesDirs": [],
    "localNodeModules": ""
  }
}
@kaiyoma
Copy link
Author

kaiyoma commented May 12, 2019

If I disable linter-eslint, open my ~20 files, then re-enable the linter, everything seems to be fine. This issue seems to happen only when the linter is trying to lint a large number of files that are being opened simultaneously.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants