http://bugs.winehq.org/show_bug.cgi?id=21714 Jörg Höhle <hoehle(a)users.sourceforge.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hoehle(a)users.sourceforge.ne | |t --- Comment #2 from Jörg Höhle <hoehle(a)users.sourceforge.net> 2010-07-30 09:47:14 --- Is there a demo? or free download URL? Is the crashing version any of the 2 versions present in AppDB (8.0/2009)? If yes, please link the bug to the appropriate version. Is there a known work-around to prevent the crash (e.g. disable music in settings file)? You set "x86-64 Linux". Are you actually running the 64bit version of Wine? I can't recommend doing so because of bug #22146. You can ignore the fixme:mcimidi:... track=N messages. Do you actually hear anything? Do you have any other .exe that manages to play MIDI with Wine on your machine, proving that your Linux/MIDI setup is correct? See http://wiki.winehq.org/MIDI Your backtrace shows that one crash happens from mciSendCommandW. Please attach a WINEDEBUG=+mci,+mcimidi trace so that we can see the offending MCI command and parameters. I suppose that you attached the logs of several test runs because the crash is not always the same (e.g. only your last run produced a backtrace). Please try to find out how to cause reproduceable crashes. WINEDEBUG=warn+heap may help here. Setting HKCU\Software\Wine\WineDbg "ShowCrashDialog"=dword:00000000 also. If you have reasons to believe race conditions are involved, add +tid to WINEDEBUG. -- 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.