Bug#825668: Firefox memory reporting

2016-05-29 Thread Pavon
Another clue that I have seen is that Firefox has been reporting a negative value for the heap-texture memory use. I don't know if this indicates a bug in Firefox's managing of that memory, it's reporting of that memory, or of Xorg's managing of that memory which is just being exposed by Firefox

Bug#825668: Appears Fixed

2016-09-05 Thread Pavon
After installing updates a couple weeks, this problem appears to have gone away. Some potentially relevant package numbers (old, new): xserver-common:amd64 (2:1.18.3-1, 2:1.18.4-1) xserver-xorg-core:amd64 (2:1.18.3-1, 2:1.18.4-1) xorg:amd64 (1:7.7+15, 1:7.7+16) x11-common:amd64 (1:7.7+15, 1:7.7+