Yes, we ended up doing some refactoring for the upcoming v1.11 (currently available as a nightly pre-release) and it should resolve the likely underlying problem. So if you haven't checked it out yet, give it a try and see how you go 
1 Like