This is very similar to the issue I reported here.
The difference is that the object has a class, which for some reason causes this problem to arise again.
I have set up a simple reproduction here.
And a slightly more advanced reproduction here (this more closely resembles our actual use case).
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too