Back to bug 23627
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| gordon.jin | 2009-09-01 18:13:16 UTC | Assignee | gordon.jin | haihao.xiang |
| Summary | Calling XvShmPutImage or XvPutImage above some critical frequency causes resource contention on /tmp/.X11-unix/X0, resulting in user noticeable poor performance. In our environment, 60Hz is above the critical frequency. | Calling XvShmPutImage or XvPutImage above some critical frequency causes resource contention on /tmp/.X11-unix/X0 | ||
| cworth | 2009-10-26 12:11:13 UTC | Status | NEW | ASSIGNED |
| chris | 2010-07-02 13:50:39 UTC | Summary | Calling XvShmPutImage or XvPutImage above some critical frequency causes resource contention on /tmp/.X11-unix/X0 | Calling XvShmPutImage or XvPutImage above some critical frequency causes client starvation. |
| chris | 2010-07-18 02:33:50 UTC | Summary | Calling XvShmPutImage or XvPutImage above some critical frequency causes client starvation. | Calling synchronous XvShmPutImage or XvPutImage faster than vblank causes client starvation. |
| Component | Driver/intel | Server/general | ||
| Assignee | haihao.xiang | xorg-team | ||
| gitlab-migration | 2018-12-13 22:21:21 UTC | Status | ASSIGNED | RESOLVED |
| Resolution | --- | MOVED |
Back to bug 23627
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.