http://bugs.winehq.org/show_bug.cgi?id=30191
Bug #: 30191
Summary: Stuttering mmdevapi audio (Mac OS X)
Product: Wine
Version: 1.4
Platform: x86
OS/Version: Mac OS X
Status: NEW
Severity: normal
Priority: P2
Component: mmdevapi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hoehle(a)users.sourceforge.net
CC: aeikum(a)codeweavers.com
Classification: Unclassified
The interactive mmdevapi render tests stutters quasi continuously on my Mac OS
X "early 2009" nVidia Mac mini.
Actually, stuttering can be interpreted as an indicator of low-latency, which
is good :-) Consider winecoreaudio's 20ms period. If audio would only start
at e.g. t=9ms, then at period time t=20, underrun would be very far when
writing the next frames.
The reasons for stuttering are known from winealsa, yet the details are
different: lead-in and regularity.
Lead-in:
Note that mmdevapi/render.c:test_worst_case does not behave like XAudio2 with
winecoreaudio and wineoss, due to their use of a 20ms period. Alexey's
analysis in bug #28723, comment #19 is that XAudio then writes a lead-in of
3/4*4 = 3 periods, unlike the 1 period written in the 10ms period case.
test_worst_case uses 0 or 1 period.
So XAudio2 apps may not stutter, whereas the mmdevapi test does. That does not
imply that our winecoreaudio code is great, rather than that we're forbidden to
reduce the period to the 10ms that native uses everywhere.
Unlike ALSA, I see no notion of underrun in CoreAudio. So I don't see when
writing a lead-in would be appropriate, except at start. I think we need
something else.
Regularity/stability:
XAudio2 and test_worst_case write at most one period worth of frames per event.
Writing nothing is a guarantee of underrun (unless the event rate is
artificially high to counter this). Indeed, adding a trace("MISS") to
test_worse_case every time GetCurrentPadding is too high to add more samples
correlates with some, but not all underruns.
Again, my ntdll CreateTimerQueue stabilisator patch from bug #30071 helps a
little, as otherwise callbacks are mostly 21ms apart rather than 20ms. That
clock skew also accounts for a few underruns.
However the major point is: XAudio2 needs event signalling to match decrease of
padding, such that it adds the next period of data. My ALSA work-in progress
code does exactly that, but CoreAudio needs it even more due to the absence of
the lead-in safety-belt.
--
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=26800
Summary: KDE taskbar is over app window
Product: Wine
Version: 1.3.17
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: alexandrbezenkov(a)gmail.com
My KDE 4.4.3 taskbar is over the app window in fullscreen. If wine is switched
in virtual desktop mode, then I have a blue bar in the top of screen making
game graphics go lower than it must be. Running game in the second X server
gives the same result as running in VD mode.
Specs: Mandriva 2010.2, KDE 4.4.3, ATI RadeonHD 4350 with fglrx 8.791
driver(corresponds ATI Catalyst 10.11).
Wine versions bug present in: 1.3.14, 1.3.15, 1.3.17
--
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=32386
Bug #: 32386
Summary: MSTSC (Remote Desktop) 7.0 crashes
Product: Wine
Version: 1.5.18
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kenjiru.ro(a)gmail.com
Classification: Unclassified
Created attachment 42735
--> http://bugs.winehq.org/attachment.cgi?id=42735
MSTSC 7.0 stack trace
After running as expected for some time, the application crashes.
I've attached the stack trace.
--
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=33178
Bug #: 33178
Summary: Game 'Rome: Total War' crashes under wine 1.4
w/err:seh:raise_exception Unhandled exception code
c0000005 flags 0 addr 0xeb2119
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: runevi(a)nwo.no
Classification: Unclassified
This is an error with the game "Rome: Total War"
Game worked wonderfully well for two days of gameplay until suddenly it crashes
(no matter what) when I click End Turn
$ wine --version
wine-1.4
Wine outputs the following errors:
fixme:d3d_surface:surface_convert_format Cannot find a conversion function from
format WINED3DFMT_B5G6R5_UNORM to WINED3DFMT_B8G8R8A8_UNORM.
fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #13:
fixme:d3d_shader:print_glsl_info_log Vertex info
fixme:d3d_shader:print_glsl_info_log -----------
fixme:d3d_shader:print_glsl_info_log 0(13) : warning C7050: "R5.w" might be
used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(14) : warning C7050: "R6.w" might be
used before being initialized
fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #22:
fixme:d3d_shader:print_glsl_info_log Vertex info
fixme:d3d_shader:print_glsl_info_log -----------
fixme:d3d_shader:print_glsl_info_log 0(12) : warning C7050: "R4.w" might be
used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(13) : warning C7050: "R5.w" might be
used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(10) : warning C7050: "R2.w" might be
used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(11) : warning C7050: "R3.w" might be
used before being initialized
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0xeb2119
fixme:advapi:RegisterEventSourceA ((null)," "): stub
fixme:advapi:RegisterEventSourceW (L"",L" "): stub
fixme:advapi:ReportEventA
(0xcafe4242,0x0001,0x0000,0x00000000,(nil),0x0001,0x00000060,0x62e5dc,0x65309a):
stub
fixme:advapi:ReportEventW
(0xcafe4242,0x0001,0x0000,0x00000000,(nil),0x0001,0x00000060,0x133f78,0x65309a):
stub
err:eventlog:ReportEventW L"6"
fixme:advapi:DeregisterEventSource (0xcafe4242) stub
fixme:advapi:RegisterEventSourceA ((null)," "): stub
fixme:advapi:RegisterEventSourceW (L"",L" "): stub
fixme:advapi:ReportEventA
(0xcafe4242,0x0001,0x0000,0x00000000,(nil),0x0001,0x000002cc,0x62e5dc,0x653112):
stub
fixme:advapi:ReportEventW
(0xcafe4242,0x0001,0x0000,0x00000000,(nil),0x0001,0x000002cc,0x133f78,0x653112):
stub
err:eventlog:ReportEventW L"7"
I'm guessing that the interesting line is:
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0xeb2119
I'm sorry for the backtrace paste. It wasn't extremely large, so I'm hoping
it's okay.
--
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=27863
Summary: eMachineShop: unable to get past "Fix Video problems"
screen
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Mac OS X 10.6
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sam.kuper(a)uclmail.net
Created an attachment (id=35644)
--> (http://bugs.winehq.org/attachment.cgi?id=35644)
Screenshot of "Fix Video problems" window
System used:
* 2.16GHz Macbook
* Mac OS X 10.6.8
* Wine 1.3.24 (installed via MacPorts)
Steps to reproduce:
Download emssetup173.exe from
http://www.emachineshop.com/machine-shop/Download/page100.html to Downloads
folder
In Terminal, enter: cd ~/Downloads/
Then enter: wine emssetup173.exe
Allow the installation wizard to run with default settings.
In Terminal, enter: cd ~/.wine/drive_c/Program Files/eMachineShop
Then enter: wine emachineshop.exe
A popup window appears, via X11, titled "Fix Video problems" (see attachment).
It offers a button to activate software-only rendering mode. Regardless whether
I select that mode or not, the software does not run any further.
If I quit X11 and run emachineshop.exe again, then I get a different window
complaining that eMachineShop didn't quit properly the last time it was run and
asking me if I'd like to run it again "normally", or with a blank document,
etc. But after that, I get the "Fix Video problems" window again.
--
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=27734
Summary: Aion crash every half hour and incorrectly displaying
quest logs.
Product: Wine
Version: 1.3.23
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mikahbot(a)gmail.com
Created an attachment (id=35489)
--> (http://bugs.winehq.org/attachment.cgi?id=35489)
Aion game crash text
So, I was able to install Aion by pulling the files from the Windows
installation, installing the language font packs, mono, and the like. However,
there are two things I found are annoying, and because of their frequency, I am
setting the severity as major.
Problem #1:
Every half hour of login time, Aion suddenly crashes. I always use it with a
console command so that I can see the output and this is what I got [see
attachment]. the first few lines before the ... is what I get when I play the
game, and after if what happens when it crashes.
Problem #2:
Every fresh login displays all the text information correctly. However, within
15 minutes or less, quest logs become glitched. When you click on a quest, I
get a scroll with the text on it that's smooshed together [as is the easiest to
explain]. Instead of being neatly separated as you see in this text, it's
glued together. It's the same for the tracking options on the top right.
Is anyone else having these problems and if so, is there a possible fix or a
workaround? Also, the options in the system menu don't seem to want to stick.
--
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=27509
Summary: Eden Eternal Will Not Launch _Launcher.exe / Client
Product: Wine
Version: 1.3.22
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: iyeru42(a)gmail.com
The client produces no debug output, so it cannot be traced. Anything before
you press "Start Game" is related to the launcher of Eden, and not the client.
Also, installing indeo codecs, and some other codecs will cause the launcher to
spam "Encoder has started" messages, or whatever.
--
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=32892
Bug #: 32892
Summary: FlushFileBuffers cause termination of RS232
functionality
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sorokinea(a)mail.ru
Classification: Unclassified
Comp port is opened once. After each output FulshFileBuffers is called. After
2-4 writes COM port stop sending and receiving answers.
--
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=31495
Bug #: 31495
Summary: Dota 2: performance issues on post-game screen
Product: Wine
Version: 1.5.11
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: phoenix(a)mail.ru
Classification: Unclassified
Created attachment 41403
--> http://bugs.winehq.org/attachment.cgi?id=41403
usual game fps
Repro:
1. Start/watch dota 2 game
2. Wait for one side to win
3. Observe performance of post-game screen
Result:
Performance drops significantly while showcasing awards earned by player; after
showcasing is finished, it starts spiking. Usually i have 30-35 fps with medium
graphic settings, on post-game screen during showcasing it drops to 4-6, then
spikes between 6-8 and 40 (final scene looks relatively simple).
Expected:
No significant performance drop should occur.
Note:
You can launch dota 2 with "-console" option (add it to RMB Dota 2 > Properties
> Set launch options), during match press ~, and enter cl_showfps 1 - to
measure accurate value of fps.
--
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=32352
Bug #: 32352
Summary: ntsd2.4 gives error message "cannot create art
surface" and crashes when loading sasuke.dat
Product: Wine
Version: 1.4.1
Platform: Other
OS/Version: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: advapi32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lokeo78(a)gmail.com
Classification: Unclassified
I'm a noob, so I don't know anything. Many modules listed as deferred. 288 vram
and simply trying to run the .exe.
--
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.