From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64099] New: Mesa 9.0.3 implementation error: In _mesa_DeleteHashTable, found non-freed data
Date: Wed, 01 May 2013 03:55:45 +0000 [thread overview]
Message-ID: <bug-64099-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1037 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=64099
Priority: medium
Bug ID: 64099
Assignee: dri-devel@lists.freedesktop.org
Summary: Mesa 9.0.3 implementation error: In
_mesa_DeleteHashTable, found non-freed data
Severity: minor
Classification: Unclassified
OS: Linux (All)
Reporter: bogomancer@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: 9.0
Component: Drivers/Gallium/r600
Product: Mesa
I'm playing around with GL, and I'm receiving this message when my application
ends:
"Mesa 9.0.3 implementation error: In _mesa_DeleteHashTable, found non-freed
data
Please report at bugs.freedesktop.org"
The problem seems to be with GL_ARB_debug_output, since the message only
appears if I make a call to glDebugMessageInsertARB during my application.
If you need any more information, please ask.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2362 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:[~2013-05-01 3:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 3:55 bugzilla-daemon [this message]
2013-07-23 20:32 ` [Bug 64099] Mesa 9.0.3 implementation error: In _mesa_DeleteHashTable, found non-freed data bugzilla-daemon
2019-09-18 19:02 ` 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-64099-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.