From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91982] [radeonsi] fs leak in get_radeon_bo()
Date: Fri, 11 Sep 2015 19:03:48 +0000 [thread overview]
Message-ID: <bug-91982-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2842 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91982
Bug ID: 91982
Summary: [radeonsi] fs leak in get_radeon_bo()
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: shawn.starr@rogers.com
QA Contact: dri-devel@lists.freedesktop.org
While debugging something for Borderlands 2, I broke the DRI driver, tripped a
file descriptor leak
Mesa git master (Sept 10th build), kernel 4.3.0-0.rc0.git9.2.fc24.x86_64m
libdrm-2.4.64 aug 18th
Steps to reproduce fd leak
==========================
Take my trace for Borderlands 2 from here:
https://drive.google.com/open?id=0Bze7CJKD12nORWQ4RTdIbk4zT1k
1) apitrace trim --frames=0-2469 --exact -o bl2469.trace
Borderlands2-menu.trace
2) apitrace replay --loop -b bl2469.trace
Wait... it will crash... see attachment
Kernel:
[129925.490377] VFS: file-max limit 100000 reached
[129925.651137] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to
allocate GEM object (135168, 2, 4096, -23)
[129925.651717] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to
allocate GEM object (135168, 2, 4096, -23)
[129925.652239] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to
allocate GEM object (135168, 2, 4096, -23)
[129925.652754] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to
allocate GEM object (135168, 2, 4096, -23)
[129925.653278] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to
allocate GEM object (1216512, 2, 4096, -23)
[129925.653813] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to
allocate GEM object (1216512, 2, 4096, -23)
[129925.764233] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to
allocate GEM object (8847360, 6, 16384, -23)
[129925.764829] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to
allocate GEM object (8847360, 6, 16384, -23)
[131671.087659] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to
allocate GEM object (4096, 6, 4096, -23)
[131671.207257] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to
allocate GEM object (4096, 6, 4096, -23)
[131671.241259] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to
allocate GEM object (4096, 6, 4096, -23)
[131671.311307] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to
allocate GEM object (4096, 2, 4096, -23)
[131671.312227] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to
allocate GEM object (4096, 2, 4096, -23)
[131671.331355] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to
allocate GEM object (3244032, 2, 4096, -23)
See attachment for stack dump from DRI
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4207 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-09-11 19:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 19:03 bugzilla-daemon [this message]
2015-09-11 19:04 ` [Bug 91982] [radeonsi] fs leak in get_radeon_bo() bugzilla-daemon
2015-09-13 15:42 ` bugzilla-daemon
2015-09-14 1:40 ` bugzilla-daemon
2015-09-14 3:12 ` bugzilla-daemon
2015-09-14 7:39 ` bugzilla-daemon
2015-09-14 18:35 ` bugzilla-daemon
2015-09-14 21:44 ` bugzilla-daemon
2016-08-31 3:51 ` 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-91982-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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