From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 18953] randr crashes server
Date: Sun, 11 Sep 2011 02:38:33 -0700 (PDT) [thread overview]
Message-ID: <20110911093833.C8814130160@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-18953-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=18953
--- Comment #3 from Christian Volkmann <haveaniceday@cv-sv.de> 2011-09-11 02:38:33 PDT ---
May be I can reproduce this bug on a openSUSE:
<https://bugzilla.novell.com/show_bug.cgi?id=716220>
It looks for me that xrandr does not resize the "system buffer"
(exa_migration_mixed.c)
> I have doubled the allocated memory at exa_migration_mixed.c line 205 for a
> test.
> The crash is gone. There are now copy of the images (shown by display) on
> the other screen.
> => The problems are more complex than missing increased buffers.
/* Do we need to allocate our system buffer? */
if (!pExaPixmap->sys_ptr) {
pExaPixmap->sys_ptr = malloc(pExaPixmap->sys_pitch *
pPixmap->drawable.height);
if (!pExaPixmap->sys_ptr)
FatalError("EXA: malloc failed for size %d bytes\n",
pExaPixmap->sys_pitch * pPixmap->drawable.height);
}
valgrind ( as root ) with the x-server showed a write after the buffer
"pExaPixmap->sys_ptr".
But may be mine is a different error ?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next parent reply other threads:[~2011-09-11 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-18953-502@http.bugs.freedesktop.org/>
2011-09-11 9:38 ` bugzilla-daemon [this message]
2011-09-12 8:36 ` [Bug 18953] randr crashes server bugzilla-daemon
2011-09-12 19:31 ` bugzilla-daemon
2012-12-29 11:50 ` 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=20110911093833.C8814130160@annarchy.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