Worker died unexpectedly errors in 5.2.0

[onlywei]

Occasionally I get "Worker died unexpectedly" errors when working with v5.2.0. My console says this:

ESLint Worker Info Objectstderr: "(55920,0x7fff741de300) malloc: *** error for object 0x7ff461e3f340: pointer being freed was not allocated↵*** set a breakpoint in malloc_error_break to debug↵"stdout: "eslint [options] file.js [file.js] [dir]↵↵Basic configuration:↵  -c, --config path::String   Use configuration from this file or shareable config↵  --no-eslintrc               Disable use of configuration from .eslintrc↵  --env [String]              Specify environments↵  --ext [String]              Specify JavaScript file extensions - default: .js↵  --global [String]           Define global variables↵  --parser String             Specify the parser to be used - default: espree↵↵Caching:↵  --cache                     Only check changed files - default: false↵  --cache-file path::String   Path to the cache file. Deprecated: use --cache-location - default: .eslintcache↵  --cache-location path::String  Path to the cache file or directory↵↵Specifying rules and plugins:↵  --rulesdir [path::String]   Use additional rules from this directory↵  --plugin [String]           Specify plugins↵  --rule Object               Specify rules↵↵Ignoring files:↵  --ignore-path path::String  Specify path of ignore file↵  --no-ignore                 Disable use of .eslintignore↵  --ignore-pattern String     Pattern of files to ignore (in addition to those in .eslintignore)↵↵Using stdin:↵  --stdin                     Lint code provided on <STDIN> - default: false↵  --stdin-filename String     Specify filename to process STDIN as↵↵Handling warnings:↵  --quiet                     Report errors only - default: false↵  --max-warnings Number       Number of warnings to trigger nonzero exit code - default: -1↵↵Output:↵  -o, --output-file path::String  Specify file to write report to↵  -f, --format String         Use a specific output format - default: stylish↵  --no-color                  Disable color in piped output↵↵Miscellaneous:↵  --init                      Run config initialization wizard - default: false↵  --fix                       Automatically fix problems↵  --debug                     Output debugging information↵  -h, --help                  Show help↵  -v, --version               Outputs the version number↵"__proto__: Object

ESLint Worker Info Objectstderr: "(57299,0x7fff741de300) malloc: *** error for object 0x7fd63bd1bf40: pointer being freed was not allocated↵*** set a breakpoint in malloc_error_break to debug↵"stdout: ""__proto__: Object

[steelbrain]

Yeah it's an electron (Atom's core) issue, this has been fixed in latest beta

[ebramanti]

@steelbrain So this should be fixed in next release of Atom?

Edit: This made things clearer.