@Dustin, the issue seems to have some relationship to the resolution(s) selected, but I don't *think* it is strongly monitor-specific. It might be interesting if you tested against a couple other monitors to see if there is a pattern. But I think the bug has stalled out upstream because as originally reported it sounded to them like a texture buffer size issue (>4096). But it sounds like this is a more fundamental error.
Dustin, it might be helpful to have a new bug report, filed with a very minimal setup (no more than one monitor attached, using the fewest tools to reproduce, etc.) We could shoot that upstream and hopefully get a different set of eyes on it.
@Andres, how has your testing gone so far?
@Dustin, the issue seems to have some relationship to the resolution(s) selected, but I don't *think* it is strongly monitor-specific. It might be interesting if you tested against a couple other monitors to see if there is a pattern. But I think the bug has stalled out upstream because as originally reported it sounded to them like a texture buffer size issue (>4096). But it sounds like this is a more fundamental error.
Dustin, it might be helpful to have a new bug report, filed with a very minimal setup (no more than one monitor attached, using the fewest tools to reproduce, etc.) We could shoot that upstream and hopefully get a different set of eyes on it.