with the ...355.7z build the racer renders fine, starts moving smoothly, but memory (i have 16gb) rises rapidly towards 100% and the system slows to a crawl, i managed to delete the tab with the racer & memory drops back to normal. webgl set to forced in config.

Ah okay I might have gotten jemalloc working again and I think I've found the reason for the memory leaks too!

So Waterfox 36.0 should be ready for tomorrow, therefore I'm putting this test build here to make sure everything launches smoothly!

What's New

Gamepad support has been added!

WebGL will now render with DirectX 11 if available instead of just DX9

This build has been compiled with Windows 8 SDK

Things to help with

If anyone could let me know if they have any memory issues that'd be great. I monitored on an 8GB system and browsing a purported leaky website, as well as a benchmark and conformance test usage never went above ~800MB.

My main concern is now memory usage with WebGL. If you run a WebGL application memory usage is supposed to increase but not forever...if it does please let me know!

Normal usage of Waterfox, latest test build, seems much like the last few builds. In that through my daily surf routine of news sites, various science related sites, Social Media sites, and various online training sites...memory NEVER got above 450MB (+/- 5MB).

I read up on WebGL in Firefox with an Intel Graphics card. Updated my drivers, went into "about:options", made sure that "webgl.disabled" was set to false and that "Hardware Acceleration" was active in Options->Advanced section of Firefox. I couldn't tell you one way or the other if it was the driver or that I wasn't running hardware acceleration last test, but in doing the exact same things...my memory never got above 900MB...running the same activities as earlier in the same browser in different tabs. I even went to the extent of running all the aforementioned sites in separate windows and still my memory usage never went above 900MB. Small fluctuations in one way or the other, that were negligible at best. I also never crashed on the site, David Walsh WebGL Demos, which crashed WF last test I did. So between this build and two builds back memory usage decreased by 300MB, since before when running these same tests I had usage of 1.2GB and crashed. Again, I don't use WebGL and usually have it disabled with hardware acceleration turned off. Videos on Youtube tend to run better for me in full screen when acceleration is off and I spend a lot of time with tutorials and the like that use video.

I tried to learn a bit more about WebGL, but got bored with it as it isn't something I am entirely interested in to begin with. However, it does seem that the video drivers are the most important factor here and browser settings. Albeit, there are those video cards that either aren't supported or just don't work in some browsers. These are things that I read repeatedly from a simple Google search of "WebGL issues". I encourage anyone who is interested in WebGL to read a bit on the subject. Especially if it is a deal breaker on the browser you intend to use.

As for me...well I just disabled WebGL in firefox and turned hardware acceleration back off, as it suits my needs fine. Good luck to the rest of you and I hope this was somewhat helpful in testing this latest version of WF, thanks to Alex's efforts of course.

System specs for the record, not a monster machine by a long shot. Definitely not built for gaming:

Hello Racer rendering started good then was taking 10-20 seconds between refreshes.
Waterfox reaches 3.2gb in Task Manager.
There was no extra download activity (as seen in 36.0) but the hard drive was working nonstop.

So the build of a couple days ago, the first after 36.0's initial debut, had WebGL that worked better than the initial or the present release (I didn't get to try the second-to-last, was gone all day) -- though it was still problematic and skippy. Edited by themushroom - 2/26/15 at 11:14pm

Normal usage of Waterfox, latest test build, seems much like the last few builds. In that through my daily surf routine of news sites, various science related sites, Social Media sites, and various online training sites...memory NEVER got above 450MB (+/- 5MB).

I read up on WebGL in Firefox with an Intel Graphics card. Updated my drivers, went into "about:options", made sure that "webgl.disabled" was set to false and that "Hardware Acceleration" was active in Options->Advanced section of Firefox. I couldn't tell you one way or the other if it was the driver or that I wasn't running hardware acceleration last test, but in doing the exact same things...my memory never got above 900MB...running the same activities as earlier in the same browser in different tabs. I even went to the extent of running all the aforementioned sites in separate windows and still my memory usage never went above 900MB. Small fluctuations in one way or the other, that were negligible at best. I also never crashed on the site, David Walsh WebGL Demos, which crashed WF last test I did. So between this build and two builds back memory usage decreased by 300MB, since before when running these same tests I had usage of 1.2GB and crashed. Again, I don't use WebGL and usually have it disabled with hardware acceleration turned off. Videos on Youtube tend to run better for me in full screen when acceleration is off and I spend a lot of time with tutorials and the like that use video.

I tried to learn a bit more about WebGL, but got bored with it as it isn't something I am entirely interested in to begin with. However, it does seem that the video drivers are the most important factor here and browser settings. Albeit, there are those video cards that either aren't supported or just don't work in some browsers. These are things that I read repeatedly from a simple Google search of "WebGL issues". I encourage anyone who is interested in WebGL to read a bit on the subject. Especially if it is a deal breaker on the browser you intend to use.

As for me...well I just disabled WebGL in firefox and turned hardware acceleration back off, as it suits my needs fine. Good luck to the rest of you and I hope this was somewhat helpful in testing this latest version of WF, thanks to Alex's efforts of course.

System specs for the record, not a monster machine by a long shot. Definitely not built for gaming:

Hello Racer rendering started good then was taking 10-20 seconds between refreshes.
Waterfox reaches 3.2gb in Task Manager.
There was no extra download activity (as seen in 36.0) but the hard drive was working nonstop.

So the build of a couple days ago, the first after 36.0's initial debut, had WebGL that worked better than the initial or the present release (I didn't get to try the second-to-last, was gone all day) -- though it was still problematic and skippy.

Hmm okay thanks I'm patching in an upstream version of ANGLE to see if issues get resolved.

Quote:

Originally Posted by thecreator1965

Hi Mr. Alex,

Waterfox 34.0.1 is showing that it is Up-to-date.

Must WaterFox be manually upgraded, since using About WaterFox is reporting that it is Up-To-Date.

Don't worry the update patch is on hold until 36.0 is released officially!

Hi. I'm posting here since I have that critical issue with memory leak(s) (no crash, but out of memory after several hours, can't use any memory consuming application) and general browser perfomance slowdown due to it.

Can you, please, update the current status of the work with memory allocator (replacement/improvement/plans) ?

TO ALL

You can consider using two options with the current memory leaks, which helps a lot with them:

1. Disable Adblock Plus/Adblock/Edge addons and replace it with uBlock.
2. Use this little handy application.