@Nelli I saw someone else on this thread suggest that a few days back. I got this error only one time on chrome and it was something in my code that broke with the 2018.1 upgrade. Adjusting my code fixed it. But i saw someone comment a few days back that they were using FF as a workaround...