The error appears to be coming from this plugin:
There’s a similar report in that thread, so try updating to the latest version of that plugin.