From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 32297] New: [r300g] WoW crashes on exit, when run in a window instead of full-screen.
Date: Fri, 10 Dec 2010 08:11:17 -0800 (PST) [thread overview]
Message-ID: <bug-32297-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=32297
Summary: [r300g] WoW crashes on exit, when run in a window
instead of full-screen.
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: rankincj@googlemail.com
Tested with my RV350, Linux 2.6.36.2 kernel, with WoW running in a 1152x864
window instead of full-screen. On exiting WoW, it crashes with the following
stack trace:
Backtrace:
=>0 0x7d88bbf7 dri2_invalidate_drawable+0x47(dPriv=*** Invalid address
0x0032eda8 ***
Internal symbol error: unable to access memory location 0x32eda8)
[/home/chris/Programs/mesa/src/gallium/state_trackers/dri/drm/dri2.c:60] in
r300_dri.so (0x0032edc0)
1 0x7e9542fb dri2InvalidateBuffers+0x2a(dpy=*** Invalid address 0x0032edc8
***
Internal symbol error: unable to access memory location 0x32edc8, drawable=***
Invalid address 0x0032edcc ***
) [/home/chris/Programs/mesa/src/glx/dri2_glx.c:678] in libgl.so.1 (0x0032ee00)
2 0x7e95496f DRI2WireToEvent+0x11e(dpy=*** Invalid address 0x0032ee08 ***
Internal symbol error: unable to access memory location 0x32ee08, event=***
Invalid address 0x0032ee0c ***
Internal symbol error: unable to access memory location 0x32ee0c, wire=***
Invalid address 0x0032ee10 ***
Internal symbol error: unable to access memory location 0x32ee10)
[/home/chris/Programs/mesa/src/glx/dri2.c:136] in libgl.so.1 (0x0032ee40)
3 0x7e9a9dd1 _XEnq+0x60() in libx11.so.6 (0x0032ee90)
4 0x7e9b0a64 in libx11.so.6 (+0x42a63) (0x0032eeb0)
5 0x7e9b10f8 _XEventsQueued+0x67() in libx11.so.6 (0x0032eed0)
6 0x7e9b119a _XFlush+0x49() in libx11.so.6 (0x0032eef0)
7 0x7e988eb2 XFlush+0x31() in libx11.so.6 (0x0032f000)
8 0x7dd7087a X11DRV_WindowPosChanged+0x199() in winex11 (0x0032f100)
9 0x7ed2ff32 USER_SetWindowPos+0x6e1() in user32 (0x0032f240)
10 0x7ed2f2d7 SetWindowPos+0xa6() in user32 (0x0032f2c0)
11 0x7ed30e95 WINPOS_ShowIconTitle+0xf4() in user32 (0x0032f310)
12 0x7ed31bd4 show_window+0x513() in user32 (0x0032f390)
13 0x7ed31cdb ShowWindow+0x6a() in user32 (0x0032f3c0)
14 0x007b2651 in wow (+0x3b2650) (0x0032f3d4)
15 0x007b1008 in wow (+0x3b1007) (0x0032f444)
16 0x7ed33e1a WINPROC_wrapper+0x19() in user32 (0x0032f474)
17 0x7ed3456c call_window_proc+0x5b() in user32 (0x0032f4c4)
18 0x7ed351fc WINPROC_CallProcWtoA+0x90b() in user32 (0x0032fb54)
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-12-10 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 16:11 bugzilla-daemon [this message]
2011-01-05 0:35 ` [Bug 32297] [r300g] WoW crashes on exit, when run in a window instead of full-screen bugzilla-daemon
2011-01-05 1:30 ` [Bug 32297] [r300g] Memory corruption crash when exiting DRI2/OpenGL application bugzilla-daemon
2011-01-05 1:48 ` [Bug 32297] [r300g] Memory corruption crash when exiting application using DRI2_InvalidateBuffers bugzilla-daemon
2011-01-05 1:49 ` bugzilla-daemon
2011-01-06 0:40 ` bugzilla-daemon
2011-01-09 19:13 ` 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-32297-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.