I have noticed a trend in recent Roblox updates where the binary size of the .exe is consistently getting bigger without any features being really added.
To prove this, current deployed version (version-7a4a5d7d1fb3449f) is 106MB, older version (for example version-f6cd26d0e71b47c9 deployed on 24th September) is 105MB in size, and future version (version upcoming version-4aeb17bd13994560) has got another 2MB bump up in size (exactly 108MB).
Upon looking closer onto the binary, what has changed almost always is the size of class descriptors, going from reasonable sizes (0x800 bytes) to absurd sizes (like 0x2000 bytes), having in mind this is for ALL class descriptors that Roblox has, which is about 700 of them, it is most likely this is the culprit.
Or is this change in size expected and intended? Even though you have added more bytes to the class descriptors they seem to store garbage data instead of actual data.
Very dumb problem in my opinion. It’s steadily growing the binary’s size; at least if you’re going to do things like this, do it on the heap, not on the binary itself, wouldn’t surprise me we will be facing a 110mb binary soon honestly.
Thanks for calling this out. We’re working on some migrations for new more performant containers within the ClassDescriptor. In order to ensure the capability to rollback without a new release we had to duplicate the data held.
We expect this to be temporary. That being said we’re looking at ways to further mitigate the binary size footprint from this migration and should hopefully have something out soon.