Bug#599769: (no subject)

[macarthur]

after looking at the new driver this issue is still happening. 260.19.36 
is still causing this weird issue. Now that firefox is using the opengl 
acceleration for various rendering things, it's as if it's happening now 
more than it used to. I think it's something to do with the way that it 
handles its memory allocation.

It's still there and has been for quite some time. I've already told 
nvidia about it on their forums but i doubt it's ever giong to fix it. 
It's either their problem(a bug that is continually reintroduced and 
never leaves) or it is something with the way that xorg works with 
opengl accelerated applications.