From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 81837] [radeonsi] memory leaks in OpenCL
Date: Wed, 30 Jul 2014 17:42:16 +0000 [thread overview]
Message-ID: <bug-81837-502-7WHbuDYN3B@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-81837-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 586 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=81837
--- Comment #3 from Vladimir Ysikov <grantipak@gmail.com> ---
Created attachment 103691
--> https://bugs.freedesktop.org/attachment.cgi?id=103691&action=edit
valgrind.log
>The output from running the app with valgrind --leak-check=full might be interesting as well.
Speed of pyrit in valgrind very low. After 13 hours i kill program.
Segmentation error occurs after the moment when the end system memory. The
higher the speed of the faster this occurs.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1478 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 prev parent reply other threads:[~2014-07-30 17:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 12:57 [Bug 81837] New: [radeonsi] memory leaks in OpenCL bugzilla-daemon
2014-07-28 14:48 ` [Bug 81837] " bugzilla-daemon
2014-07-29 3:21 ` bugzilla-daemon
2014-07-30 17:42 ` bugzilla-daemon [this message]
2014-07-30 17:47 ` bugzilla-daemon
2014-07-31 3:36 ` bugzilla-daemon
2014-07-31 17:12 ` bugzilla-daemon
2014-08-09 7:46 ` bugzilla-daemon
2014-08-09 11:17 ` bugzilla-daemon
2015-02-21 6:00 ` 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-81837-502-7WHbuDYN3B@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;
as well as URLs for NNTP newsgroup(s).