This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

-- 
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/1798165

Title:
  Vulkan applications cause permanent memory leak with Intel GPU

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  
  == SRU Justification ==
  Vulkan applications, as Dota 2 and DXVK games cause a memory leak where
  memory is never freed and can cause a system crash if the applications are
  used for long enough. Certain applications can make the leak be as high as
  10 MB/minute.

  This commit has been cc'd to upstream stable, but it has not landed in
  Bionic or Cosmic as of yet.

  Details about the upstream bug can be seen at:
  https://github.com/doitsujin/dxvk/issues/632
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  == Fix ==
  337fe9f5c1e7 ("drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set")

  == Regression Potential ==
  Low.  This commit has been cc'd to stable, so it has had additional
  upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  Vulkan applications, as Dota 2 and DXVK games cause a memory leak
  where memory is never freed and can cause a system crash if the
  applications are used for long enough. Certain applications can make
  the leak be as high as 10 MB/minute.

  Details about this bug can be seen at
  https://github.com/doitsujin/dxvk/issues/632 and
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
  The particular commit is:

  commit a2cef7d049f07995406b403605119a54881daf15
  Author: Jason Ekstrand <ja...@jlekstrand.net>
  Date:   Wed Sep 26 02:17:03 2018 -0500

      drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set

      commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.

      We attempt to get fences earlier in the hopes that everything will
      already have fences and no callbacks will be needed.  If we do succeed
      in getting a fence, getting one a second time will result in a duplicate
      ref with no unref.  This is causing memory leaks in Vulkan applications
      that create a lot of fences; playing for a few hours can, apparently,
      bring down the system.

      Cc: sta...@vger.kernel.org
      Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
      Reviewed-by: Chris Wilson <ch...@chris-wilson.co.uk>
      Signed-off-by: Jason Ekstrand <ja...@jlekstrand.net>
      Signed-off-by: Sean Paul <seanp...@chromium.org>
      Link: 
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
      Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>

  On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as:
  https://i.imgur.com/qMAvuwl.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  usuario    4655 F.... pulseaudio
   /dev/snd/seq:        usuario    4640 F.... timidity
  CurrentDesktop: XFCE
  Date: Tue Oct 16 14:16:54 2018
  HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
  InstallationDate: Installed on 2017-06-13 (489 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt 
i915.enable_gvt=1 i915.fastboot=1 
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M 
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x100000
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware                             1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1798165/+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