After some playing around with Process Explorer, I made a small discovery:
If I suspend the only mswsock.dll thread, studio doesn’t freeze or eat RAM. (it just waits forever)
When I resume it, that’s the moment studio freezes and starts eating RAM.
Apparently it’s the HTTP requests itself that somehow do this stuff…
Also goddamnit the waiting and freezing is annoying.
EDIT: Actually the HTTP stuff is fine.
It’s the QtWebKit4.dll that uses the HTTP stuff that eats the RAM. (Which also freezes the GUI, which makes sense as it is the GUI’s DLL, no?)
GIF of the QtWebKit4.dll thread: (although that dll name doesn’t appear in the Stack anymore) (If I spawn-refresh the Stack window during The Big Yield, it’s 99% of the time QtWebKit4.dll stuff) (for some reason while I took that GIF it didn’t appear a single time, which is weird on its own but eh)
I googled “QtWebKit4.dll download” and got this file:
(direct download link being http://www.dlldump.com/dllfiles/Q/qtwebkit4.dll)
I went to %localappdata%/Roblox/Versions/CURRENT_STUDIO_FOLDER.
There I renamed “QtWebKit4.dll” to “QtWebKit4_OLD.dll” and put the downloaded one in its place.
After restarting studio, the publish GUI stuff is (minus HTTP, less than a second) instant.
I have no idea, AFAIK there’s no %localappdata%, instead its stored within the RobloxStudio package or something, but that has no dlls in it, only framework + dylib
Almost a month has passed, and guess what still happens when I try to upload stuff? freeze EDIT: Forgot to mention: I can still fix it by replacing the QtWebKit4.dll
Maybe it’s time ROBLOX updated it?
We’re actively working on a few upgrade projects. That said, we want to complete them one at a time to make sure we know what causes new problems when we encounter them.
Any updates on this? I timed it and it literally takes me literally 60 seconds to upload over one of my existing animations. 30 seconds to load the list of animations, 30 seconds after I click on the one I want to upload over.
After spending 2 minutes publishing to a new place, clicking the “Next” button froze studio for another minute. (luckily I can still fix it by replacing the QtWebKit4.dll myself, which makes me wonder why it takes so long…)