We are experiencing a memory leak with the Gamma Preview 7.0-355
Before satori there is no leak at all, but now the memory usage slowly but steadily climbs. That is while patching. Haven’t tested the exported app yet.
It is unfortunately a very large project, that cannot be shared and I have no idea, what could be causing it, but here at least is the bug report - maybe not so useful yet.
I’ll update here, if I can narrow down the problem.
Just checked here. With 7.0-349 everything seems to be fine.
7.0-351 & 7.0-355 are starting out with a bigger memory footprint to begin with (1,9 GB vs. 3,3 GB) but afaiu that’s to be expected?
After sitting for a short amount of time they start leaking ~400 MB / min. Just running the patch, no editing and no interaction with the application.
It’s a rather extensive patch using Stride, lots of TextureFX, Fuse particles and a UI mainly based on Skia. I could share it privately if that helps @Elias.
If possible please share. But gut feeling tells me already that this experiment with satori is already over. Definitely not gonna use it for the final release. So sad. But let’s hope it gets more traction and becomes an official option at some point.
oh no :(
Maybe we can keep it as an export option for the time being?
Upcoming preview will be back to normal. Having it as an option for export - would be possible yes, but not sure it’s a good idea. Just another checkbox where things can go wrong. In case of reported issues we’d always have to ask whether or not that checkbox was on etc.
I mean you can still do it on your own, by publishing your exported app as self contained and copying those dlls into the output folder as an after publish step.
i see and understand.
maybe a checkbox for self-contained then in the exporter?
That we could add yes.
Sent you a dm on Matrix.
