Some information (https://github.com/atom/atom/issues/17060 https://github.com/atom/atom/issues/17060) indicates that the problem is related to `atom.config.set

Some information (https://github.com/atom/atom/issues/17060 https://github.com/atom/atom/issues/17060) indicates that the problem is related to `atom.config.set`. `linter-ui-default` is one plugin that triggers it. So maybe it's not a bug of `linter-ui-default` after all. Sorry dear innocent man, my judgement is not always on point :)