Yes, please, it would be great if we could get one more public patch (for example, 2022.3.62f3) that includes the memory leak fix. Thanks a lot for the help
Unfortunately it’s not the answer I know you wanted but the official answer I’ve been given so far is that your only option now is to upgrade to a supported Unity 6 LTS.
Whilst I can understand the apprehension, Unity 6 has been out for a fair while and has proven to be very stable. I’d also like to add that there’s been significant improvements to 2D and 2D physics.
Sorry I couldn’t give you the answer you wanted.
Based on my experience developing for Android, upgrading Unity versions often brought new problems: broken projects, higher crash rates,unexpected regressions or other new bugs.
Moving from 2021.3 LTS to 2022.3 LTS this time already caused a memory leak that took days to debug and resolve. I don’t really want to find out what Unity 2023 or Unity 6 might bring, every newer version so far has only introduced more problems for me, so I prefer not to upgrade unless there is a strong reason to do so.
I see.. that’s actually what I expected from the start, but you gave me a glimpse of hope, ahaha. Thanks for trying to help though, I really appreciate it.
I understand that these decisions aren’t up to you, but leaving this bug as it is is really a pity. So.. I guess I’ll need to test Unity 6 and move eventually, but for now I need a bit of a break from firefighting.
Yeah, really sorry. I simply didn’t know if it were possible and I wasn’t aware that the fix wasn’t available generally until I saw this thread otherwise I would’ve raised it internally before.
I guess this makes this fix the absolutely worst timing for 2D physics I’ve even seen. ![]()
This extra year of support for enterprise users really just creates tons of Feels Bad™ for anyone not on an enterprise plan, and ends up stuck with a broken version of the engine.
The state 2022.3 has been left in for non-enterprise users is pretty shocking honestly.
Nobody was aware of the root cause of this until yesterday to be fair. I’m still involved in discussing this internally but as above, I cannot promise anything as there are a lot of factors at play here. For sure, it’s terrible timing for a memory leak fix to land which rarely happens. Please bear with me on this.
I think the best solution now is, keep using the older Unity version (like 2022.3.50f1) (with security problem, yes) UNTIL they release 2022.3.64f2 which fixed both memory leak and security problem.
I guess 2022.3.64f2 will be released by the end of this year. Hope that until the time come, the players won’t meet problems like losing banking account or something like that. It’s not my fault anyway because I can’t hack into Unity’s engine to fix that.
@RaventurnPatrick [RaventurnPatrick]
Any reason why you are not using Unity 6 LTS?
Technically my game run well with Unity 6, but, a lot of SDKs be used in the game (include the publisher’s SDK) haven’t support Unity 6 yet. I can’t tell the SDKs provider “hey, support Unity 6 now!”.
Was there any specific reason stated why those fixes are effectively behind an additional paywall?
Ultimately it’s just poor timing. The ‘free’ 2022 LTS period ended just before the major inspector bug was fixed, and before this memory leak was addressed.
So it comes down to whether Unity decides they want to cultivate some goodwill or not.
I’m just not sure what the point is of having LTS updates that are enterprise specific. I get that enterprise would have dedicated support if they encounter issues, but if it is a Unity update anyways, why not make it available for everyone?
I mean on one hand giving out the updates that are part of the extended enterprise period for free would undermine part of the incentive for paying for Enterprise support.
But on the other hand, as mentioned, it’s nothing but feel bads for us who don’t have access to these updates when the version we’re left with has major issues.
Though this is a bed Unity made themselves.
I’m not sure that enterprise support was specifically targeting updates for all Enterprise users, but rather specific support (also if I’m not mistaken it is mandatory to use enterprise when reaching certain revenue threshholds)
I would strongly advocate to unity to rethink their strategy and release LTS updates for all users. Having more users use a version of Unity should also increase the stability of said version - so it should actually be a win-win for enterprise customers.
I think it’s more an incentive to sell enterprise licenses: you get an extra year of updates to your engine version.
But I think the idea is misguided as I’d wager enterprise and industry customers are paying for their licenses for one sole reason: they’re required to by Unity’s licensing terms. Such as their income level.
So I think locking updates behind a particular license is only a net negative for Unity.
And should they become public, any enterprise user complaining about it would have to be a special kind of selfish.
I think the crux of the specific isssue here is that people depending on LTS status are stuck. They can’t move forward because it’s enterprise only and they can’t roll back due to a serious and exploitable bug. To me, this isn’t just a case of cultivating good will but is in fact doing their job and actually providing Long Term Support - the words on the tin and the backbone of any sense of stability.
As I said above, it was only a few days ago that this issue was discovered so please bear with us as it just takes a little time to deal with things.
You can always rollback to version which was working, and simply apply patcher on apk/aab.
Hi everyone,
We have produced a new build of the final public version of the 2022 LTS — Unity 2022.3.62f3 — which includes a fix for the memory leak affecting 2D physics in webGL projects discussed in this thread, as well as another one for a bug causing the Inspector not showing all public/serialized script properties until refreshed.
We recommend all users still working in 2022.3 to update to this build to avoid these issues and benefit from the vulnerability fix we included in the previous f2 release.
The general release notes are available here: Unity 2022.3.62f3
Hi Everyone!
I realized the new version 2022.3.62f3 is not available on Unity Cloud Build yet. Is there an ETA to be included there?
