Comment # 72
on bug 81644
from Aaron B
(In reply to comment #71) > (In reply to comment #70) > > https://drive.google.com/file/d/0B1laUfqMuZQBeWpHSDYtV2N3RjQ/edit?usp=sharing > > Can you reproduce the crash by feeding those traces to glretrace? > > > (In reply to comment #69) > > If I get time I'll compile Mesa 10.1 32 and 64 bit and see if they work. No > > promises, as git always fails either on or right after receiving 99% of > > objects, so I have to try about 20 times to even attempt compile basically > > anything. > > Note that you only really need to clone a Git repository once, after that > all the history (including all the commits you might need to test during the > bisection) is available locally. Yeah, but I build it with yaourt, which likes to contain it's gits elsewhere and apparently deletes them every time as you can't keep a clone unless it's in the same session. I would work on getting 2-3 clones and uploading them to my git and copying from that if need be, but it's just tons of work for me. Like I said, I have to try about 20 times to even clone anything, it's a severe pain. And running glretrace about 10 times on the trace files, no beans on getting another crash. [aaron@Aaron-Arch Chromiumapitrace]$ glretrace chromium.trace 0 64 glXSwapIntervalMESA(interval = 1) = 0 64: warning: unsupported glXSwapIntervalMESA call Rendered 150 frames in 2.68355 secs, average of 55.8961 fps [aaron@Aaron-Arch Chromiumapitrace]$
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
