Bugzilla

I apologize that this is causing you distress. The problems here, again, seem to be related to out-of-memory issues, as Firefox can accumulate memory in various places during a running session. It would explain the multitude of symptoms you are seeing about weird colored rectangles in various situations (not simply text, but everywhere else), and also the unpredictable aspect of it. This is not necessarily a simple problem to fix and will require discussion amongst the Graphics team here to see if there are things we can mitigate some of the symptoms.

Note that the ESR version of Firefox for the next year will be 91, so that you will still at least be able to disable WebRender in the ESR version if nothing else. One thing you might be able to do in the meanwhile in later versions while we investigate a fix with WebRender is to try using your OS's support for Swap/Page files and increase the amount of that available: https://www.geeksinphoenix.com/blog/post/2010/10/26/Managing-Virtual-Memory-Pagefile-in-Windows-7

What you can do to help us start narrowing down if there are things we can fix is to go to "about:memory" and click on "Measure and save". Then attach the produced memory report so we can look at it.

I apologize that this is causing you distress. The problems here, again, seem to be related to out-of-memory issues, as Firefox can accumulate memory in various places during a running session. It would explain the multitude of symptoms you are seeing about weird colored rectangles in various situations (not simply text, but everywhere else), and also the unpredictable aspect of it. This is not necessarily a simple problem to fix and will require discussion amongst the Graphics team here to see if there are things we can mitigate some of the symptoms. This is, in technical terms, a problem with the OpenGL API not giving us enough feedback to say if a texture allocation has failed - so that the texture we are rendering with is actually bad causing the weird solid coloring.

Note that the ESR version of Firefox for the next year will be 91, so that you will still at least be able to disable WebRender in the ESR version if nothing else. One thing you might be able to do in the meanwhile in later versions while we investigate a fix with WebRender is to try using your OS's support for Swap/Page files and increase the amount of that available: https://www.geeksinphoenix.com/blog/post/2010/10/26/Managing-Virtual-Memory-Pagefile-in-Windows-7

What you can do to help us start narrowing down if there are things we can fix is to go to "about:memory" and click on "Measure and save". Then attach the produced memory report so we can look at it.

I apologize that this is causing you distress. The problems here, again, seem to be related to out-of-memory issues, as Firefox can accumulate memory in various places during a running session. It would explain the multitude of symptoms you are seeing about weird colored rectangles in various situations (not simply text, but everywhere else), and also the unpredictable aspect of it. This is not necessarily a simple problem to fix and will require discussion amongst the Graphics team here to see if there are things we can mitigate some of the symptoms. This is, in technical terms, a problem with the OpenGL API not giving us enough feedback to say if a texture allocation has failed - so that the texture we are rendering with is actually bad causing the weird solid coloring.

Note that the ESR version of Firefox for the next year will be 91, so that you will still at least be able to disable WebRender in the ESR version if nothing else. One thing you might be able to do in the meanwhile in later versions while we investigate a fix with WebRender is to try using your OS's support for Swap/Page files and increase the amount of that available: https://www.geeksinphoenix.com/blog/post/2010/10/26/Managing-Virtual-Memory-Pagefile-in-Windows-7

What you can do to help us start narrowing down if there are things we can fix is to go to "about:memory" and click on "Measure and save". Then attach the produced memory report so we can look at it. It is best to record the memory report right about where the symptoms would normally occur (or even after symptoms occur if the browser UI is usable enough to do that), so that we can see where memory pressure is highest in that longer running session.