Comment # 2
on bug 94008
from serge
(In reply to Alejandro Piñeiro (freenode IRC: apinheiro) from comment #1) > (In reply to serge from comment #0) > > > I also made an apitrace which you can find on the following link, if someone > > is interested into looking at this issue: > > > > https://drive.google.com/file/d/0B6bdV-rKtJnFWDlvWE1vZnFtaXc/view?usp=sharing > > Under the risk of adding noise here, I tried this apitrace on a intel HD4600 > (haswell). I got several visual artifacts (in addition to be really slow), > getting several performance related debug warnings. For example, at the > initial phase, where it is mostly compiling shaders: It does the same when playing the apitrace with my card, but those artifacts where not there at recording time. I think they are due to fake calls injections. There is an explanation for this on the tracing section of the following link: https://github.com/apitrace/apitrace/blob/master/docs/BUGS.markdown
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
