Public bug reported:

Kernal 4.15.0-107 has a memory leak on this pc I am using here the
motherboard is an rm-ecoquiet-965 using 4 gb of ddr 2 667 ram and an
intel T 8300 cpu together with a gt 220 512 mb.

I have noticed this issue with several kernals and I know it is a
strange pc set up, due to using laptop ddr2 and a laptop cpu, together
with the graphics card which is a slimmed down gt 220 having 8 rops and
24 shaders, instead of the more usual 48 shaders, it was built to keep
electricity costs down as I spend a lot of time on my pc, it is
basically a back up pc built during lock down, for those reasons, It was
also, very cheap and uses laptop hard disks as well.

I have been unable to pinpoint the exact source of the memory leak,
which, is never the less present as the two kernals, below, do not
display the same problems.

4.15.0-45 works fine on it, without issues, as does 4.13.0-32.

For anyone else, who may encounter this issue.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1900395

Title:
  Memory Leak

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kernal 4.15.0-107 has a memory leak on this pc I am using here the
  motherboard is an rm-ecoquiet-965 using 4 gb of ddr 2 667 ram and an
  intel T 8300 cpu together with a gt 220 512 mb.

  I have noticed this issue with several kernals and I know it is a
  strange pc set up, due to using laptop ddr2 and a laptop cpu, together
  with the graphics card which is a slimmed down gt 220 having 8 rops
  and 24 shaders, instead of the more usual 48 shaders, it was built to
  keep electricity costs down as I spend a lot of time on my pc, it is
  basically a back up pc built during lock down, for those reasons, It
  was also, very cheap and uses laptop hard disks as well.

  I have been unable to pinpoint the exact source of the memory leak,
  which, is never the less present as the two kernals, below, do not
  display the same problems.

  4.15.0-45 works fine on it, without issues, as does 4.13.0-32.

  For anyone else, who may encounter this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900395/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to