@Andy Foley:
Thanks for the hint, but I have the issue with both versions: fglrx und
fglrx-updates
(Radeon R7 200)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314787
Title:
Memory leak
To
** Changed in: linux (Ubuntu)
Milestone: ubuntu-14.04.3 => None
** Changed in: fglrx-installer (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314787
I just started getting this problem after swapping an old nvidia GFX
card with a Radeon 6850. Running Mint 17.2 (based on 'Trusty'), kernel
3.13.0-24-generic.
I found a stab-in-the-dark solution that works for me. In synaptic
package manager, I replaced all the fglrx packages with the 'updates'
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New = Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Changed in: linux (Ubuntu)
Milestone: None = ubuntu-14.04.3
--
You received this bug
Well, I'm willing to try because I spoke too soon : leak is back for me
after a few days if i let 1 or 2 programs running. It's still slower
than before to fill my ram, but still here.
2) Installing kernels from the 3.13 or 3.16 (I have not bothered with
3.15 branches) branches result in the
I see where you are coming from, but no, I do not think it is a
regression because a) it existed with the prior AMD driver set, and b)
it goes away with the 3.14.x kernel Trusty shipped with the 3.13.x
branch. Technically, I guess it could be some sort of regression though
because it comes back
'Couldn't agree more on the poor AMD driver set. That's also why I was
(notice the past tense) not quite convinced about it being kernel
related, since some people with both AMD and latest kernel don't share
this leak problem. Anyway, thanks for sharing your positive results with
3.14 kernel, it
Hi,
Just downgraded kernel 3-16 - 3.14.39 and I followed GVS's instruction above.
And after that I installed
http://www2.ati.com/drivers/linux/amd-catalyst-omega-14.12-linux-run-installers.zip
See this Xorg process's memory comsumption:
nuhapumppu Desktop # uptime; pmap 1564 | grep total
Awesome! And you are welcome. :)
Gordon VS
gvsche...@cciwireless.ca
On 15-04-23 08:21 PM, santzi wrote:
Hi,
Just downgraded kernel 3-16 - 3.14.39 and I followed GVS's instruction above.
And after that I installed
I was able to reduce (but not solved) the leak somehow, for 3 days now, using
swappiness. I have slightly icreased my swap partition, and setup like this :
cat /proc/sys/vm/swappiness
sudo sysctl vm.swappiness=40
sudo mousepad /etc/sysctl.conf
# confirm you have this line :
vm.swappiness=40
Guys: I know that some of you think that this issue exists independent
of kernel version. Personally, that is simply not correct. Of course I
can only go on my own detailed experience as there is no official
response to this issue. However, I can reproduce the issue at will. I
can also get
Hellou,
I followed GVS's instruction above and leak is still exist.
Linux Mint 17.1
MATE 1.8.1
Kernel: 3.16.0-34-generic
AMD Catalyst driver: 14.20
Uptime about 2 hours:
1479 root 20 0 1126892 840244 101008 S 1,0 20,8 15:56.05 Xorg
So almost 21% Xorg has eat memry.
uptime; pmap
I cured my issue by installing kernel 3.12.36 and the drivers mentioned
in my solution. I was using 3.13.x. I now use 3.14.38 with no issues.
Even though it may not be the same for others, the kernel was definitely
an issue on my system.
What makes this so frustrating is that very few people
I build them, using a method close to yours. I've just installed latest
3.16.0-36.48 kernel a few minutes ago, and I can already tell I'm
probably gonna still have the issue...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Damn. That is so frustrating. I know how you feel. What distro you
using?
Gordon VS
gvsche...@cciwireless.ca
On 15-04-17 11:14 AM, Mediaklan wrote:
I build them, using a method close to yours. I've just installed latest
3.16.0-36.48 kernel a few minutes ago, and I can already tell I'm
I'm on kernel 3.16.0-34-generic, already with latest AMD catalyst
driver, and I'm still having this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314787
Title:
Memory leak
To manage
How did you install the AMD driver? Did you build the packages or use
the update drives app, or use the:
sh ./drivername.run
method.
For me only building the packages for my distro worked. The method is
in my post.
Gordon VS
gvsche...@cciwireless.ca
On 15-04-17 10:23 AM, Mediaklan wrote:
Xubuntu 14.10 x64 on an Aspire One 722 (4go RAM - AMD series C-60). As you say
earlier, it's quite frustrating indeed : it's clearly related to fglrx and xorg
in some point, but I think it's not related to kernel : this netbook had a
fresh install not so long ago and so, started with a 3.16
Still a big problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314787
Title:
Memory leak
To manage notifications about this bug go to:
FWIW, I have Kubuntu 14.10 with an AMD 5770 video card. If i use the
fglrx or fglrx-updates drivers, reboot, within 6 hours my 8GB RAM is
used up and swap is thrashing.
If i switch back to the xserver-xorg-video-ati driver, reboot, then apt-
get --purge autoremove, then reboot again... memory use
Backup using Clonezilla (recommended).
STEP ONE: Remove proprietary AMD / ATI drivers.
STEP TWO:
What kernel are you using? Type in terminal:
uname -r
If you are not using this kernel (3.14.37) download it here as I know it
works very well:
[Expired for fglrx-installer (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: fglrx-installer (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bug #1354350 looks like the same as this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314787
Title:
Memory leak
To manage notifications about this bug go to:
@GVS (gvscheik1-g)
Is you system still up and running without leaks? I have got
3.11.0-20-generic and the leak is there. I just wonder why Canonic is
not interested at all this major bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
using 3.13.0-33-lowlatency with fglrx beta driver[1], leak still there ...
will test today new installed 3.13.0-34-lowlatency and look if it still
happens
[1] http://support.amd.com/en-us/kb-articles/Pages/latest-linux-beta-
driver.aspx
--
You received this bug notification because you are a
No leaks since the kernel upgrade. However, I have stopped latest
updates of Network-Manager-Gnome at version 0.9.8.8-0ubuntu4.2 due to
the fact that the latest update made the memory leak so bad I could not
be up for more than a couple of hours without a reboot.
Being that I am unwilling to
How I stopped the Xorg memory leak (or slowed it down enough to not
notice it):
1) I Did NOT update to latest Network-Manager-Gnome update (0.9.8.8-0ubuntu4.3).
2) I updated the kernel via system updates to Generic Linux kernel 3.13.0.34.40
3) Installed latest AMD ATI Drivers 14.8 available here:
I also have done a clean install of the best ubuntu yet, and my system
is affected by the bug, xorg is leaking 2GB/day as mentioned above.
I am new to Ubuntu and previosly was using mac. So ubuntu feels
familliar to me, but the buginess bugs me...
In obinions what linux needs is not features,
I am very pleased to say that on my system the memory leak appears to
be corrected by upgrading to generic kernel 3.13.0.33.39.
Xorg is once again releasing memory.
It has been only 24 hours of up time so I have my fingers crossed.
Before the kernel upgrade I would have had to reboot at least
I do not know if anyone is working on this horrible bug.
Being that I noticed users here said they upgraded to Trusty (as did
I), I decided to do a clean install to see if indeed the issue was
confined to upgraded systems.
Alas, the memory leak is as bad as ever on a clean install.
Trusty is
Hi! Is anybody working on the bug? I find myself in the same situation
with my AMD graphic card, memory Xorg leak is about 2 GB per day. So i
have to restart the system every once in a while.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
And I have the same issue on my Toshiba C650D w/ 3 GB and AMD Radeon
6350. Being that it is an older laptop and has only 3 GB memory, I have
to either restart or kill and restart Xorg many times a day. Terrible,
and soon to be a deal breaker for Xubuntu if a fix is not released very
soon.
This
@Nipul Gandhi
Based on the date of your comment, I ask if you noticed the memory leak
exacerbated after the recent Network-manager-gnome 0.9.8.8-0ubuntu4.3
update from Network-manager-gnome 0.9.8.8-0ubuntu4.2?
After the above NMG update, on my system, Xorg uses up all memory
several times a
** Package changed: xorg (Ubuntu) = fglrx-installer (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314787
Title:
Memory leak
To manage notifications about this bug go to:
If you get a worser problem with the updated network-manager-gnome, does
killing nm-applet free some of the leaked memory?
** Changed in: fglrx-installer (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
No, it does not release any of the memory used by Xorg, just the memory
used by NMG. One can exit all open apps, and even kill many processes
and Xorg retains the leaked memory.
There is definitely some relation between the latest NMG update and the
Xorg memory leak. I have since backracked to
To be clear (which the above was not):
The extreme memory leakage mentioned in the last paragraph above is of
course, AFTER the NMG update. However, the leak before the NMG update
is still initiated by activity through the network interfaces, it is
just not anywhere near as extreme.
--
You
I have the same problem. I have a DELL XP with 8GB and a AMD Radeon 5700
XOrg will grow to take up around 5-6 GB every 24 hours. I have to kill Xorg
with sudo restart lightdm daily.
The issue only started after I upgraded from Ubuntu 13.10 to 14.04
Please help !
--
You received this bug
I have the same problem since I upgraded from 13.10 to 14.04 on my
TOSHIBA S50D. AMD A10 4 core processor and a RADEON HD 8500 dual graphis
card. With only the system monitor running in a 24 hour period Xorg
consumes 7GB of pgysical memory and 4 GB of swap space.
Another symptom, is that on the
I have the same problem, memory leak galore, fglrx in combination with
Xorg and the selected window manager.
Ironically the bug seem to trigger memory leaks in Xorg a lot faster
when using Gnome classic login (metacity), like 1GB per day, than it
does when you login choosing Unity (default),
Same here, trusty and fglrx, eventually xorg eats up 3.5 gb of RAM and I
have to restart. Otherwise it will eventually lock up the entire system
(can't alt-ctrl out to a terminal). However I can still ssh into the
machine, but xorg refuses to be killed.
xrestop doesn't show anything with more
I suspect the memory leak is related to fglrx. After I removed it, Xorg
stopped eating my RAM. Note that OP is also using fglrx.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314787
Title:
Memory
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314787
Title:
43 matches
Mail list logo
