TOPIC:

Without knowing the cause of the problem, it's very hard to eliminate it.
We received this report only from you, so it's most probably related to a specific implementation of yours.

All we can do now is to add another workaround in the reported method, but it does not mean that the problem is solved.
This workaround will be added in the next version 3.12, but it's still under beta for now (we expect to publish it as stable within a week or 10 days)