webdriverio: "is calling TIS/TSM in non-main thread environment, ERROR" repeated hundreds of times when running tests

Is your feature request related to a problem? Please describe. I get 100s of lines of output like this on Mac OS X when I run many tests:

2019-10-17 16:33:38.605 chromedriver[83751:1536943] pid(83751)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-10-17 16:33:38.605 chromedriver[83751:1536943] pid(83751)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-10-17 16:33:38.605 chromedriver[83751:1536943] pid(83751)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-10-17 16:33:38.605 chromedriver[83751:1536943] pid(83751)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-10-17 16:33:38.605 chromedriver[83751:1536943] pid(83751)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-10-17 16:33:38.605 chromedriver[83751:1536943] pid(83751)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-10-17 16:33:38.605 chromedriver[83751:1536943] pid(83751)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-10-17 16:33:38.605 chromedriver[83751:1536943] pid(83751)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!

Describe the solution you’d like Directly filter it out until a better solution can be found, like this: https://github.com/processing/processing/commit/f512457c6e6034a1230161a01080ede5f431eebb

Describe alternatives you’ve considered 🤷‍♂

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 15 (5 by maintainers)

Most upvoted comments

I can reproduce this issue with two specs that each contain element.setValue(...) calls. If they run in parallel (maxInstances >= 2), I see the above TIS/TSM log output (apparently one error per character?). The problem may be with Chromedriver, it might be the way that WebdriverIO is implementing element.setValue(), not sure. I haven’t tried the selenium-standlaone service to see if the issue can be mitigated by avoiding Chromedriver directly.