From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 209987] New: Memory leak in amdgpu_dm_update_connector_after_detect
Date: Sun, 01 Nov 2020 06:15:59 +0000 [thread overview]
Message-ID: <bug-209987-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=209987
Bug ID: 209987
Summary: Memory leak in amdgpu_dm_update_connector_after_detect
Product: Drivers
Version: 2.5
Kernel Version: 5.9.1
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: lstarnes1024@gmail.com
Regression: No
Created attachment 293341
--> https://bugzilla.kernel.org/attachment.cgi?id=293341&action=edit
/sys/kernel/debug/kmemleak
It looks like there's a memory leak in
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c:amdgpu_dm_update_connector_after_detect.
It appears to be calling drm_add_edid_modes, which indirectly calling ito
either do_detailed_mode or drm_mode_duplicate.
This has caused me to run out of memory a handful of times, which could only be
resolved by rebooting.
I only experienced this after upgrading to 5.9.1, and it looks like commit
b24bdc37d03a0478189e20a50286092840f414fa added the call to drm_add_edid_modes
in amdgpu_dm_update_connector_after_detect.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-11-01 6:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 6:15 bugzilla-daemon [this message]
2020-11-01 6:19 ` [Bug 209987] Memory leak in amdgpu_dm_update_connector_after_detect bugzilla-daemon
2020-11-09 4:24 ` bugzilla-daemon
2020-11-09 6:14 ` bugzilla-daemon
2020-12-21 15:57 ` bugzilla-daemon
2020-12-21 16:29 ` bugzilla-daemon
2020-12-21 16:47 ` bugzilla-daemon
2020-12-21 17:17 ` bugzilla-daemon
2020-12-24 15:01 ` bugzilla-daemon
2021-01-05 14:14 ` bugzilla-daemon
2021-01-10 19:47 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-209987-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox