Thaddeus Loke
Thaddeus Loke
Do you have a sample workspace that reproduces the issue? We should look into this, but it will be easier if we have a consistent repro to work off.
Is the issue with memory usage in general, or is there a clear growth pattern? If the case is that there's constant memory growth over time that doesn't stabilize, then...
One more question: if you do a full build (ctrl + shift + B), does that cause the memory usage to decrease again? This should force a garbage collection.
I can't find any documentation on it either, but I'll try to clarify what I think should happen. ForceUpgrade should do just that, force the upgrade codeunit to be run...
Almost. I did mean "Publish Extension Without Building" but it's a command that only shows up once you have attached to the server. So: 1. F5 and choose the Attach...
Is this SaaS or local? If it's SaaS, can I get the AAD tenant Id and environment name? If it's local, there might be something in your windows event logs....
That doesn't ring a bell for me unfortunately, it's weird because this publish isn't any different request wise from the publish from a regular F5 publish. Let me spin up...
Sorry for the delay in getting back on this, no I was not able to reproduce this on a SaaS or local OnPrem instance. In both cases, I can attach...
I'm actually surprised that this alternative method works. It shouldn't! Or at least it's not designed to work in this way, so I don't think we want to document this....
@tfenster - can we get a more minimal repro for this?