Originally Posted by themushroom
Originally Posted by MrAlex
Hmm. As seti mentioned below, does setting webgl.disable-angle
to true still invoke memory leaks?
I did both of the config tweaks mentioned, went to the tester page to confirm ANGLE isn't in use (sizes are now 4096), closed and reopened WF for good measure, and then checked out the WebGL demo pages. And the leak continues.
Something's up on my end but what?
Hmm I don't think any config changes will help for this. I'm going to be making a new build in a bit and I'll also post here for you to test out to see if it makes a difference for you. Also just to clarify, this happens on Firefox as well?
Originally Posted by kevindd992002
MrAlex, isn't the updater already fixed? My v35 WF still doesn't see that there's a v36 update.
It is fixed but the issue is that the 35.0 updater only accepts signed MAR files (for some reason this was changed and enabled by default in 35.0!) so I've been scavenging the Mozilla docs to see how to sign the update file properly!! Old builds didn't have this on by default and I've disabled it for 36.0 but I'll make sure to find out how to sign MAR files for 35.0! Sorry about the inconvenience, I've been trying for a few weeks now to get this to work but I'm sure I'll figure it out soon.
Originally Posted by chorse
My update work. It informed me of the new V36. I downloaded it and it installed fine. No issues yet with WF36.
Yes only 35.0 hasn't received the update as I'm not seeding it to that version until I can sign the update files correctly. Good to hear it worked for you!
Originally Posted by bIOforger
v36 is a great release, RAM usage is back to under 1.5gigs for my setup, performance is also much snappier generally than before, probably better than it was in V34.
One tiny gripe the help/about page doesn't seem to be looking for an update, so i had to download it manually. Great work, keep it up
Great to hear! And yes sorry about that, it's the issue I've mentioned above.