http://bugs.winehq.org/show_bug.cgi?id=26045
Summary: comctl32/imagelist tests show some invalid reads under
valgrind
Product: Wine
Version: 1.3.13
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: download, source, testcase
Severity: minor
Priority: P2
Component: comctl32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Invalid read of size 4
at is_valid (imagelist.c:3618)
by ImageList_Destroy (imagelist.c:796)
by test_iimagelist (imagelist.c:1358)
by func_imagelist (imagelist.c:1961)
by run_test (test.h:556)
by main (test.h:624)
Address 0x7f01a9e8 is 144 bytes inside a block of size 312 free'd
at notify_free (heap.c:262)
by RtlFreeHeap (heap.c:1747)
by RtlFreeAnsiString (rtlstr.c:173)
by FILE_CreateFile (file.c:182)
by NtCreateFile (file.c:271)
by CreateFileW (file.c:1386)
by PROFILE_Open (profile.c:781)
by GetPrivateProfileStringW (profile.c:1128)
by GetPrivateProfileStringA (profile.c:1171)
by GetProfileStringA (profile.c:1199)
by SYSPARAMS_Init (sysparams.c:941)
by process_attach (user_main.c:276)
by DllMain (user_main.c:332)
by __wine_spec_dll_entry (dll_entry.c:40)
by ??? (loader.c:139)
by MODULE_InitDLL (loader.c:978)
by process_attach (loader.c:1067)
by process_attach (loader.c:1059)
by process_attach (loader.c:1059)
by attach_process_dlls (loader.c:2535)
Invalid read of size 4
at is_valid (imagelist.c:3618)
by ImageList_Destroy (imagelist.c:796)
by test_iimagelist (imagelist.c:1368)
by func_imagelist (imagelist.c:1961)
by run_test (test.h:556)
by main (test.h:624)
Address 0x7f01c860 is 64 bytes inside a block of size 312 free'd
at notify_free (heap.c:262)
by RtlFreeHeap (heap.c:1747)
by RtlFreeAnsiString (rtlstr.c:173)
by FILE_CreateFile (file.c:182)
by NtCreateFile (file.c:271)
by CreateFileW (file.c:1386)
by PROFILE_Open (profile.c:781)
by GetPrivateProfileStringW (profile.c:1128)
by GetPrivateProfileStringA (profile.c:1171)
by GetProfileStringA (profile.c:1199)
by SYSPARAMS_Init (sysparams.c:941)
by process_attach (user_main.c:276)
by DllMain (user_main.c:332)
by __wine_spec_dll_entry (dll_entry.c:40)
by ??? (loader.c:139)
by MODULE_InitDLL (loader.c:978)
by process_attach (loader.c:1067)
by process_attach (loader.c:1059)
by process_attach (loader.c:1059)
by attach_process_dlls (loader.c:2535)
--
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=21809
Summary: StarCraft 2 quits after confirming login name
Product: Wine
Version: 1.1.39
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lubosz(a)gmail.com
Created an attachment (id=26391)
--> (http://bugs.winehq.org/attachment.cgi?id=26391)
Attempt to login. Nearly same output if i quit the application at that point.
The client quits without a exception or extra output, after typing in any email
address. There are no errors or output.
In windows the password step would come next, and after that the account check
with the server.
The login window is written in flash, it utilizes Scaleform gfx.
http://en.wikipedia.org/wiki/Scaleform_gfx
--
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=6033
--- Comment #66 from Andrew Trapani <andrewtrapani(a)gmail.com> 2011-02-09 20:40:28 CST ---
Hi,
Without the high resolution patch, it will not even start up.
With the high resolution patch, it does start up.
In the FO2 'ddraw.ini' file added by the high resolution patch, Mode=4,
fullscreen dx9, and mode=5, windowed dx9.
Both result in a white screen on my system (codeweavers 9.2, OS X), just like
the native OS X port (for PPC).
Please try changing the Mode in ddraw.ini in FO2 to use dx9 mode and see what
happens for you.
Otherwise in default mode I get the unplayably slow graphical lag. (push an
arrow key and watch it sluggishly re-draw the screen as it scrolls)
--
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=5526
--- Comment #52 from David Eccles (gringer) <winehq(a)gringer.org> 2011-02-09 19:52:43 CST ---
> Actually the bug has not been committed to upstream because the synchronisation
of the extra thread is broken.
Okay, sorry for getting that wrong.
> A better way to get this game working OK is using the opengl ddraw renderer. At
least if your driver works OK and fast enough with that(it should work with the
nvidia binary driver)
Is it possible that the software fallback for opengl rendering is causing the
slowdown (e.g. on low-spec intel cards like i945)?
--
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=6033
--- Comment #65 from Xavier Vachon <xvachon(a)gmail.com> 2011-02-09 18:05:26 CST ---
For those whom are complaining about the lag, do you use the resolution patch?
I tried today with the GOG version of the game, the unofficial patch and the
high resolution patch, and with a 1680*1050 resolution the game is indeed very,
very slow.
--
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=7990
Sebastian <ghettopolak04(a)hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ghettopolak04(a)hotmail.com
--- Comment #13 from Sebastian <ghettopolak04(a)hotmail.com> 2011-02-09 16:58:31 CST ---
The bug doesn't appear to be present anymore. Tested with wine 1.3.10 and
Catalyst 10.12, with a Radeon 5670.
--
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=5526
--- Comment #51 from Stefan Dösinger <stefandoesinger(a)gmx.at> 2011-02-09 14:53:46 CST ---
Actually the bug has not been committed to upstream because the synchronisation
of the extra thread is broken.
A better way to get this game working OK is using the opengl ddraw renderer. At
least if your driver works OK and fast enough with that(it should work with the
nvidia binary driver)
--
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=24941
Summary: Fable: The Lost Chapters can't play video
Product: Wine
Version: 1.3.5
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: quartz
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
On launch, it hung in the splash screen, and the log showed
err:module:import_dll Library msvcrt.dll (which is needed by
L"C:\\windows\\system32\\msvcr71.dll") not found
err:module:import_dll Library MSVCRT.dll (which is needed by
L"C:\\windows\\system32\\MFC42.DLL") not found
err:module:import_dll Library MFC42.DLL (which is needed by
L"C:\\users\\dank\\Temp\\DW210f4.tmp") not found
I worked around that with 'winetricks vcrun6'.
The game then started up and was somewhat playable.
On startup, the game complained
"Unable to play video."
You could click past it, but it was still annoying.
I worked around that with 'winetricks wmp9 quartz devenum'.
Even if we have to install wmp, it'd be nice if wine's quartz
and devenum were up to the task...
--
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=5526
--- Comment #50 from David Eccles (gringer) <winehq(a)gringer.org> 2011-02-09 14:46:18 CST ---
It's been labelled as fixed for a couple of reasons:
* trigger-happy maintainers that mark bugs as fixed without asking if the
problem has been resolved (e.g. comment #45)
* testing to see if this bug still exists is tricky. I have a suspicion that my
comment #48 was incorrect, because I have also observed slowdowns (but to a
lesser degree) since then
Stefan's patch has not been implemented because the wine architecture has
changed a fair amount since then. I have some vague feeling that fixing bug 421
will be a good canary for when the drawing architecture has stabilised.
--
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=5526
sam.derbyshire(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sam.derbyshire(a)gmail.com
--- Comment #49 from sam.derbyshire(a)gmail.com 2011-02-09 14:28:54 CST ---
This bug does not seem to be fixed. I still get big slowdowns with cursor
flickering on recent versions of Wine (for instance 1.3.13). The game runs much
better in Wine 0.9.51 with Dösinger's patch.
(Note that running the game in 16bpp helps, but not at all as much as
Dösinger's patch.)
Has Dösinger's patch not been implemented? Why has this bug been label as
fixed?
--
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.