Bugzilla

Hi Eric. Thanks for using my tryserver build despite its problems. What you say about artifacts in non-popup windows is bad news, though. Though it'd be tricky, I should be able to change my patch's behavior according to whether or not Firefox is drawing into a popup window. I currently have no idea how I'd deal with them if they can happen in any window, more or less at random.

Please keep testing. If you go for a week without crashes, then it'll be worthwhile trying to save my patch (even though I currently don't have a clue how to do that). Otherwise it's back to the drawing board.

I suspect Safari's artifacts have something to do with its more aggressive "purging", and with the fact that your system uses its video resources to their limits, and sometimes a little beyond. That's just a guess, though. And I don't think they are related to the target of your blog post's challenge: Safari's artifacts seem to fill an entire native object, but the webrender artifacts seem to be random splotches.

Hi Eric. Thanks for using my tryserver build despite its problems. What you say about artifacts in non-popup windows is bad news, though. Though it'd be tricky, I should be able to change my patch's behavior according to whether or not Firefox is drawing into a popup window. I currently have no idea how I'd deal with them if they can happen in any window, more or less at random.

Please keep testing. If you go for a week without crashes, then it'll be worthwhile trying to save my patch (even though I currently don't have a clue how to do that). Otherwise it's back to the drawing board.

I suspect Safari's artifacts have something to do with its more aggressive "purging", and with the fact that your system uses its video resources to their limits, and sometimes a little beyond. That's just a guess, though. I don't think they are related to the target of your blog post's challenge: Safari's artifacts seem to fill an entire native object, but the webrender artifacts seem to be random splotches.

Hi Eric. Thanks for using my tryserver build despite its problems. What you say about artifacts in non-popup windows is bad news, though. Though it'd be tricky, I should be able to change my patch's behavior according to whether or not Firefox is drawing into a popup window. I currently have no idea how I'd deal with them if they can happen in any window, more or less at random.

Please keep testing. If you go for a week without crashes, then it'll be worthwhile trying to save my patch (even though I currently don't have a clue how to do that). Otherwise it's back to the drawing board.

I suspect Safari's artifacts have something to do with its more aggressive "purging", and with the fact that your system uses its video resources to their limits, and sometimes a little beyond. That's just a guess, though. I don't think they are related to the target of your blog post's challenge: Safari's artifacts seem to fill an entire native object (if they're similar to the ones you've seen with my tryserver build), but the webrender artifacts seem to be random splotches.