Closed IanKemp closed 7 years ago
Looks like this happens after I run a master build (which writes config data) then run a 0.9.9.152 instance, which attempts to load that config file and obviously doesn't support the "new" values.
You're right : there is a bug in release 0.9.9 but fixed in master branch. I will publish a new release 'RC1' with bug fixes commited since.
Win10 x64, MemoScope 0.9.9.152 (latest release).
Furthermore, after this exception, the app looks like this: