Summary: | randr crashes server | ||
---|---|---|---|
Product: | Mesa | Reporter: | Danny <moondrake> |
Component: | Drivers/DRI/r300 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | haveaniceday |
Version: | git | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Danny
2008-12-08 07:58:10 UTC
Mass version move, cvs -> git Can you reproduce the bug with newer mesa,xf86-video-ati and xserver? 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 ? (In reply to comment #3) > But may be mine is a different error ? It most definitely is. If you can still reproduce your problem with current upstream versions of xserver (1.11) and xf86-video-ati (6.14.2), please file your own bug. xorg-x11-server-7.6_1.10.4-166.2.x86_64 of the opensuse repositories solves my problem. So I xpect the newest server does not fall back to the old problem. Thanks for the hint. I am going to close the bug. I am not sure it is really fixed, but I no longer have this hardware, and nobody else confirmed this problem. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.