I subscribed to the GH issue. The only thing I frequently see is that when people disable the object cache without also flushing it right after or right before re-activating it, then the old stale cache data will show up on the site, and sometimes is even written back to SQL.
I found the problem.
WooCommerce creates transients with names like product-transient-revision and uses their values (timestamps) to cons up the names of other transients. Deactivating a persistent object cache plugin makes those transients’ values revert to whatever they were before the object cache was activated. That is, they revert to stale values. In turn that means that other stale transients get used to look up variants and other product stuff.
This way of using transients made it into WooCommerce as a fix to their performance defect [#5777](https://github.com/woocommerce/woocommerce/issues/5777) .
The fix to object caching plugins is to delete all transients from the database upon deactivation, so no stale values are left.
I added this to Redis Object Cache. Object Cache Pro was already doing it.
