Can you run your
config.jsonthrough a json validator and paste back confirmation there's not a typo?If your file is valid, check the semantics of the settings.
There was a bug in error message output that we didn't catch until we started seeing reports like this. So you get this cryptic then when the json isn't valid. It's fixed on master and will be in for the next release.
@eric could we have your help tracking that an invalid config.json file is included in the next test pass? Also, when we do the 3.1 post-mortem, could you remember to bring up looking through past user issues on the forum and making sure we have tests covering those issues?
The panic issue is coming from the addition of internationalization in 2.0, I think it's a sequencing issue where it's trying to find the error messages in the translation files and something's happening the wrong sequence.