I am not sure if you can detect anything in the code, but if you can, it’d be super perfect to fix this problem, as we can’t really do much about it other than to tell our customers “it’s not us”.
Even with the parameters, I don’t manage to reproduce or to understand why it can happens. Can you give us the package name that the user uses to reproduce ? Or can you send us the package to reproduce via Private content (you can find in section 3 of this page how to do so) ?
if only it were so easy. This only appears randomly and rarely - but when it does, it doesn’t respect the settings at all.
Just set up a sample wasm and it should happen for you eventually - our package is way too large to be relevant in this scenario and I doubt it will cause it for you either, as it only happens as I said randomly and very rarely.
Others have reported same, however, so it’s not us causing it…