- 26 Jan, 2012 10 commits
-
-
Jacek Caban authored
-
Rico Schüller authored
-
Rico Schüller authored
-
Rico Schüller authored
-
Rico Schüller authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
wined3d: Clear the device if we're not removing the entry from the table in wined3d_unregister_window(). The device may be destroyed after the window is unregistered, causing device_process_message() to access freed memory.
-
Thomas Faber authored
-
Ken Thomases authored
-
- 25 Jan, 2012 30 commits
-
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alistair Leslie-Hughes authored
-
Christian Costa authored
-
Christian Costa authored
d3dxof: Fix object leak in error path by calling Release method which does all the work and simplify some inits for better readability.
-
Andrew Eikum authored
-
Andrew Eikum authored
-
Andrew Eikum authored
-
Jacek Caban authored
-
Jacek Caban authored
-
Frédéric Delanoy authored
-
Detlef Riekenberg authored
-
Detlef Riekenberg authored
-
Detlef Riekenberg authored
-
Austin English authored
-
Austin English authored
-
Austin English authored
-
Austin English authored
-
Alex Henrie authored
-
Francois Gouget authored
-
Matteo Bruni authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
wined3d: Only take the wined3d mutex during the WM_DISPLAYCHANGE handler in device_process_message(). We can deadlock if we send messages while holding the wined3d mutex and the message loop is on another thread. Ideally we probably shouldn't send messages while holding the wined3d mutex at all, but that may be hard to enforce with the way wined3d locking is currently set up.
-
Frédéric Delanoy authored
-
Hwang YunSong authored
-
Nikolay Sivov authored
-
Francois Gouget authored
-