Summary: | Stack overflow when rendering with a Picture that has an alpha_map cycle | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Aaron Plattner <aplattner> | ||||||
Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> | ||||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||
Severity: | normal | ||||||||
Priority: | medium | ||||||||
Version: | git | ||||||||
Hardware: | Other | ||||||||
OS: | All | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Aaron Plattner
2009-08-28 12:58:48 UTC
Created attachment 28987 [details]
Test case
My immediate reaction is that it should be a BadMatch if you try to set a picture as its own alpha map, and also if you try to set an alpha map that itself has an alpha map already. Those two rules together seem like they would prevent cycles. There is also the case where a picture and its alpha map point to the same underlying drawable, but I don't think that will cause other issues than unpredictable painting, at least in the software implementation. Created attachment 36080 [details] [review] Do not recurse looking for an alpha map This patch makes the alpha map lookup non-recursive, stopping after the first alpha map. Fixed in 1.9. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.