https://bugs.freedesktop.org/show_bug.cgi?id=37168 --- Comment #2 from Sean McNamara <gm.potato.ul@xxxxxxxxx> 2011-05-13 16:27:44 PDT --- (In reply to comment #1) > (In reply to comment #0) > > > > Mesa 7.10.2 tarball OR Mesa 7.10 branch from git: Correct rendering; no > > crashing. > > Can you bisect mesa and see what commits between 7.10 and master broke it? debc45bca07a5dfad4199079f080b35c19f00e85 starts the memory leaks (very noticeable on this commit, just watch gnome-system-monitor's total memory usage grow by 25 - 100 MB/s) I got two kernel hard-locks with 8c631cfeae29b5236928f759e222aa35e6e4984c also, but it doesn't seem to have the memory leak. Anyway, I'm not sure *exactly* which commit because I was fighting hardlocks and memory leaks at the same time, and sometimes they are intermittent, but if you look at the r600g commit series by Marek on or around January 28 - 29, I think the problem lies somewhere in there. That's my best guess, and it's certainly more relevant than what I came up with the last time I bisected, which was the merge of dricore support (and I'm not even using dricore, btw). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- 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
