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 31617] New: Radeon/Compiz: 'failed to attach dri2 front buffer', error case not handled
Date: Sun, 14 Nov 2010 04:10:14 -0800 (PST)	[thread overview]
Message-ID: <bug-31617-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: Radeon/Compiz: 'failed to attach dri2 front buffer',
                    error case not handled
           Product: Mesa
           Version: 7.9
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/R600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: daniel.lichtenberger@gmail.com


Created an attachment (id=40267)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=40267)
backtrace

System: Fedora 14, Radeon 4850, x86_64.

Using the system's mesa-dri-drivers package Compiz frequently crashes while
resizing windows. The backtrace (attached) and the error message, "failed to
attach dri2 front buffer XX", point to radeon_update_renderbuffers in
radeon_common_context.c around line 745:

            bo = radeon_bo_open(...);

            if (bo == NULL) {

                fprintf(stderr, "failed to attach %s %d\n",
                    regname, buffers[i].name);

            }

            ret = radeon_bo_get_tiling(bo, &tiling_flags, &pitch);


An error message is printed when 'bo' could not be allocated, but bo is then
happily dereferenced in radeon_bo_get_tiling afterwards. Working around the
null pointer dereference (e.g. by adding a 'continue' in the "if bo==NULL"
block) fixes the crash for me and I haven't seen visual artifacts yet, although
the error message is printed from time to time while running Compiz.

The same stacktrace was logged by several people over at
https://bugzilla.redhat.com/show_bug.cgi?id=568593.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2010-11-14 12:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-14 12:10 bugzilla-daemon [this message]
2010-11-15  6:37 ` [Bug 31617] Radeon/Compiz: 'failed to attach dri2 front buffer', error case not handled 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-31617-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