I’m sorry I can’t, due to out component support all languages with language-data and the monitor did’t report the specific info because we dont know how to catch error like this
Too bad. It looks like some fundamental assumption in the parser library (there always being one active parse stack) is being violated somehow, but I couldn’t figure out from reading nearby code how this is happening—so it’d be helpful to be able to reproduce this.