dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75732] New: Memory leak with celestia
Date: Mon, 03 Mar 2014 23:26:14 +0000	[thread overview]
Message-ID: <bug-75732-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2685 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=75732

          Priority: medium
            Bug ID: 75732
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Memory leak with celestia
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: rankincj@googlemail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Drivers/Gallium/r600
           Product: Mesa

This bug might be a duplicate of #74549. However, WoW + Wine + Valgrind is
currently proving to be an intractable problem, and so I've decided to Valgrind
celestia instead (since at least I've managed to get THAT to running again on
x86_64!!!!!!!)

For this test, git HEAD was set to:

commit 9bace99d77642f8fbd46b1f0be025ad758f83f5e
Author: Zack Rusin <zackr@vmware.com>
Date:   Tue Jan 28 16:34:18 2014 -0500

    gallivm: fix opcode and function nesting

I executed the following command:

$ valgrind --leak-check=full celestia

and amidst all of the other issues that Valgrind complained about, it also
happened to mention this:

==7446== 352 bytes in 1 blocks are possibly lost in loss record 8,803 of 9,718
==7446==    at 0x4C291D4: calloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==7446==    by 0x4011C44: _dl_allocate_tls (dl-tls.c:296)
==7446==    by 0xBEE8862: pthread_create@@GLIBC_2.2.5 (allocatestack.c:580)
==7446==    by 0x22F18208: pipe_thread_create.constprop.7 (threads_posix.h:264)
==7446==    by 0x22F18B47: radeon_drm_winsys_create (radeon_drm_winsys.c:661)
==7446==    by 0x22BA18F5: create_screen (drm_target.c:38)
==7446==    by 0x22F13876: dri2_init_screen (dri2.c:1044)
==7446==    by 0x22BA295F: driCreateNewScreen2 (dri_util.c:158)
==7446==    by 0x52DC260: dri2CreateScreen (dri2_glx.c:1240)
==7446==    by 0x52B67E8: __glXInitialize (glxext.c:778)
==7446==    by 0x52B31AA: GetGLXPrivScreenConfig.part.2 (glxcmds.c:174)
==7446==    by 0x52B392F: glXChooseVisual (glxcmds.c:170)
==7446==
==7446== 360 bytes in 5 blocks are possibly lost in loss record 8,811 of 9,718
==7446==    at 0x4C291D4: calloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==7446==    by 0xA24CEC6: g_malloc0 (in /usr/lib64/libglib-2.0.so.0.3800.2)
==7446==    by 0x9FBC1D4: g_closure_new_simple (in
/usr/lib64/libgobject-2.0.so.0.3800.2)
==7446==    by 0x9FBD671: g_cclosure_new (in
/usr/lib64/libgobject-2.0.so.0.3800.2)
==7446==    by 0x781E83F: gtk_action_group_add_toggle_actions_full (in
/usr/lib64/libgtk-x11-2.0.so.0.2400.22)
==7446==    by 0x4623F5: main (in /usr/bin/celestia)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4026 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

             reply	other threads:[~2014-03-03 23:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03 23:26 bugzilla-daemon [this message]
2014-03-03 23:26 ` [Bug 75732] [r600g] Memory leak with celestia, RV790 bugzilla-daemon
2014-03-04  0:43 ` bugzilla-daemon
2014-03-04  4:11 ` bugzilla-daemon
2014-03-04  8:53 ` bugzilla-daemon
2014-03-04  8:57 ` bugzilla-daemon
2014-03-05  2:47 ` bugzilla-daemon
2014-03-05  8:48 ` bugzilla-daemon
2014-03-05 14:31 ` bugzilla-daemon
2019-09-18 19:15 ` 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-75732-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