d2910912a4
some X state will have initialized mutexes and some won't, leading to unpredictable results depending on the feature set compiled into wxWidgets and so on. wxGTK starts by calling Xlib functions indirectly through gdk very early on, so we must hook into wxApp::Initialize(). I believe this should properly fix issue 1540. In case of problems, please reopen that issue. If you see XLockMutex in a backtrace, that's a pretty good indication. git-svn-id: https://dolphin-emu.googlecode.com/svn/trunk@7205 8ced0084-cf51-0410-be5f-012b33b47a6e |
||
---|---|---|
.. | ||
FramebufferManager.cpp | ||
FramebufferManager.h | ||
GLUtil.cpp | ||
GLUtil.h | ||
Globals.h | ||
NativeVertexFormat.cpp | ||
PixelShaderCache.cpp | ||
PixelShaderCache.h | ||
PostProcessing.cpp | ||
PostProcessing.h | ||
RasterFont.cpp | ||
RasterFont.h | ||
Render.cpp | ||
Render.h | ||
SConscript | ||
TextureCache.cpp | ||
TextureCache.h | ||
TextureConverter.cpp | ||
TextureConverter.h | ||
VertexManager.cpp | ||
VertexManager.h | ||
VertexShaderCache.cpp | ||
VertexShaderCache.h | ||
VideoBackend.h | ||
main.cpp | ||
main.h | ||
stdafx.cpp | ||
stdafx.h |