http://bugs.winehq.org/show_bug.cgi?id=3930
Jörg Höhle <hoehle(a)users.sourceforge.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hoehle(a)users.sourceforge.ne
| |t
--- Comment #34 from Jörg Höhle <hoehle(a)users.sourceforge.net> 2010-02-15 11:44:39 ---
Hi,
it would be useful if the many folks interested in this issue could investigate
a little more and figure out the nature of the thread that calls the
CALLBACK_FUNCTION.
A) is one thread created per call to DriverMessage? (ouch, what Damjan's patch
does)
B) is there a unique "WINMM callback thread" that receives one notification per
CALLBACK_FUNCTION event and invokes the function? (i.e. redirecting
DriverCallback FUNCTION to the message queue of one THREAD which then
sequentially calls the functions).
C) is one such thread created per xyzOpen with CALLBACK_FUNCTION?
D) the callback in invoked on the callers thread (some sort of
ExecuteInContext), because winmm processing occurs in another thread already?
E) is that serviced by some other entity altogether?
Then I believe there's a good change to get a patch accepted in Wine.
My observation is that winmm/midi* functions are affected as well as wave*.
MSDN says about MIDI in+out:
http://msdn.microsoft.com/en-us/library/dd798478%28VS.85%29.aspx
"Applications should not call any multimedia functions from inside the
callback function, as doing so can cause a deadlock..."
People warn against calling winmm functions in various forum posts I googled
up, indeed reporting (sometimes random) hangs on native.
"... Other system functions can safely be called from the callback."
This is different from what Damjan says in comment #18.
I've seen logs of apps calling midiStreamOut from within the MOM_DONE callback
(without hanging). This is clearly not allowed, but apps do so, so Wine must
support it.
There's a particularly interesting note about MEVT_F_CALLBACK:
http://msdn.microsoft.com/en-us/library/dd743561%28VS.85%29.aspx
"Any events after the MEVT_F_CALLBACK event in the buffer will be scheduled and
sent on time regardless of how much time is spent in the callback function."
This suggests that indeed there's a decoupled entity that invokes the callback
functions and does not disturb the time-critical playing of MIDI notes. Wine
currently would freeze MIDI output while busy in the callback.
Perhaps this decoupling only applies to MEVT_F_CALLBACK and not to other
messages like MOM|WOM_OPEN|DONE, but perhaps the mechanism applies to all of
winmm?
Regards,
Jörg Höhle
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=3493
bl00d_rav3n(a)gmx.net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bl00d_rav3n(a)gmx.net
--- Comment #40 from bl00d_rav3n(a)gmx.net 2010-02-15 08:56:23 ---
(In reply to comment #39)
> for the record, problem seems to be still there with 1.1.36
I tried out with wine 1.1.38 on Arch and the problem seems fixed. (configured
as WinXP, windowed mode, X has 32 bit depth)
But now the game crashes after some seconds, even in the main menu.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=20616
Summary: Warcraft 3 crash when login to BNet
Product: Wine
Version: 1.1.32
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: elvanor2007(a)gmail.com
This is a fully reproducible crash, I think it's different from bug 9787 as the
patches there were only needed to be able to host a game on BNet (I did not
patch War3 with those but using older versions of Wine like 0.9.59 I was able
to play on BNet without problems).
The bug happens when you login to Battle.Net. The login seems to proceed OK but
when the bronze doors open there is a systematic crash:
FATAL ERROR!
ACCES_VIOLATION
The memory could not be 'written'.
It tries to access memory at 0x00000078.
I reproduced this using 1.1.27, 1.1.28, 1.1,31, 1.1.32. Gentoo Linux, kernel
2.6.30.9, nvidia-drivers-185.18.36 on x86.
Until this bug is fixed, I can unfortunately no longer play War3 under Wine :(
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=9190
Vitaliy Margolen <vitaliy(a)kievinfo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on|21726 |
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=9008
Vitaliy Margolen <vitaliy(a)kievinfo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on|21726 |
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=21641
Summary: Black water in Age Of Empires III
Product: Wine
Version: 1.1.38
Platform: x86
URL: http://www.microsoft.com/games/pc/age3.aspx#downloads
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jaimerave(a)gmail.com
There is a regression from Wine 1.1.37 that makes the water appear black in age
of empires III. Regression Test result:
ef82681d59ec264b981bb3653ea774044f02fa9c is first bad commit
commit ef82681d59ec264b981bb3653ea774044f02fa9c
Author: Henri Verbeet <hverbeet(a)codeweavers.com>
Date: Mon Feb 1 13:52:57 2010 +0100
wined3d: Handle a zero source value for WINED3DSIH_RCP.
:040000 040000 631cf1be997a0ae11b2feaca92a987fdff47c935
ab263cdcbc9159b5748ba4ec13bdb50172816ef3 M dlls
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=9190
Michael <mikademus(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |21726
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=9008
Michael <mikademus(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |21726
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=9190
--- Comment #16 from Michael <mikademus(a)gmail.com> 2010-02-15 06:25:04 ---
This bug may partially depend on http://bugs.winehq.org/show_bug.cgi?id=21726
(lack of explicit access and creation of front and back buffers in WINE for
ddraw interfaces prior to version 7).
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.