Emulator Issues #1378
closed
[Linux x86_64] OpenGL related crashes
0%
Description
What steps will reproduce the problem?
- Start the Dolphin binary executable
- Load an ISO or rom file
- Wait about 5 seconds for the crash
What is the expected output? What do you see instead?
Expected output: A smoothly working gamecube emulator
Actual output: Annoying crashes
What version of the product are you using? On what operating system?
Revision: 4203
Operating system: Gentoo GNU/Linux x86_64
Please provide any additional information below.
Loading any game results in unavoidable crashes about 5 seconds later.
Dolphin spits out the following message incessantly:
39:33:163 E[Video]: bad scissor!
Ultimately it crashes with:
Dolphin: xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int) ((xcb_req) -
(dpy->request)) >= 0)' failed.
I am pretty sure the Direct3D work is hurting the OpenGL plugin. First: why
do you invest work in a non-free 'technology' (yeah right) like DirectX? It
goes against the very open source nature of this project. Second: What's
wrong with OpenGL on Windows? OpenGL kicks DirectX' ass in every
conceivable way.
Updated by unmacaque over 15 years ago
With a similar setup (Ubuntu Linux 9.04 64 Bit) I also get crashes shortly after
emulation has started. The console output looks different each time. Take for example
Super Smash Bros Melee, it looks like one of these, maybe depending on how far the
emulation has come before the crash happens (usually a few seconds after starting):
Dolphin: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Another one:
Dolphin: ../../src/xcb_io.c:176: process_responses: Assertion `!(req &&
current_request && !(((long) (req->sequence) - (long) (current_request)) <= 0))' failed.
(0) : fatal error C9999: *** exception during compilation ***
If Dolphin manages to get to the menu, it spits out this message with varying error
names and codes:
The program 'Dolphin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
(Details: serial 20438 error_code 170 request_code 152 minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
(0) : fatal error C9999: *** exception during compilation ***
Cg compiler terminated due to fatal error
Updated by 
Updated by