mike@koala% rpm -q xorg-x11-server
With this version of Xorg and fglrx, every time I open a chrome window (either browsing or Webapp window), Xorg server memory grow by at least 5MB. This memory won't go away when I close the chrome window.
As time goes on, Xorg will eat up all memory and I'll have to logout and restart Xorg.
I have filed a bug to Chrome as well. Also, I found a similar bug report claiming that this is also happening for Nvidia drivers since Xorg 1.16.1.
I ran Xorg with valgrind and opened Google Drive Webapp several times. Valgrind does report leaks (after InitOutput()) from fglrx-libglx.
However, I cannot upload attachment here. How could I send you the log?
Created attachment 111551 [details]
(In reply to Mike Qin from comment #1)
> I ran Xorg with valgrind and opened Google Drive Webapp several times.
> Valgrind does report leaks (after InitOutput()) from fglrx-libglx.
> However, I cannot upload attachment here. How could I send you the log?
Here's the log, it's simply too large. Oops.
fglrx is ATI's closed source driver - X.Org can't fix bugs in that.
(In reply to Alan Coopersmith from comment #4)
> fglrx is ATI's closed source driver - X.Org can't fix bugs in that.
Well, both Nvidia and fglrx drivers have this issue according to https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-trusty/+bug/1402551
I'm not sure what's really happening, but I suspect it could be some undocumented API change in Xorg that's causing this leak. Both of the closed source driver are leaking memory, it just sounds so much like the lower layer's regression.
I am genuinely shocked but the issue is gone with google-chrome 54.0.2840.100 (64-bit) on openSUSE 42.1 and latest AMD Catalyst 5.12 driver (which has not seen any updates for a very long time). Looks like the latest stable google chrome finally fixed this.
rpm -q xorg-x11-server
$ rpm -qa | grep fglrx