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
, the memory consumption was several GBs
so far (11 hours)
So kernel 3.14.39 cured my system.
Need to know which kernel commit(s) fix this memory leak.
So I don't update kernel to 3.16 until this leak is fixed. I stay 3.14.xx
branch.
Big thanks to GVS!!!
--
You received this bug
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
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
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
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:
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:
/ubuntu/ppa
to back up your setup and try the kernel update. With the above config
my system is doing OK now.
Good luck!
Gordon VS
gvsche...@cciwireless.ca
On 14-08-15 01:22 AM, Pekka Kola wrote:
@GVS (gvscheik1-g)
Is you system still up and running without leaks? I have got
3.11.0-20-generic
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 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
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
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
15 matches
Mail list logo
