If the code that is passed to linter.verify contains \\n in a string, and no-useless-escape is enabled, the function hangs and cpu usage hits 100%.
Passing the exact same code through eslint (7.32.0) does not.
The following code can be used to reproduce:
const Linter = require('eslint4b');
const linter = new Linter();
var defaultConfig = {
"env": {
"es2021": true
},
"parserOptions": {
"ecmaVersion": 12
},
"rules": {
"no-useless-escape": "error",
}
}
linter.verify('const a = "\\n"', defaultConfig)